none
Bluescreen caused by ntoskrnl.exe i think

    Question

  • I have had some bluescreens since i installed Windows 7 Ultimate x64. When i use the WinDbg program with the dump file it say "Probably caused by : ntoskrnl.exe". I have opend all the dump files and all of them say the same.

    The first bluescreen was 14/03-2010. Since then I have had 5 dumpfiles, but i don't know if that is all the bluescreens since the computer was set to overwrite existing files.

    Is there anything I can do to fix the problem or is it something that can't be fixed? If it helps i can upload the dumpfile text.

    Saturday, May 22, 2010 3:17 PM

Answers

All replies

  • Yes, upload the dump file text if you can. A driver may have corrupted some memory before the crash, and Ntoskrnl.exe just tried to use that memory. In that case, depending on the type of bugcheck, it would be a great idea to test your system drivers using Driver Verifier.
    Microsoft MVP Windows Desktop Experience
    Saturday, May 22, 2010 3:32 PM
    Answerer
  • Here is the text from the dumpfile:

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


    Loading Dump File [C:\Windows\Minidump\052210-32385-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`04154500?
    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 \SystemRoot\system32\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 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c55e50
    Debug session time: Sat May 22 14:24:36.763 2010 (UTC + 2:00)
    System Uptime: 0 days 18:02:14.930
    *********************************************************************
    * 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 \SystemRoot\system32\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
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {3, fffffa8004ae2060, fffff80004154518, fffffa8007f55c60}

    ***** 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!TRIAGE_9F_POWER                            ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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!_IO_STACK_LOCATION                         ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                       ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe

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

    And here is the massage that I get after the machine has booted again (it's on Norwegian):

    Problemsignatur:
      Navn på problemhendelse:    BlueScreen
      OS-versjon:    6.1.7600.2.0.0.256.1
      ID for nasjonal innstilling:    1044

    Tilleggsinformasjon om problemet:
      BCCode:    9f
      BCP1:    0000000000000003
      BCP2:    FFFFFA8004ADFA20
      BCP3:    FFFFF80000B9C518
      BCP4:    FFFFFA8004FDB1F0
      OS Version:    6_1_7600
      Service Pack:    0_0
      Product:    256_1

    Filer som bidrar til å beskrive problemet:
      C:\Windows\Minidump\052210-31995-01.dmp
      C:\Users\Ivar\AppData\Local\Temp\WER-157405-0.sysdata.xml

    Tried to run the Driver Verifier, but I don't know how to use it and what to look after. But I got a massage after i had rebooted the computer that no drivers had been changed.

    Saturday, May 22, 2010 8:52 PM
  • Please upload the file   C:\Windows\Minidump\052210-31995-01.dmp to your SkyDrive and post a link here.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Saturday, May 22, 2010 10:57 PM
  • http://cid-a5c0ac83d72f58cd.skydrive.live.com/self.aspx/.Public/052210-31995-01.dmp
    Saturday, May 22, 2010 11:32 PM
  • Hi Ivar,

    your BSOD is caused by the Intel® Wireless WiFi Link Adapter driver ( NETw5s64 .sys). Your driver is from 15th september 2009. Please check if you can get a newer driver for your WLAN device.

    best regards
    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Sunday, May 23, 2010 12:34 AM
  • Thank you,

    I found a newer driver and installed it, ill hope it will work =)

    Sunday, May 23, 2010 10:17 AM