New
#1
BSOD @ Shutdown/Startup
MY PC started acting up last week, crashing every time I tried to shut it down - immediately after I hit "shutdown", it would go to the BSOD:
STOP 0X0000001E (OXFFFFFFFFC0000005, 0XFFFFF80002EB7117, 0X000000000000000, 0X000000007EFA0000)
This prevents me from using system restore, as when it goes to restart the PC will instead hit me with the BSOD instead of restoring. I reinstalled the OS hoping that would fix it up but no go, so I'm hoping to get a bit of help from the folks who know more than I (which is about all of you I would suppose!)
Attached you'll find the SF information requested in the BSOD thread instructions. In the event that my system specs aren't displayed in this post, here they are:
Windows 7 Home Premium
Gigabyte GA990FXA-UD3 Motherboard
AMD FX6100 6-Core Processor
8GB Kingston HyperX DDR3 (2 x 4GB)
Thermaltake TR2 RX 850W PSU
2 1TB Western Digital 7200RPM Hard Drives
Thank you for your help! Let me know if I've missed any information required.
=========
ETA - From "WhoCrashed" utility:
On Sun 10/7/2012 11:52:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-35833-01.dmp
This was probably caused by the following module: atapi.sys (atapi+0x2101)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000337EFEA, 0x1, 0x18)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI IDE Miniport Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.