black screen when coming out of sleep mode Results

Sponsored Links:

Hello all;

For the past several mornings, when clicking my mouse to wake my PC from sleep mode, my screen remains completely black. I can hear the PC start up, the fan running, etc. I can even hear the Windows log on sound when I punch in my password. All power lights are on, but the monitor refuses to display anything, not even a blinking cursor.

My keyboard then becomes unresponsive and I'm unable to shut my PC down using the power button. I've had to hard reboot several times by manually switching my surge protector off and on. After getting the expected message that Windows didn't shut down properly, my system then starts up as usual.

I have Windows 7 Home Premium (64 bit). My processor is an AMD Athlon II X4 630 and I have 6 GB of RAM. Both my PC and monitor are brand new. I would greatly appreciate any advice. Thank you.

Hello Everyone,
I'm hoping you all can help me out with some recent BS OD problems I've been having lately. FYI, I'm running 64-bit Windows 7 Professional Edition SP 1 w 12 GB of RAM. This problem has been going on for about a week now and seems to usually happen after the computer comes out of sleep mode or at least that's when I've actually witnessed the crashes. What happens is, a few seconds after the PC wakes up, the screen displays a sort of checkerboard pattern of various colors but I can still see some of the text/graphics that had been on the display in the background. This pattern will display for a few seconds before the computer reboots itself and after rebooting prompts me with the message that Windows did not shut down properly and offers to check online for a solution. It also offers the advanced option which lists the minidump file name and location as well as a .XML file name.

The first few times this happened I clicked the icon to check for an online solution, found nothing and otherwise foolishly ignored the crash. A few days ago, I came into my room to the PC which had been on for a while and noticed the screen was black except for the text "missing operating system". I turned the PC off then back on again with the power button but got the same missing operating system message. I did this a few more times and after the third try the PC booted and displayed the message that Windows did not shut down correctly and gave me the option to boot up in safe mode, safe mode with networking, etc. I booted into safe mode, backed up my data and rebooted again. I googled debugging minidump files and followed the instructions on the webpage How to Debug Kernel Mode Blue Screen Crashes (for beginners) - Ask the Core Team - Site Home - TechNet Blogs and displayed the results below. I see in the output that it mentions natspeak.exe, that's Dragon NaturallySpeaking which I use just about every day, could that have been causing all those BS OD's? Any idea why I got the missing operating system error message? I performed a chkdsk and no bad sectors were found and no other messages appeared that would indicate problems with the hard drive. Thanks in advance for any info you can provide.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:WindowsMinidump82911-14414-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e68000 PsLoadedModuleList = 0xfffff800`030ad670
Debug session time: Mon Aug 29 12:25:40.738 2011 (UTC - 4:00)
System Uptime: 1 days 0:28:32.689
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff800031a848b, fffff88006c0f070, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption

0: kd> !analyze -v
* *
* Bugcheck Analysis *
* *

An exception happened while executing a system service routine.
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff800031a848b, Address of the instruction which caused the bugcheck
Arg3: fffff88006c0f070, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

nt! ?? ::NNGAKEGL::`string'+e8a1
fffff800`031a848b 0e ???

CONTEXT: fffff88006c0f070 -- (.cxr 0xfffff88006c0f070)
rax=0000000000000001 rbx=0000000000000000 rcx=fffff8a0011d6d60
rdx=fffff8a01c170a01 rsi=fffffa800e2b8150 rdi=fffffa800e2b8160
rip=fffff800031a848b rsp=fffff88006c0fa50 rbp=fffffa800e2b8130
r8=fffff8a01c170a00 r9=0000000000000030 r10=fffff8000305c3c0
r11=fffff8a019e57a90 r12=fffff8a0011d6d60 r13=fffff80002e68000
r14=000000000008ec00 r15=fffff8a00364b840
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt! ?? ::NNGAKEGL::`string'+0xe8a1:
fffff800`031a848b 0e ???
Resetting default scope




PROCESS_NAME: NatSpeak.exe


LAST_CONTROL_TRANSFER: from fffff800031dc12d to fffff800031a848b

fffff880`06c0fa50 fffff800`031dc12d : 00000000`00000000 fffffa80`0a17da00 fffffa80`0e2b8150 fffffa80`09d5b401 : nt! ?? ::NNGAKEGL::`string'+0xe8a1
fffff880`06c0fac0 fffff800`031dbf31 : 00000000`00000000 fffffa80`00000000 fffff8a0`0364b840 00000000`00000000 : nt!ObpDecrementHandleCount+0x6d
fffff880`06c0fb40 fffff800`031dc4f4 : 00000000`00000774 fffffa80`0a17da00 fffff8a0`0364b840 00000000`00000774 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`06c0fbd0 fffff800`02ee3ed3 : fffffa80`09e03b60 fffff880`06c0fca0 00000000`fffdb000 00000000`fffdb000 : nt!ObpCloseHandle+0x94
fffff880`06c0fc20 00000000`7785140a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e318 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7785140a

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff800031a848b - nt! ?? ::NNGAKEGL::`string'+e8a1
[ 0f:0e ]
1 error : !nt (fffff800031a848b)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption



STACK_COMMAND: .cxr 0xfffff88006c0f070 ; kb



Followup: memory_corruption

My laptop will no longer shut down, hibernate, or sleep.

When I choose to shut down the window sits at logging off, and will not change.
When I chose to hibernate/sleep it will sit at a black screen, but do nothing more. The fan still blows hard, and it will not come out of the "hibernate/sleep"

I am using Windows 7 Home Premium(64 bit) and my specs are:

Version: 6.1.7600 Build 7600
Model: HP Pavilion dv5 Notebook PC
Manufacturer: Hewlett-Packard
Processor: Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz 2.00GHz
Ram: 4.00 GB
64-bit operating system

Also, my computer will successfully shut down when I am running it in safe mode (which I am doing now, with networking enabled).

Thanks in advance for the help, and I'm no whiz when it comes to computers, so if I am missing any information just tell me.

EDIT: I just remembered I had this issue when I first installed Windows 7. Then after a 2 days it started to work properly. Now it has started again, but this time it has continued for about 5 days.

I did a full install of Ubuntu 10.10 to a Seagate external HDD. When I say full install I mean running the installer and fully installing 10.10 to the drive, NOT using Universal USB installer and putting the live CD on a thumbdrive.

The install went well and Ubuntu boots and runs perfectly. The problem I'm having is coming out of standby/sleep mode. Ubuntu enters standby/sleep no problem but when I open the lid of my laptop the computer wakes and starts running but all I get is a black screen and a cursor. I have to do a hard restart to get out of this.

Any suggestions as to what would cause this? It's happening on all machines that I boot from so I can rule out a hard ware issue with a specific machine.