Windows cold boot problem

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Beth_1987

Thread Starter
Joined
Jan 21, 2013
Messages
20
Hello Everyone!

When I cold boot my pc, it fails to complete the boot initially, then boots to the desktop with an error reporting message, then works fine (occasionally reboots 8-10 hours later with the same message).

My system:
OS: Windows 8 64 bit
Processor: AMD Phenom II x4 965
Motherboard: Gigabyte 970A-D3 rv 1.4
Video Card: Gigabyte Radeon HD 6670
RAM: Kingston HyperX KHX1600C9D3K2/4GX 4GB (2x2 DDR3 1600)
WhoCrashed Report is below

My thoughts were that it was a video driver issue, but uninstalling and reinstalling the video drvers and ati catalyst 13.1 have not fixed the issue. I also ran Memtest 86+ v4.20 to check for bad memory but 8 passes show no errors. This problem didn't happen when I was running win xp, only began when I installed windows 8 on 1/13. Any help would be appreciated, because I'm lost at this point.

Thanks,

Beth

WhoCrashed Report:
[FONT=Segoe UI, Arial] System Information (local) [/FONT]
[FONT=Segoe UI, Arial]computer name: FRED
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4292071424 total
VM: 2147352576, free: 1835905024


[/FONT]
[FONT=Segoe UI, Arial] Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 1/21/2013 6:49:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-13416-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003BE9060, 0xFFFFF80068C78920, 0xFFFFFA8003EEE790)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 1/21/2013 6:49:06 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003BE9060, 0xFFFFF80068C78920, 0xFFFFFA8003EEE790)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 1/20/2013 7:22:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-14149-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003BE6060, 0xFFFFF803B1421920, 0xFFFFFA80077A4010)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 1/20/2013 3:29:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011913-29234-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80047B7060, 0xFFFFF8030EFD8920, 0xFFFFFA8003A4E3C0)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 1/19/2013 11:49:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011913-12558-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80047BE060, 0xFFFFF80253C78920, 0xFFFFFA8004425B40)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 1/19/2013 6:05:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011913-16021-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003BE7600, 0xFFFFF802F962C920, 0xFFFFFA80077C4790)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 1/19/2013 4:41:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-13821-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80047B9060, 0xFFFFF8004BB78920, 0xFFFFFA8005EA0010)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 1/19/2013 3:23:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-33243-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80047B9600, 0xFFFFF801FB9B8920, 0xFFFFFA80051C85E0)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 1/18/2013 7:04:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-17737-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003BDE060, 0xFFFFF800E1178920, 0xFFFFFA8008811B40)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 1/17/2013 6:01:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-11918-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003BE3060, 0xFFFFF80085878920, 0xFFFFFA8007473010)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 1/17/2013 3:00:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-14086-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003BDE060, 0xFFFFF8025ED98920, 0xFFFFFA80048F2500)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Wed 1/16/2013 6:00:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-16052-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003BE3600, 0xFFFFF80121878920, 0xFFFFFA8003EA7700)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Wed 1/16/2013 2:34:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011513-11310-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80047BD060, 0xFFFFF803A9C21920, 0xFFFFFA80050215E0)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 1/15/2013 8:20:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011513-10452-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80047B8060, 0xFFFFF800CF421920, 0xFFFFFA80058A8940)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 1/15/2013 2:59:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-11169-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003BE2060, 0xFFFFF8009C698920, 0xFFFFFA8003EF39E0)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]16 crash dumps have been found and analyzed. Only 15 are included in this report. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


[/FONT]
 
Joined
Dec 7, 2011
Messages
829
can you upload the minidump files in the directory shown in those errors? I can help you with those
 

Beth_1987

Thread Starter
Joined
Jan 21, 2013
Messages
20
Thanks for your reply, I am not sure how to find and upload the minidump files. I'm googling how now and will upload as soon as i figure out how!

Beth
 
Joined
Dec 7, 2011
Messages
829
got to C:\Windows\Minidump and put all the files in a zip file and upload it.
 

Beth_1987

Thread Starter
Joined
Jan 21, 2013
Messages
20
Aaron:

I meant that I forgot to say Thank You for your help when I posted the minidump files.
 

Beth_1987

Thread Starter
Joined
Jan 21, 2013
Messages
20
Hello Everyone!

I refreshed windows 8 last night, hoping that would fix my BSOD problem. It didn't.

I ran the windows debugger today and it appears the problem is in the atapi.sys module. I have attached the current minidump file and below is the most recent whocrashed report. Can anyone suggest how to fix this or where I go from here? Thanks.



WhoCrashed:
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Fri 1/25/2013 6:26:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012513-62884-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7B340)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80047A6060, 0xFFFFF801907B8920, 0xFFFFFA8006F81B20)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 1/25/2013 6:26:22 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80047A6060, 0xFFFFF801907B8920, 0xFFFFFA8006F81B20)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/FONT]
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
[/FONT]
 

Attachments

Joined
Dec 7, 2011
Messages
829
whoa! I completely forgot to look at the minidump files! I am doing so right now! Sorry! :(
 
Joined
Dec 7, 2011
Messages
829
I found an exact case of your BSOD. You first should try uninstalling any antivirus.
 

Beth_1987

Thread Starter
Joined
Jan 21, 2013
Messages
20
Hi Aaron:

No problem. Sorry for my late reply, I ran out for a little bit with a couple of friends.

The only antivirus on the machine is the built in windows defender. A quick google indicates it is very difficult to completely remove, so will disabling work or does it have to be completely removed? Thanks.
 
Joined
Dec 7, 2011
Messages
829
windows defender wouldn't cause the problem. It looks like the problem resides with your hard drive. Go to device manager and uninstall the hard drive (but don't check delete device software). Then reboot your computer. If that doesn't work then you will need to find the model of your hard drive.
 

Beth_1987

Thread Starter
Joined
Jan 21, 2013
Messages
20
Aaron,

I have 2 Western Digital 500gb drives:
Drive 1: WD Black WD5003AZEK (Location 0). OS on this one.
Drive 2: WD Blue WD5000AAKX (Location 1). Used for Back up.

Additionally, I have a Kingston DataTraveler SE9 16gb thumb drive plugged into a usb port. I have removed this thumb drive several times to see if it was causing my BSOD on cold boot, but removing it didn't fix the problem.

Which drive do you want me to uninstall? Also, my BSOD error primarily happens on cold boot. Restarts, if the computer is warm, don't trigger it.
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Staff online

Top