Missing operating system error message after BS OD

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Quadzilla, Aug 31, 2011.

  1. Quadzilla

    Quadzilla New Member

    Feb 13, 2011
    Likes Received:
    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:\Windows\Minidump\082911-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
  2. zigzag3143

    zigzag3143 Honorable Member
    Microsoft MVP

    Jun 2, 2009
    Likes Received:
    2 people like this.
  3. Elmer

    Elmer Extraordinary Member

    Mar 5, 2010
    Likes Received:
    Hi Quadzilla and Welcome to The Forum.

    Memory_Corruption usually indicates out of date Drivers, Bad Memory or incorrectly configured Memory Timings.

    We really need the dmp file for analysis.

    To ensure minidumps are enabled:
    Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    Under the Advanced tab, click on the Startup and Recovery Settings... button.
    Ensure that Automatically restart is unchecked.
    Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    OK your way out.
    Reboot if changes have been made.

    The .dmp files are located at C:\Windows\Minidump. Until a .dmp file is generated, the Minidump folder may not exist.

    Go to your C:\Windows\Minidump folder. Copy the .dmp files to a new folder on your desktop. Zip up that folder and attach to a post.

    Damn that fast fingered zigzag!!
    1 person likes this.
  4. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Oct 16, 2009
    Likes Received:
    Just in case it might be related to Dragon, what version are you using, and have you checked for any updates lately?

Share This Page