BSOD ataport.sys

[slyckmb]

I've been running this install of Windows 7 since February 2011. Yesterday, shortly after I logged into Windows, the subject BSOD came up for the first time.

I rebooted, and logged in again, and it came up at the same point - a few seconds after login.

I logged in via "Safe Mode" and found that MS Explorer would continuously "restart" itself, but no BSOD would appear. I was able to complete a full CHKDSK on the only hard disk in the system.

I logged into the full system again, and the same BSOD appeared. I then tried to login via "Safe Mode with Networking" and the login process froze on the driver load screen. I left it an went to bed.

This morning, the system had restarted. I did a normal login, and got the same BSOD. I then did an advanced F8 bood, and disabled automatic restarts, as well as tride to boot the "last known good configuration" - which still resulted in the BSOD.

I rebooted into "Safe Mode with Networking" and am now currently logged into a stable system. I have attached my minidum files.

Any help is appreciated.

 

[Thrax]

Try this: http://www.pchelpforum.com/win-7-vista-bsod/103587-blue-screen-death-ataport-sys.html#post624061

 

[zigzag3143]

I've been running this install of Windows 7 since February 2011. Yesterday, shortly after I logged into Windows, the subject BSOD came up for the first time.

I rebooted, and logged in again, and it came up at the same point - a few seconds after login.

I logged in via "Safe Mode" and found that MS Explorer would continuously "restart" itself, but no BSOD would appear. I was able to complete a full CHKDSK on the only hard disk in the system.

I logged into the full system again, and the same BSOD appeared. I then tried to login via "Safe Mode with Networking" and the login process froze on the driver load screen. I left it an went to bed.

This morning, the system had restarted. I did a normal login, and got the same BSOD. I then did an advanced F8 bood, and disabled automatic restarts, as well as tride to boot the "last known good configuration" - which still resulted in the BSOD.

I rebooted into "Safe Mode with Networking" and am now currently logged into a stable system. I have attached my minidum files.

Any help is appreciated.

First check the thread that Thrax suggests, It is from Feb of this year and one of mine.


Then update these old drivers

EMS7SK.sys    2/15/2006 10:55:09 PM        0x92092000    0x920a0e00    0x0000ee00    0x43f3e98d                        
ESM7SK.sys    2/15/2006 10:55:15 PM        0x920ba000    0x920cc380    0x00012380    0x43f3e993                        
lmimirr.sys    4/10/2007 6:32:11 PM        0x92184000    0x92184c80    0x00000c80    0x461c106b                        
TVALZ_O.SYS    11/8/2007 11:07:46 PM        0x889c9000    0x889cd180    0x00004180    0x4733cf02                        
RaInfo.sys    1/4/2008 2:57:12 PM        0x923f7000    0x923f8800    0x00001800    0x477e8188                        
LMIRfsDriver.sys    7/14/2008 12:26:22 PM        0x8eb2e000    0x8eb38000    0x0000a000    0x487b7e2e                        
SynTP.sys    8/14/2008 10:02:22 PM        0x9211f000    0x9214f000    0x00030000    0x48a4e3ae                        
AGRSM.sys    11/10/2008 10:56:37 AM        0x90670000    0x90776000    0x00106000    0x49184ba5                        
hamachi.sys    2/19/2009 6:36:27 AM        0x92222000    0x92226c00    0x00004c00    0x499d362b                        
netw5v32.sys    3/26/2009 12:10:37 PM        0x91c1a000    0x9202d000    0x00413000    0x49cba8fd

Finally since they are all memory exceptions please run these two tests




1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html