BSOD problems. Minidump included

Larry227 · 17 Dec 2010

My wife's computer started acting up a few days ago. AFAIK she didn't install anything new before it happened and I know there were no hardware changes. It just started rebooting on it's own. I went to Safe Mode and turned off the auto-restart so I could get the BSOD long enough to get some clues.

Last night it wouldn't even try to start and I diagnosed a bad ps. It would only put out 6v on the 12v wires in the pc and on the bench. I thought that would be the problem but a new ps today lets it start but it still crashes when she logs in on a normal boot. I can get to safe mode just fine so I copied the minidump files I'm attaching.

So far I tried new power supply, swapped graphics card with mine, ran memtest on the ram (passed). As of this minute I just left safe mode after changing the startup in msconfig to Diagnostic. It booted into windows normally for now but not sure where to go from here. I'm attaching all the minidumps from when this started on the 14th.

Win 7 Pro 64bit
Asus P7H55-M Pro w/i7 quad core
8gb (4x2) of Corsair DDR3 ram

Larry227 · 17 Dec 2010

I've tried a few more things since my first post.

I unhooked all periphals and used a substitute keyboard and mouse.
Unplugged both internal DVD players and her 1TB SATA storage drive.
Disabled onboard sound and lan in the bios.
Created a new user and tried to log in to it with no success.

None of the above helped. It gets to the login screen and after inputting the password it hangs up and I get the BSOD IRQL not less or equal
Stop: 0x0000000A

Now I'm having a hard time just getting into Safe mode. I tried botting to the Win7 DVD and repairing Startup but it finds nothing wrong. Can't restore back to last week because she didn't have system restore turned on.

I really don't want to format (especially if it's a hardware issue) but I'm running out of ideas.

Jonathan_King · 17 Dec 2010

Hello, and welcome!

I'm wondering if this could be a hard drive problem; could you run SeaTools on the drive to find out? You can use either the Windows or DOS version; the DOS version might be helpful if Windows cannot boot.

...Summary of the dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 14:58:22.442 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:14.457
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 14:07:38.242 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:34.256
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  taskhost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiTryUnwaitThread+28
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 13:50:21.898 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:35.912
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  AtBroker.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiTryUnwaitThread+28
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 13:40:36.340 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:41.354
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 12:36:16.582 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:36.596
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  AtBroker.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Larry227 · 17 Dec 2010

Thanks for the response. I was wondering about the hd too. I downloaded the iso and will burn it and boot to it right away. I didn't even think of looking for that tool. I"ll post back as soon as the scan is done.

Larry227 · 18 Dec 2010

Ok, both hd's passed all the tests. I tried the repair options from the DVD bootup a couple more times and it would say it repaired but never did. Since I couldn't do a normal bootup I couldn't run an actual upgrade/repair full installation.

I finally gave up and formatted. The wife has never been happy with Win 7 anyways so I put XP back on for her. It ran fine all night with numerous reboots while doing updates so I guess it's case closed. She'll be happier now but I'm a bit discouraged. It's been a long time since I had a computer get the best of me like this.

Thanks for the help Jonathon.

Jonathan_King · 18 Dec 2010

Sorry to hear that, but I'm glad that you at least have XP working good. Let us know if you need anything else, or if the problem returns on XP.