Windows 8 and 8.1 Forums


Help with minidump ntoskrnl.exe problem

  1. #1


    Posts : 63
    Windows 8.1 Pro

    Help with minidump ntoskrnl.exe problem


    Hi everyone,


    Please help with one BSOD. It appeared when tried to start one game.

    This is more about the problem:


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

    Loading Dump File [C:\Windows\Minidump\012515-15078-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff801`05e87000 PsLoadedModuleList = 0xfffff801`06160250
    Debug session time: Sun Jan 25 00:05:01.353 2015 (UTC + 2:00)
    System Uptime: 0 days 21:05:53.792
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................
    Loading User Symbols
    Loading unloaded module list
    ......................................
    ************* Symbol Loading Error Summary **************
    Module name Error
    ntoskrnl The system cannot find the file specified
    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
    You should also verify that your symbol search path (.sympath) is correct.
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff80105f7aaa2, ffffd001525dbb20, 0}
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands 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 : ntoskrnl.exe ( nt+f3aa2 )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80105f7aaa2, Address of the instruction which caused the bugcheck
    Arg3: ffffd001525dbb20, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    Debugging Details:
    ------------------
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands 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 ***
    *** ***
    *************************************************************************
    ADDITIONAL_DEBUG_TEXT:
    You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
    MODULE_NAME: nt
    FAULTING_MODULE: fffff80105e87000 nt
    DEBUG_FLR_IMAGE_TIMESTAMP: 545167e0
    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP:
    nt+f3aa2
    fffff801`05f7aaa2 488b4928 mov rcx,qword ptr [rcx+28h]
    CONTEXT: ffffd001525dbb20 -- (.cxr 0xffffd001525dbb20;r)
    rax=0000000000000056 rbx=ffffe00160ddba60 rcx=43b34880d109a4e8
    rdx=ffffe00160ddba60 rsi=0000000020000000 rdi=70ca87b44a755ef0
    rip=fffff80105f7aaa2 rsp=ffffd001525dc550 rbp=0000000000000004
    r8=fffff801061e2c40 r9=fffff8010618a180 r10=0000000000000001
    r11=fffff78000000008 r12=0000000000000000 r13=0000000000000000
    r14=ffffe0015e85db00 r15=ffffe0015ee4a000
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    nt+0xf3aa2:
    fffff801`05f7aaa2 488b4928 mov rcx,qword ptr [rcx+28h] ds:002b:43b34880`d109a510=????????????????
    Last set context:
    rax=0000000000000056 rbx=ffffe00160ddba60 rcx=43b34880d109a4e8
    rdx=ffffe00160ddba60 rsi=0000000020000000 rdi=70ca87b44a755ef0
    rip=fffff80105f7aaa2 rsp=ffffd001525dc550 rbp=0000000000000004
    r8=fffff801061e2c40 r9=fffff8010618a180 r10=0000000000000001
    r11=fffff78000000008 r12=0000000000000000 r13=0000000000000000
    r14=ffffe0015e85db00 r15=ffffe0015ee4a000
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    nt+0xf3aa2:
    fffff801`05f7aaa2 488b4928 mov rcx,qword ptr [rcx+28h] ds:002b:43b34880`d109a510=????????????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x3B
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER: from ffffe00160ddba60 to fffff80105f7aaa2
    STACK_TEXT:
    ffffd001`525dc550 ffffe001`60ddba60 : 00000000`00000000 00000000`00000000 ffffe001`5e7c97b0 00000000`20000000 : nt+0xf3aa2
    ffffd001`525dc558 00000000`00000000 : 00000000`00000000 ffffe001`5e7c97b0 00000000`20000000 00000000`00000004 : 0xffffe001`60ddba60

    FOLLOWUP_IP:
    nt+f3aa2
    fffff801`05f7aaa2 488b4928 mov rcx,qword ptr [rcx+28h]
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: nt+f3aa2
    FOLLOWUP_NAME: MachineOwner
    IMAGE_NAME: ntoskrnl.exe
    STACK_COMMAND: .cxr 0xffffd001525dbb20 ; kb
    BUCKET_ID: WRONG_SYMBOLS
    FAILURE_BUCKET_ID: WRONG_SYMBOLS
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:wrong_symbols
    FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
    Followup: MachineOwner
    ---------
    0: kd> g
    ^ No runnable debuggees error in 'g'


    I have and another problem. If this BSOD has something common:
    BSOD - KERNEL_DATA_INPAGE_ERROR - Win 8.1

    Thanks in advance!

      My System SpecsSystem Spec

  2. #2


    Posts : 2,480
    Windows 10 Pro x64


    Upload the minidumps.
      My System SpecsSystem Spec

  3. #3


    Posts : 63
    Windows 8.1 Pro

    Attaching Debug information


    Quote Originally Posted by softwaremaniac View Post
    Upload the minidumps.

    This is my minidump.
    Thank you in advance!
      My System SpecsSystem Spec

  4. #4


    Posts : 2,480
    Windows 10 Pro x64


    There is a lot of stuff going on here. You have both Nvidia and AMD software installed. Please remove them using DDU and install the ones you currently have. Update the rest of the drivers in red.
    Code:
    usbVM31b.sys Mon Sep 19 08:57:34 2005  (432E615E) 
    
    usbVM31b.sys - this driver hasn't been added to the DRT as  of this run. Please search Google/Bing for the driver if additional information  is needed. 
    
    usbfilter.sys Wed Aug 29 03:27:12 2012 (503D6FF0)  
    AMD USB Filter Driver (likely part of the chipset drivers) 
    http://www.carrona.org/drivers/driver.php?id=usbfilter.sys 
    
    AODDriver2.sys Wed Nov 21 08:44:04 2012 (50AC8644)  
    AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7[br][br]Part of AMD Fuel[br][br]Location:  C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys 
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys 
    
    Rt630x64.sys Fri Jun 21  11:29:10 2013 (51C41CE6) 
    Realtek PCI/PCIe Adapters 
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys 
    
    amd_sata.sys Fri Jun 28 06:45:40  2013 (51CD14F4) 
    AMD SATA Controller AHCI 1.2 Device Driver 
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys 
    
    amd_xata.sys Fri Jun 28 06:45:43  2013 (51CD14F7) 
    AMD Stor Filter Driver 
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys 
    
    tap0901.sys Thu Aug 22 14:40:01  2013 (521606A1) 
    TAP-Win32 Adapter V9 or[br]OpenVPN driver or COMODO 
    http://www.carrona.org/drivers/driver.php?id=tap0901.sys 
    
    RTKVHD64.sys Tue Dec 3 13:26:10  2013 (529DCDE2) 
    Realtek High Definition Audio Function Driver 
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys 
    
    nvhda64v.sys Thu Oct 9 19:02:27  2014 (5436BFA3) 
    nVidia HDMI Audio Device (nForce chipset driver) 
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys 
    
    nvvad64v.sys Thu Nov 20 16:33:54  2014 (546E09E2) 
    NVIDIA Virtual Audio Driver 
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys 
    
    NvStreamKms.sys Sat Nov 22 08:46:45 2014 (54703F65)  
    nVidia Streaming Kernel service - may cause BSOD in  Win8.1 systems (found in May 2014). Date/TimeStamp: Tue Apr 29 20:59:44 2014  (53604B00) MAY NOT BE A PROBLEM, this is a tenative posting - Appears that  April 29 driver is a problem, July 2014 drivers seem OK 
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys 
    
    nvlddmkm.sys Sat Dec 13  07:53:17 2014 (548BE25D) 
    nVidia Video drivers 
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys 
    
    nvstusb.sys Sat Dec 13 08:30:38  2014 (548BEB1E) 
    NVIDIA Stereoscopic 3D USB driver 
    http://www.carrona.org/drivers/driver.php?id=nvstusb.sys 
    
    
    
    Debug session time: Sat  Jan 24 23:05:01.353 2015 (UTC + 1:00) 
    Loading Dump File  [C:\Users\Mihael\SysnativeBSODApps\012515-15078-01.dmp] 
    Built by:  9600.17476.amd64fre.winblue_r5.141029-1500 
    System Uptime: 0 days  21:05:53.792 
    *** WARNING: Unable to verify timestamp for nvstusb.sys 
    ***  ERROR: Module load completed but symbols could not be loaded for nvstusb.sys  
    Probably caused by : nvstusb.sys ( nvstusb+a56c ) 
    BugCheck 3B,  {c0000005, fffff80105f7aaa2, ffffd001525dbb20, 0} 
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION  (3b) 
    Bugcheck code 0000003B 
    Arguments: 
    Arg1: 00000000c0000005,  Exception code that caused the bugcheck 
    Arg2: fffff80105f7aaa2, Address of  the instruction which caused the bugcheck 
    Arg3: ffffd001525dbb20, Address of  the context record for the exception that caused the bugcheck 
    Arg4:  0000000000000000, zero. 
    BUGCHECK_STR: 0x3B 
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT 
    PROCESS_NAME: fifa14.exe 
    FAILURE_BUCKET_ID:  0x3B_nvstusb+a56c 
    BiosVersion = F3i 
    BiosReleaseDate = 10/07/2014  
    SystemManufacturer = Gigabyte Technology Co., Ltd. 
    SystemProductName =  To be filled by O.E.M.  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    
    
    
    
    --- E O J --- 2015 Jan 25 22:41:22 PM _88-dbug Copyright  2012 Sysnative Forums 
    --- E O J --- 2015 Jan 25 22:41:22 PM _88-dbug  Copyright 2012 Sysnative Forums 
    --- E O J --- 2015 Jan 25 22:41:22 PM  _88-dbug Copyright 2012 Sysnative Forums
      My System SpecsSystem Spec

  5. #5


    Posts : 63
    Windows 8.1 Pro


    Yes. I know, but I installed AMD after the problem. because I tried to install mobo chipset driver. They installed this software - Catalyst.
      My System SpecsSystem Spec

  6. #6


    Posts : 2,480
    Windows 10 Pro x64


    They couldn't have because chipset drivers are something different than Catalyst (GPU drivers control center). Download 3DP Chip and let it tell you if any drivers are outdated. If there are, update them.
      My System SpecsSystem Spec

  7. #7


    Posts : 63
    Windows 8.1 Pro


    Please tell me about this drivers. First two is for the AMD, isn't it? You advice me to uninstall? And the third is Nvidia driver. How to update? I am with the latest NVIDIA drivers. May there is another way?
    And where is my mobo chipset drivers? I am downloaded them from the manufacturer site, but installed me this ATI Catalyst.
      My System SpecsSystem Spec

  8. #8


    Posts : 63
    Windows 8.1 Pro


    I didn't saw your first reply, but please answer me for the other questions. And if you thing that is the problem from the minidump - drivers? Anything else?
      My System SpecsSystem Spec

  9. #9


    Posts : 2,480
    Windows 10 Pro x64


    For now, focus is on the drivers. Download 3DP Chip. It will tell you which drivers need to be updated, and remove AMD drivers completely, please.
      My System SpecsSystem Spec

  10. #10


    Posts : 63
    Windows 8.1 Pro


    OK, I downloaded. Can I trust 3DP, if tells me that there are newer drivers for GPU, but NVIDIA site gives me another?
    And , please, if you have time - could you see this my thread. A have other problem, may be different from this BSOD:
    BSOD - KERNEL_DATA_INPAGE_ERROR - Win 8.1
    To tell me did you see in the minidump something suspicious and common with this problem.
    Thank you in advance!
      My System SpecsSystem Spec

Page 1 of 11 123 ... LastLast
Help with minidump ntoskrnl.exe problem
Related Threads
i recently upgraded from windows 8 to 8.1... when i use my lap it suddenly change into a bluescreen "pc ran into a problem" and the error is "bad pool caller,header".... when i further investigate the crash is "ntoskrnl.exe"... i attached the system information withthis .... please help to...
Heya! Ive been having these bluescreens from time to time mostly every other day. I get a different "crash" everytime KMODE_EXCEPTION_NOT_HANDLED DRIVER_OVERRAN_STACK_BUFFER IRQL_NOT_LESS_OR_EQUAL_ BAD_POOL_HEADER
Minidump help in BSOD Crashes and Debugging
Hi there, I hope I'm not breaking the rules here but I'm in a tight spot. All I have is a minidump file from a computer, which randomly crashes and displays 'Driver Power State Failure'. This is all I've got to go with so, can anyone help me decipher the minidump file? I need to have it fixed for...
minidump freeze in BSOD Crashes and Debugging
Hello All, I am getting a similar problem to a lot of the posts here. am running Win8 Intel Quad Core Q6600. PC either doesn't boot or crashes shortly after. 3 main messages I get are listed below Can anyone help?...
Minidump and sysdata pb in BSOD Crashes and Debugging
Hello, I've just bought a new computer (Sony VAIO SVE1112) running with Windows 8. I've downloaded Firefox 19.0. When I'm using IE or Firefox, after few minutes, the PC disconnect and restart. It sends informations :
BSOD with minidump files in BSOD Crashes and Debugging
My computer crashed after it went into sleep mode; it has experienced multiple similar crashes over the past two weeks.
Eight Forums Android App Eight Forums IOS App Follow us on Facebook