ntoskrnl.exe BSOD need help

Discussion in 'General Hardware' started by kenjishinoda, Mar 11, 2012.

  1. kenjishinoda

    kenjishinoda Active Member

    Messages:
    92
    Likes Received:
    0
    GPU:
    SAPPHIRE 6870
    this is the first time i've encountered a weird problem like this. it first occurred right after I saved an image on paint, after I named the file and hit "save", my mouse pointer suddenly became sluggish and very slow. After a few seconds, my comp just restarted itself automatically, and then gave me a BSOD error result after the restart.

    the next BSOD happened while I was playing KOA - Reckoning. I was just listening to a character dialogue and then everything froze, comp restarted automatically, and gave a BSOD error after restart.

    I wanted to know what might have caused this BSOD problem, so I did a memory test and a hard drive test, but there were no errors. I also downloaded a "blue screen viewer" software that helped me detect the causes of BSOD's, and I found out that it was caused by the file called "ntoskrnl.exe" I do not know how to fix that, I hope someone can help me.

    After those 2 BSOD's, I was just playing Reckoning again today and was using fraps, and then my comp was completely frozen. There was no automatic restart however, just a complete lockup and it needed a forced restart.

    Here's one weird thing that also happened. I wanted to change my headset to another one while I was about to watch a youtube video, then right after I plugged the 3.55mm jack into the front panel, my comp restarted right away, and then gave another BSOD error after restart which was caused by "ntoskrnl.exe" again. What the hell was that? What could be the cause of all these?

    i'm using the latest amd drivers, realtek hd audio driver R267. I'm also uploading my BSOD .dmp files with the "blue screen viewer", and my DXDIAG

    BSOD .dmp files with "blue screen viewer" software: http://www.mediafire.com/?0rdlh13qdd4p9ke

    DXDIAG: http://www.mediafire.com/?68os3z5zmx07mm8

    P.S. i forgot to mention that i've recently been using the software called sapphire trix to make a custom fan profile, could it also be caused by software?
     
    Last edited: Mar 11, 2012
  2. Portal2Two

    Portal2Two Banned

    Messages:
    27
    Likes Received:
    0
    GPU:
    AMD 6970
    Yes, overheating can cause stop 0x124.

    --------------------------------------------

    Both your crash dumps show this:

    WHEA_UNCORRECTABLE_ERROR (124)
    0x124_AuthenticAMD
    A fatal hardware error has occurred.


    Possible causes:

    - faulty hardware needing replacement
    - wrong bios settings
    - overclocking
    - overheating


    Troubleshooting:

    - reset bios (you might wanna try bios upgrade which sometimes helps )
    - 8 passes of memtest
    - a few hours of prime95
    - watch for temperatures not to go higher than allowed


    Code:
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [H:\DMP\031012-15319-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*h:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`03e17000 PsLoadedModuleList = 0xfffff800`0405c670
    Debug session time: Sat Mar 10 10:37:59.800 2012 
    System Uptime: 0 days 0:00:08.470
    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
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8004cf1038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    FAULTING_MODULE: fffff80003e17000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`031bd6f0 fffffa80`04cf1038 : 00000000`00000001 00000000`00000000 fffffa80`04d9b020 fffffa80`04cf1038 : nt+0x4b16cc
    fffff880`031bd6f8 00000000`00000001 : 00000000`00000000 fffffa80`04d9b020 fffffa80`04cf1038 00000000`00000000 : 0xfffffa80`04cf1038
    fffff880`031bd700 00000000`00000000 : fffffa80`04d9b020 fffffa80`04cf1038 00000000`00000000 00000000`00000000 : 0x1
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [H:\DMP\031112-14726-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*h:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`03e63000 PsLoadedModuleList = 0xfffff800`040a8670
    Debug session time: Sun Mar 11 15:36:37.771 2012 
    System Uptime: 0 days 0:00:07.456
    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
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8004d498f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    FAULTING_MODULE: fffff80003e63000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`031a86f0 fffffa80`04d498f8 : 00000000`00000001 00000000`00000000 fffffa80`04d0b4f0 fffffa80`04d498f8 : nt+0x4b16cc
    fffff880`031a86f8 00000000`00000001 : 00000000`00000000 fffffa80`04d0b4f0 fffffa80`04d498f8 00000000`00000000 : 0xfffffa80`04d498f8
    fffff880`031a8700 00000000`00000000 : fffffa80`04d0b4f0 fffffa80`04d498f8 00000000`00000000 00000000`00000000 : 0x1
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    Followup: MachineOwner
    ---------
    
    start             end                 module name
    fffff880`00eca000 fffff880`00f21000   ACPI     ACPI.sys     Sat Nov 20 11:19:16 2010 (4CE79294)
    fffff880`00c2a000 fffff880`00c35000   amdxata  amdxata.sys  Fri Mar 19 18:18:18 2010 (4BA3A3CA)
    fffff880`00de4000 fffff880`00ded000   atapi    atapi.sys    Tue Jul 14 02:19:47 2009 (4A5BC113)
    fffff880`00c00000 fffff880`00c2a000   ataport  ataport.SYS  Sat Nov 20 11:19:15 2010 (4CE79293)
    fffff880`01680000 fffff880`01688000   AtiPcie  AtiPcie.sys  Mon Aug 24 11:25:26 2009 (4A924E76)
    fffff880`00cba000 fffff880`00d7a000   CI       CI.dll       Sat Nov 20 15:12:36 2010 (4CE7C944)
    fffff880`01650000 fffff880`01680000   CLASSPNP CLASSPNP.SYS Sat Nov 20 11:19:23 2010 (4CE7929B)
    fffff880`00c5c000 fffff880`00cba000   CLFS     CLFS.SYS     Tue Jul 14 02:19:57 2009 (4A5BC11D)
    fffff880`01000000 fffff880`01072000   cng      cng.sys      Thu Nov 17 06:23:17 2011 (4EC48C35)
    fffff880`01688000 fffff880`01696000   crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD)
    fffff880`0163a000 fffff880`01650000   disk     disk.sys     Tue Jul 14 02:19:57 2009 (4A5BC11D)
    fffff880`016a2000 fffff880`016ab000   dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
    fffff880`01696000 fffff880`016a2000   dump_ataport dump_ataport.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
    fffff880`016ab000 fffff880`016be000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
    fffff880`0113b000 fffff880`0114f000   fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481)
    fffff880`010ef000 fffff880`0113b000   fltmgr   fltmgr.sys   Sat Nov 20 11:19:24 2010 (4CE7929C)
    fffff880`01211000 fffff880`0121b000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 02:19:45 2009 (4A5BC111)
    fffff880`01600000 fffff880`0163a000   fvevol   fvevol.sys   Sat Nov 20 11:24:06 2010 (4CE793B6)
    fffff880`018ec000 fffff880`01936000   fwpkclnt fwpkclnt.sys Sat Nov 20 11:21:37 2010 (4CE79321)
    fffff800`03e1a000 fffff800`03e63000   hal      hal.dll      Sat Nov 20 15:00:25 2010 (4CE7C669)
    fffff880`019e6000 fffff880`019ef000   hwpolicy hwpolicy.sys Sat Nov 20 11:18:54 2010 (4CE7927E)
    fffff800`00bbb000 fffff800`00bc5000   kdcom    kdcom.dll    Sat Feb 05 18:52:49 2011 (4D4D8061)
    fffff880`013d7000 fffff880`013f2000   ksecdd   ksecdd.sys   Thu Nov 17 05:48:13 2011 (4EC483FD)
    fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Thu Nov 17 06:23:44 2011 (4EC48C50)
    fffff880`00c3b000 fffff880`00c48000   mcupdate mcupdate.dll Tue Jul 14 04:29:09 2009 (4A5BDF65)
    fffff880`00d7a000 fffff880`00d94000   mountmgr mountmgr.sys Sat Nov 20 11:19:21 2010 (4CE79299)
    fffff880`00f2a000 fffff880`00f34000   msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE)
    fffff880`0114f000 fffff880`011ad000   msrpc    msrpc.sys    Sat Nov 20 11:21:56 2010 (4CE79334)
    fffff880`019d4000 fffff880`019e6000   mup      mup.sys      Tue Jul 14 02:23:45 2009 (4A5BC201)
    fffff880`014ae000 fffff880`015a1000   ndis     ndis.sys     Sat Nov 20 11:23:30 2010 (4CE79392)
    fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Sat Nov 20 11:23:13 2010 (4CE79381)
    fffff800`03e63000 fffff800`0444c000   nt       ntoskrnl.exe Thu Jun 23 05:53:23 2011 (4E02AAA3)
    fffff880`01234000 fffff880`013d7000   Ntfs     Ntfs.sys     Fri Mar 11 05:39:39 2011 (4D79997B)
    fffff880`00f74000 fffff880`00f89000   partmgr  partmgr.sys  Sat Nov 20 11:20:00 2010 (4CE792C0)
    fffff880`00f34000 fffff880`00f67000   pci      pci.sys      Sat Nov 20 11:19:11 2010 (4CE7928F)
    fffff880`00e00000 fffff880`00e07000   pciide   pciide.sys   Tue Jul 14 02:19:49 2009 (4A5BC115)
    fffff880`00e07000 fffff880`00e17000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 02:19:48 2009 (4A5BC114)
    fffff880`01200000 fffff880`01211000   pcw      pcw.sys      Tue Jul 14 02:19:27 2009 (4A5BC0FF)
    fffff880`00c48000 fffff880`00c5c000   PSHED    PSHED.dll    Tue Jul 14 04:32:23 2009 (4A5BE027)
    fffff880`0199a000 fffff880`019d4000   rdyboost rdyboost.sys Sat Nov 20 11:43:10 2010 (4CE7982E)
    fffff880`01992000 fffff880`0199a000   spldr    spldr.sys    Mon May 11 19:56:27 2009 (4A0858BB)
    fffff880`016e8000 fffff880`018ec000   tcpip    tcpip.sys    Thu Sep 29 06:43:04 2011 (4E83E948)
    fffff880`00f67000 fffff880`00f74000   vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB)
    fffff880`00d94000 fffff880`00dd0000   vmbus    vmbus.sys    Sat Nov 20 11:57:29 2010 (4CE79B89)
    fffff880`01936000 fffff880`01946000   vmstorfl vmstorfl.sys Sat Nov 20 11:57:30 2010 (4CE79B8A)
    fffff880`00f89000 fffff880`00f9e000   volmgr   volmgr.sys   Sat Nov 20 11:19:28 2010 (4CE792A0)
    fffff880`00f9e000 fffff880`00ffa000   volmgrx  volmgrx.sys  Sat Nov 20 11:20:43 2010 (4CE792EB)
    fffff880`01946000 fffff880`01992000   volsnap  volsnap.sys  Sat Nov 20 11:20:08 2010 (4CE792C8)
    fffff880`00e17000 fffff880`00ebb000   Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F)
    fffff880`00ebb000 fffff880`00eca000   WDFLDR   WDFLDR.SYS   Tue Jul 14 02:19:54 2009 (4A5BC11A)
    fffff880`00dd0000 fffff880`00de4000   winhv    winhv.sys    Sat Nov 20 11:20:02 2010 (4CE792C2)
    fffff880`00f21000 fffff880`00f2a000   WMILIB   WMILIB.SYS   Tue Jul 14 02:19:51 2009 (4A5BC117)
    Mini Kernel Dump does not contain unloaded driver list
    
    
     
  3. kenjishinoda

    kenjishinoda Active Member

    Messages:
    92
    Likes Received:
    0
    GPU:
    SAPPHIRE 6870
    Thanks for your feedback Portal2Two. It's probably not overclocking, because I do not OC most of the time. The only time I OC is when I have to convert a video. I OC my CPU whenevever I do that, but I only change the multiplier to 19 (using vtune), I do not OC anything else. Then after the video conversion is done, I would reset it back to default speed. Also, I rarely have BSODs when I do that.

    It's also probably not overheating, because I monitor my temps all the time. I think the highest temp my cpu has reached is 62C, and my graphics card's highest temp is 87C. Those are the usual readings on the warmest temperatures in my room (no air-conditioner and summer temp/summer season).

    Right now I feel that it might be faulty hardware just like you mentioned, because...

    how do you explain the BSOD that occurred right after I plugged in my headphones on the front panel???

    I did an extensive memory diagnostic test last night, and found no errors.
     
  4. Portal2Two

    Portal2Two Banned

    Messages:
    27
    Likes Received:
    0
    GPU:
    AMD 6970
    Right, faulty jack or cord of a peripheral device can give you blue screens as well, but in such cases you would get something like stop 0x50, stop xa, etc., typically with a reference to that peripheral device driver. Not 0x124_AuthenticAMD as in your case. Besides, you had mentioned freezes and blue screens other than only when plugging in your headphones.

    "... my mouse pointer suddenly became sluggish and very slow. After a few seconds, my comp just restarted itself automatically, and then gave me a BSOD error result after the restart.

    the next BSOD happened while I was playing KOA - Reckoning.
    "

    ----------------------------------------------

    If your bios is right and no overheating/clocking, disconnect peripherals and see how it goes. It might be faulty motherboard. Or CPU. Or RAM sticks/slots.
     

  5. Portal2Two

    Portal2Two Banned

    Messages:
    27
    Likes Received:
    0
    GPU:
    AMD 6970

    Changing the multiplier can be wrong and therefore cause bsod. I'd suggest you disconnect all redundant devices like headphones and set all your hardware clocks to their stock strictly as recomended by the manufacture, including the multiplier you mention. Then if blue screens persist even at stock with 0x124_AuthenticAMD error, blame your hardware.

    And by the way, 500w may not be enough, given you do overclock sometimes. You're saying you "rarely have bsods when do that" means occasionally you do get them during the o/c-ing. I'd try stocks.
     
  6. vonalka

    vonalka Member

    Messages:
    44
    Likes Received:
    0
    GPU:
    3GB AMD Radeon 7970
    Are you using an SSD? I have seen this happen before on some SSD drives and a firmware update might solve the problem.
     

Share This Page