Problem when entering sleep

[JordanJP]

My laptop doesn't seem to be able to fully enter sleep mode, the screen will turn blank and then nothing happens for 10 mins. Then the system automatically restarts and when I log into Windows I get the error message stating : Windows has recovered from an error or whatever.

I'm including the DumpFile and I hope someone could find the culprit driver that's causing my system not to enter sleep.


Thanks

 

[zigzag3143]

My laptop doesn't seem to be able to fully enter sleep mode, the screen will turn blank and then nothing happens for 10 mins. Then the system automatically restarts and when I log into Windows I get the error message stating : Windows has recovered from an error or whatever.

I'm including the DumpFile and I hope someone could find the culprit driver that's causing my system not to enter sleep.


Thanks

What OS are you running???

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Mini040210-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x81c4d000 PsLoadedModuleList = 0x81d64c70
Debug session time: Fri Apr  2 12:50:21.201 2010 (GMT-4)
System Uptime: 0 days 0:15:01.978
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 84edc030, 8531d380, 8652f008}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_IRP                                       ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_IRP                                       ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_IRP                                       ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntkrnlpa.exe ( nt+cdb8d )

Followup: MachineOwner
---------

 

[JordanJP]

Vista Home Premium 32Bit

Yes I realize this is 7 forums, and yes I've got Win 7, but I get the same issue on Windows 7, thinking I wouldn't get it on Vista I installed Vista, but I still can't get my laptop to enter sleep mode, even on Vista.

It's obviously a driver issue, but what I want to know is Which DRIVER is causing this ?

Thanks

 

[JordanJP]

here's another dmp file

 

[JordanJP]

I find it odd why the dmp file would report that ?

 

[zigzag3143]

Vista Home Premium 32Bit

Yes I realize this is 7 forums, and yes I've got Win 7, but I get the same issue on Windows 7, thinking I wouldn't get it on Vista I installed Vista, but I still can't get my laptop to enter sleep mode, even on Vista.

It's obviously a driver issue, but what I want to know is Which DRIVER is causing this ?

Thanks

And I would like to tell you, but I cannot because the debugger only has symbols for win 7, so I cant make hide nor hair of the driver situation

 

[zigzag3143]

I find it odd why the dmp file would report that ?

Report what? server?

 

[OppfinnarJocke]

I have a similar problem on my Dell Precision M4400 running W7pro x64.
Occasionally, when I put it to sleep, the screen blanks out but the laptop doesn't really go to sleep, after a few minutes it wakes up. This has happened several times at work, taking the laptop home starts by itself in the bag and when I get home it is hotter than xxxx, the fan running full speed... It happened just today, again. There is no error message or anything when I log on, it's just running... the laptop is docked at work, maybe that has something to do with it...

 

[Klimek]

I have a similar problem on my Dell Precision M4400 running W7pro x64.
Occasionally, when I put it to sleep, the screen blanks out but the laptop doesn't really go to sleep, after a few minutes it wakes up. This has happened several times at work, taking the laptop home starts by itself in the bag and when I get home it is hotter than xxxx, the fan running full speed... It happened just today, again. There is no error message or anything when I log on, it's just running... the laptop is docked at work, maybe that has something to do with it...

I suggest you check this out You cannot make a computer that is running Windows 7 shut down or sleep

That solved the issue I think you're speaking of, for me.