HELP ntoskrnl.exe, ntkrnlmp.exe, win32k.sys


  1. Posts : 59
    Windows 7 64 bit
       #1

    HELP ntoskrnl.exe, ntkrnlmp.exe, win32k.sys


    So here is my crash report via Who crash, if you are having problems I highley recommend this program as it is way easier than the other option, Windows debugging tools,

    On Sat 1/29/2011 5:58:02 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012811-17659-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000319F56D, 0xFFFFF88008976750, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION

    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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Sat 1/29/2011 5:58:02 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: 0x3B (0xC0000005, 0xFFFFF8000319F56D, 0xFFFFF88008976750, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Fri 1/28/2011 8:50:13 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012811-19172-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0xCB511)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF960000FB511, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    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 which cannot be identified at this time.
      My Computer


  2. Posts : 11,840
    64-bit Windows 8.1 Pro
       #2
      My Computer


  3. Posts : 59
    Windows 7 64 bit
    Thread Starter
       #3

    Is Windows 7 . . .
    - x64
    - Yes- an OEM or full retail version?
    - YES OEM = came pre-installed on system
    - Came preloaded on a partition Full Retail = you purchased it from retailer

    - What is the age of system (hardware)? 6 months
    - What is the age of OS installation (have you re-installed the OS?) 6 months
      My Computer


  4. Posts : 13,354
    Windows 7 Professional x64
       #4

    Hello,

    Please run driver verifier: Driver Verifier - Enable and Disable

    Once it has caused a BSOD, upload a new report.

    Also, run Memtest86 overnight: RAM - Test with Memtest86+

    ...Summary of the dumps:
    Code:
    
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sun Jan 30 16:03:38.870 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:23.994
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+6378 )
    BUGCHECK_STR:  0x1a_31
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x1a_31_nt!_??_::NNGAKEGL::_string_+6378
    SystemProductName = CM5675
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat Jan 29 06:23:28.942 2011 (UTC - 5:00)
    System Uptime: 0 days 0:05:17.440
    Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  TrustedInstall
    FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpKcbCacheLookup+1dd
    SystemProductName = CM5675
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Sat Jan 29 00:58:02.077 2011 (UTC - 5:00)
    System Uptime: 0 days 0:13:01.575
    Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  TrustedInstall
    FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpKcbCacheLookup+1dd
    SystemProductName = CM5675
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Fri Jan 28 15:50:13.600 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:28.052
    Probably caused by : win32k.sys ( win32k!xxxSleepThread+81 )
    BUGCHECK_STR:  0x1E_c0000005
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  spoolsv.exe
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_win32k!xxxSleepThread+81
    SystemProductName = CM5675
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
      
    
      My Computer


  5. Posts : 59
    Windows 7 64 bit
    Thread Starter
       #5

    ok I ran verifier and no crash yet, i will keep updated, i will run memtest 86 overnight and get back to you
      My Computer


  6. Posts : 59
    Windows 7 64 bit
    Thread Starter
       #6

    Ok so as soon as this test started it already reported 1,397....2888...3k ahhh 4k it keeps going up now what..
    Failed address 001eaa87ee4 and many others.... Bad error bits like 00020000...
    Last edited by kaoticsolja; 31 Jan 2011 at 22:52.
      My Computer


  7. Posts : 13,354
    Windows 7 Professional x64
       #7

    Looks like the RAM is bad. I suggest you RMA the whole kit, and get a new one in exchange.

    If you feel up to it, you can go through the whole gamut of tests, such as Part 3 of that guide explains. It will probably end up with an RMA anyway though.
      My Computer


  8. Posts : 59
    Windows 7 64 bit
    Thread Starter
       #8

    I just want to say thanks for all the help I have found here! I really appreciate it and now have new ram installed in my pc. Asus did bang up my case a bit but on the whole 10 days isnt to bad to have this error fixed. Thank you again for all your help
      My Computer


  9. Posts : 13,354
    Windows 7 Professional x64
       #9

    Glad to hear that kaoticsolja, thanks for reporting back. Too bad about the dinged up case, but at least it works now!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:13.
Find Us