Windows 7 does an unexpected shutdown while attempting to go to sleep

Toggle sidebar Toggle sidebar
Status
Not open for further replies.
J

JoshGinter

Honorable
Jul 19, 2014
6
0
10,510
I built my PC about 6 years ago, but earlier this year I did a couple upgrades. I swapped my E8400 out for a Q9450 that my friend gave me and I swapped my old HDD out for a Samsung 840 EVO SSD. The new build works incredibly well except for this one issue: about 20% of the times I attempt to put it to sleep (rough estimate, and it'll occassionally go long spurts without the problem cropping up at all). Before the upgrade I had this issue happen maybe 3 or 4 times ever but never as often as in the last 2 months. Does anyone know what could be causing this issue? I can post any logs or additional info that might help. I just don't know what would be relevant.

Right before I posted I looked at my event log and noticed that the computer does appear to get to sleep, but then it wakes up from an unknown source seconds later, experiences some sort of error and restarts itself. I've attached all the events that happened during this time period.
 
Solution
Lutfij
Remove all the info regarding the errors past the "...period." and install Whocrashed onto your system. After which run it and post your results.

Furthermore you shouldn't even have the system go into sleep since it affects your ssd negatively. In your power options, please set "never" on the option to turn off your HDD.
Sort by date Sort by votes
Lutfij

Lutfij

Titan
Moderator
Oct 7, 2009
54,000
4,724
173,390
Remove all the info regarding the errors past the "...period." and install Whocrashed onto your system. After which run it and post your results.

Furthermore you shouldn't even have the system go into sleep since it affects your ssd negatively. In your power options, please set "never" on the option to turn off your HDD.
 
Upvote 0 Downvote
Solution
J

JoshGinter

Honorable
Jul 19, 2014
6
0
10,510


On Sat 7/19/2014 8:22:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071914-31808-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41287, 0x4E01800, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 7/19/2014 8:22:57 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41287, 0x4E01800, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 7/11/2014 5:58:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071114-10233-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80050D2A10, 0xFFFFF800040C0518, 0xFFFFFA8006D5AAA0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.



On Tue 6/3/2014 9:30:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060314-15397-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x16F4B)
Bugcheck code: 0xFE (0x4, 0xFFFFFA800776DB10, 0xFFFFFA8007E33C10, 0xFFFFFA8008B9A460)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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 that cannot be identified at this time.



On Mon 5/19/2014 10:48:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-10233-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80050DDA10, 0xFFFFF80000B9C518, 0xFFFFFA8006FD0DC0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.



On Sun 5/11/2014 5:42:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051014-10077-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x64F57)
Bugcheck code: 0xD1 (0xFFFFF8810EE29AD8, 0x2, 0x1, 0xFFFFF88001865F57)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 that cannot be identified at this time.



On Sun 5/4/2014 9:51:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050414-9640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800511E060, 0xFFFFF800040BF518, 0xFFFFFA80088584E0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.



On Thu 5/1/2014 9:18:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050114-9578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80050DF060, 0xFFFFF80000B9C518, 0xFFFFFA8005CA0200)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.



On Fri 4/25/2014 8:06:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042514-8876-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8005100A10, 0xFFFFF80000B9C518, 0xFFFFFA8008188C60)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.



On Tue 4/22/2014 11:12:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042214-9828-01.dmp
This was probably caused by the following module: srvnet.sys (srvnet+0x908C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005ABE08C, 0xFFFFF88008A96E30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\srvnet.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Server Network driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.

I included all the crash dumps it could find. I believe they all manifested as being the same basic thing I described in the original post... but maybe one was during a game... The 7/19 one is the most recent and caused the "unexpected shutdown while trying to sleep" issue.

Could you please provide a link or describe in detail the reasoning behind your second paragraph?
 
Upvote 0 Downvote
J

JoshGinter

Honorable
Jul 19, 2014
6
0
10,510




I've read through all sections of that guide regarding sleep and hibernation and there doesn't appear to be any mention of it "affecting your ssd negatively". Relevant pieces:
I recommend at least setting to high performance, as for laptops it is up to you, I would leave the default for a laptop. This step is so that Idle Time Garbage Collection can run for your SSD if you have one when the system is at idle rather than going to sleep and you get more performance out of your system just by setting it to high performance. But feel free to set it up however you like.
Click to expand...
Turning off auto-sleep improve's performance which is a rather obvious, but no mention of there being negative affects other than "lower performance". Either way I've had these settings that way since day 1. The issue crops up when I put my computer to sleep manually.
If you don't use hibernation mode, disabling it will save you several GB of disk space. If you do use hibernation mode, you can still shrink the hibernation file size. I say to do it at this point if you want to b/c it prevents extra writes as well. Also, hibernation is different than the normal sleep mode. However, it can allow you to have hybrid sleep when it is enabled.
Click to expand...
This is good advice in general as avoiding unnecessary writes to the SSD is good practice as it will lower the overall lifespan of the drive. And getting that additional disk space back has all sorts of benefits. However, I pretty much subscribe to the theory that my SSD will be far beyond its point of obsolescence before the life-span issue become worth considering. And again this doesn't actually appear to be relevant to my problem (at least I don't think so?) But I will go about turning that feature off.
 
Upvote 0 Downvote
Lutfij

Lutfij

Titan
Moderator
Oct 7, 2009
54,000
4,724
173,390
Considering that an SSD per GB is much more expensive than a platter drive every bit of longevity you can scrape off the device is a plus for you. Given that you work on a laptop/mobile device, it should at least be reliable when you need it to be.

GB written and or stored on an SSD is a performance hit. In fact try filling your ssd with data to the brim, you'll notice considerable performance drops.
 
Upvote 0 Downvote
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom