Windows 8 and 8.1 Forums


Persistent BSODs and Crashes

  1. #1


    Posts : 16
    Windows 8.1

    Persistent BSODs and Crashes: Potentially AMD APU Drivers


    I'm getting quite regular BSODs and crashes, previously I was getting crashes from AMD 14.7 beta drives so I swapped down to the 14.4 drivers. Now I'm not getting BSODs from atikmdag.sys, but I'm getting BSODs from what looks like ntoskrnl.exe. Additionally sometimes my computer will freeze, the display will show a static image, and the computer won't respond to keyboard/mouse input. Sounds can be heard to play as normal indefinitely (I haven't left it for more than a minute so not sure how long it would continue). This suggests to me that it's a display driver problem.

    Here's the list of BSODs as shown by BlueScreenView:
    Attachment 49721
    Highlighted in blue are the crashes before changing drivers.
    This is my dxdiag, I'm running an A10-7850k, 8gb corsair vengence pro 2400mhz, fm2a88x-itx+ and an 840 evo ssd.

    I can upload any requested dump files or information.

    I couldn't use SF diagnostic tool because I don't have .NET framework 3.5 installed, and when trying to install it I got error code 0x800F0906, and following all of MS's instructions failed (could still connected to update server, just not for .NET 3.5, using install media failed probably because 8 is different to 8.1).

    This is what BlueScreenView calls a "minidump" (this is for the most recent crash shown above. I'm not sure if this is any different from what SF Debug collects).

    Here's my output from SF Debug.


    Thanks!
    Last edited by gorman; 28 Aug 2014 at 13:20.

      My System SpecsSystem Spec

  2. #2


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Gorman ^_^,

    I have analyzed your dump files and below has been provided an analysis of the same for informative purposes :-
    Code:
    **************************Thu Aug 28 19:25:56.613 2014 (UTC + 5:30)***************************** 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
     
    BugCheck 1E, {ffffffffc0000005, fffff800e832de0d, 1, 973e0180}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
     
    BUGCHECK_STR:  0x1E_c0000005_W
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Aug 28 19:21:26.445 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for win32k.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
     
    Probably caused by : ntkrnlmp.exe ( nt!PpmIdlePrepare+35d )
     
    BugCheck 1E, {ffffffffc0000005, fffff800b60c8e0d, 1, 6e55e180}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
     
    BUGCHECK_STR:  0x1E_c0000005_W
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x1E_c0000005_W_nt!PpmIdlePrepare
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Aug 25 05:58:57.206 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for win32k.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
     
    Probably caused by : win32k.sys ( win32k+1a47e3 )
     
    BugCheck 3B, {c0000005, fffff80025832b1d, ffffd00030a92730, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
     
    BUGCHECK_STR:  0x3B
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  GlyphClient.ex
     
    FAILURE_BUCKET_ID:  0x3B_win32k+1a47e3
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug 24 08:25:22.778 2014 (UTC + 5:30)**************************
    Probably caused by : ntkrnlmp.exe ( nt!RtlpGetStackLimits+ee )
     
    BugCheck C4, {91, 0, ffffe00193a2b600, 0}
    BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
     
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
     
    BUGCHECK_STR:  0xc4_91
     
    PROCESS_NAME:  Morrowind.exe
     
    FAILURE_BUCKET_ID:  0xc4_91_nt!RtlpGetStackLimits
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Aug 24 04:47:21.647 2014 (UTC + 5:30)**************************
    Probably caused by : WdFilter.sys ( WdFilter!MpSetFileStateInBitmap+1a7 )
     
    BugCheck 3B, {c0000005, fffff801536a56b7, ffffd0015724dbb0, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
     
    BUGCHECK_STR:  0x3B
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  chrome.exe
     
    FAILURE_BUCKET_ID:  0x3B_WdFilter!MpSetFileStateInBitmap
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 23 07:13:59.315 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for win32k.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
     
    Probably caused by : win32k.sys ( win32k+127898 )
     
    BugCheck 50, {ffffd000fe78d855, 1, fffff9600018e898, 0}
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  chrome.exe
     
    FAILURE_BUCKET_ID:  AV_win32k+127898
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 23 06:15:51.834 2014 (UTC + 5:30)**************************
    Probably caused by : Ndu.sys ( Ndu!NduHandleNblContextRemoved+10 )
     
    BugCheck D1, {41, 2, 1, fffff801021e6088}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  AV_Ndu!NduHandleNblContextRemoved
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 23 06:09:33.751 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : hardware ( atikmdag+1b94b3 )
     
    BugCheck D1, {e232f489, 6, 1, fffff8013f0614b3}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  IP_MISALIGNED_atikmdag.sys
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 23 05:23:17.888 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for win32k.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
     
    Probably caused by : ntkrnlmp.exe ( nt!PpmIdlePrepare+35d )
     
    BugCheck 1E, {ffffffffc0000005, fffff800b4531e0d, 1, b4761180}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
     
    BUGCHECK_STR:  0x1E_c0000005_W
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x1E_c0000005_W_nt!PpmIdlePrepare
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Below is a list of 3rd party drivers present on your system :-
    Code:
    **************************Thu Aug 28 19:25:56.613 2014 (UTC + 5:30)**************************
    L1C63x64.sys                Tue Jul 16 12:26:31 2013 (51E4EE9F)
    amd_sata.sys                Fri Nov 22 08:07:08 2013 (528EC354)
    amd_xata.sys                Fri Nov 22 08:07:11 2013 (528EC357)
    AMDACPKSL.SYS               Wed Mar 12 05:19:44 2014 (531FA118)
    AtihdWB6.sys                Wed Mar 12 05:20:02 2014 (531FA12A)
    SamsungRapidDiskFltr.sys    Mon May 19 19:54:16 2014 (537A1410)
    SamsungRapidFSFltr.sys      Mon May 19 19:54:18 2014 (537A1412)
    atikmpag.sys                Tue Aug 12 07:03:58 2014 (53E96F06)
    amdacpksd.sys               Tue Aug 12 07:55:25 2014 (53E97B15)
    atikmdag.sys                Tue Aug 12 08:07:53 2014 (53E97E01)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Aug 28 19:21:26.445 2014 (UTC + 5:30)**************************
    OpenHardwareMonitor.sys     Sat Jul 26 18:59:37 2008 (488B26C1)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Aug 25 05:58:57.206 2014 (UTC + 5:30)**************************
    EagleX64.sys                Fri Oct  4 06:52:30 2013 (524E1856)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 23 07:13:59.315 2014 (UTC + 5:30)**************************
    L1C60x64.sys                Tue Jul 16 12:26:56 2013 (51E4EEB8)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 23 06:15:51.834 2014 (UTC + 5:30)**************************
    AMDACPKSL.SYS               Fri Dec 20 08:46:21 2013 (52B3B685)
    AtihdWB6.sys                Fri Dec 20 08:46:38 2013 (52B3B696)
    atikmpag.sys                Fri Dec 20 23:11:16 2013 (52B4813C)
    atikmdag.sys                Sat Dec 21 00:08:00 2013 (52B48E88)
    AODDriver2.sys              Tue Feb 11 16:36:52 2014 (52FA044C)
    http://www.carrona.org/drivers/driver.php?id=L1C63x64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=AMDACPKSL.SYS
    http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys
    http://www.carrona.org/drivers/driver.php?id=SamsungRapidDiskFltr.sys
    http://www.carrona.org/drivers/driver.php?id=SamsungRapidFSFltr.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=amdacpksd.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=OpenHardwareMonitor.sys
    http://www.carrona.org/drivers/driver.php?id=EagleX64.sys
    http://www.carrona.org/drivers/driver.php?id=L1C60x64.sys
    http://www.carrona.org/drivers/driver.php?id=AMDACPKSL.SYS
    http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys



    Please follow the below steps, one step at a time :-

    1. Please remove Open Hardware Monitor (Driver Highlighted in RED) as it contains the WinRing Libraries which are pretty famous for causing BSOD's in Windows Systems.
    2. Please remove AODDriver2.sys as well. Read this quote -
      AMD Overdrive; also in EasyTune6 for Gigabyte motherboard
      Known BSOD issues in Win7

      Part of AMD Fuel

      Location: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys
    3. Please rename Eaglex64.sys driver till the time we are troubleshooting.
    4. If the problem is still not solved then please run Memtest for atleast 8 passes using this **GUIDE**.


    Let me know how it proceeds ^_^.
      My System SpecsSystem Spec

  3. #3


    Posts : 16
    Windows 8.1


    Hi blueelvis, thanks so much for your help!

    I'm not sure exactly what to do though. OpenHardwareMonitor isn't installed, so I can't really uninstall it. Searching for the driver doesn't bring anything up. Same with AODDriver2.sys and Eaglex64.sys. I would say I probably used to have AODDriver2 installed before I rolled back the drivers, but I'm not sure.

    On a sidenote, are those dates in the driver list supposed to be meaningful? This machine was only built in late July, with a fresh install.


    I'll run some memtestx86, and thanks again!

    EDIT: After 16 hours / 8 passes of memtestx86, I can confirm that the RAM is fine. System was running at 55-65C during this time which is a bit hot I think, but I have a better heatsink on the way so I'm not terribly worried.


    EDIT: There have been a number of new crashes, I changed back to the AMD beta drivers hoping that would help (this time removing the AMD driver you suggested be removed), but it's not done anything. System temperatures are very low so I don't think it's a heat problem either. Tried changing some USB devices and port to see if that helped anything (random guess) but it didn't :P
    Last edited by gorman; 30 Aug 2014 at 10:09.
      My System SpecsSystem Spec

  4. #4


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Gorman ^_^,

    I have analyzed your dump files and below has been provided an analysis of the same for informative purposes :-
    Code:
    **************************Sat Aug 30 18:33:59.289 2014 (UTC + 5:30)***************************** WARNING: Unable to verify timestamp for win32k.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
     
    Probably caused by : ntkrnlmp.exe ( nt!PpmIdlePrepare+35d )
     
    BugCheck 1E, {ffffffffc0000005, fffff801c76cae0d, 1, 7958a180}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
     
    BUGCHECK_STR:  0x1E_c0000005_W
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x1E_c0000005_W_nt!PpmIdlePrepare
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 30 17:59:57.039 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     
    Probably caused by : atikmdag.sys ( atikmdag+f2cd8 )
     
    BugCheck 50, {ffffd001a0ffde8d, 1, fffff8014b315cd8, 1}
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  dwm.exe
     
    FAILURE_BUCKET_ID:  AV_atikmdag+f2cd8
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 30 16:12:54.199 2014 (UTC + 5:30)**************************
    Probably caused by : USBXHCI.SYS ( USBXHCI!_report_gsfailure+5 )
     
    BugCheck 139, {2, ffffd00139572780, ffffd001395726d8, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
     
    BUGCHECK_STR:  0x139
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x139_2_USBXHCI!_report_gsfailure
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 30 15:51:11.479 2014 (UTC + 5:30)**************************
    *** ERROR: Module load completed but symbols could not be loaded for ucx01000.sys
     
    Probably caused by : ucx01000.sys ( ucx01000+5087 )
     
    BugCheck 1000007E, {ffffffffc0000005, fffff800a6afd087, ffffd0004c7c6b98, ffffd0004c7c63a0}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
     
    PROCESS_NAME:  System
     
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    FAILURE_BUCKET_ID:  AV_ucx01000+5087
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 30 15:21:16.470 2014 (UTC + 5:30)**************************
    *** 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
     
    BugCheck 1000007F, {8, ffffd001a93e8130, ffffd00227d618b0, fffff80373a4f23b}
    BugCheck Info: UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
     
    BUGCHECK_STR:  0x7f_8
     
    PROCESS_NAME:  chrome.exe
     
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 30 15:19:34.527 2014 (UTC + 5:30)**************************
    *** WARNING: Unable to verify timestamp for L1C63x64.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys
     
    *** 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
     
    BugCheck 1E, {ffffffffc0000005, fffff800e0501e67, ffffd000619a7948, ffffd000619a7150}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
     
    BUGCHECK_STR:  0x1E_c0000005
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 30 14:24:30.900 2014 (UTC + 5:30)**************************
    *** 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
     
    BugCheck 3B, {c0000005, fffff8005d2486b7, ffffd00193103bb0, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
     
    BUGCHECK_STR:  0x3B
     
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
     
    PROCESS_NAME:  chrome.exe
     
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 30 11:35:33.293 2014 (UTC + 5:30)**************************
    *** 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
     
    BugCheck 3B, {c0000005, fffff80365916697, ffffd0016ddafae0, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
     
    BUGCHECK_STR:  0x3B
     
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
     
    PROCESS_NAME:  csrss.exe
     
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Aug 29 11:27:16.149 2014 (UTC + 5:30)**************************
    *** 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
     
    BugCheck 3B, {c0000005, fffff800902774f8, ffffd00161806ba0, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
     
    BUGCHECK_STR:  0x3B
     
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
     
    PROCESS_NAME:  svchost.exe
     
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Aug 28 21:02:33.530 2014 (UTC + 5:30)**************************
    Probably caused by : atikmdag.sys ( atikmdag+7fcb7 )
     
    BugCheck 3D, {ffffd000c711b2d0, 0, 0, fffff8010d90dcb7}
    BugCheck Info: INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
     
    BUGCHECK_STR:  0x3D
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x3D_atikmdag+7fcb7
     
      BIOS Version                  P2.10
     
      BIOS Release Date             01/17/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Product Name                  To Be Filled By O.E.M.
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Below is a list of 3rd party drivers present on your system :-
    Code:
    **************************Sat Aug 30 18:33:59.289 2014 (UTC + 5:30)**************************
    L1C63x64.sys               Tue Jul 16 12:26:31 2013 (51E4EE9F)
    amd_sata.sys               Fri Nov 22 08:07:08 2013 (528EC354)
    amd_xata.sys               Fri Nov 22 08:07:11 2013 (528EC357)
    usbfilter.sys              Mon Feb 17 11:53:43 2014 (5301AAEF)
    appexDrv.sys               Tue Feb 25 14:34:59 2014 (530C5CBB)
    AMDACPKSL.SYS              Wed Mar 12 05:19:44 2014 (531FA118)
    AtihdWB6.sys               Wed Mar 12 05:20:02 2014 (531FA12A)
    SamsungRapidDiskFltr.sys   Mon May 19 19:54:16 2014 (537A1410)
    SamsungRapidFSFltr.sys     Mon May 19 19:54:18 2014 (537A1412)
    atikmpag.sys               Wed Jul  9 20:49:51 2014 (53BD5D97)
    amdacpksd.sys              Wed Jul  9 21:00:00 2014 (53BD5FF8)
    atikmdag.sys               Wed Jul  9 21:04:34 2014 (53BD610A)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Aug 30 17:59:57.039 2014 (UTC + 5:30)**************************
    atikmpag.sys               Tue Aug 12 07:03:58 2014 (53E96F06)
    amdacpksd.sys              Tue Aug 12 07:55:25 2014 (53E97B15)
    atikmdag.sys               Tue Aug 12 08:07:53 2014 (53E97E01)
    http://www.carrona.org/drivers/driver.php?id=L1C63x64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=appexDrv.sys
    http://www.carrona.org/drivers/driver.php?id=AMDACPKSL.SYS
    http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys
    http://www.carrona.org/drivers/driver.php?id=SamsungRapidDiskFltr.sys
    http://www.carrona.org/drivers/driver.php?id=SamsungRapidFSFltr.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=amdacpksd.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=amdacpksd.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys



    Please follow the below steps, one step at a time :-

    1. Please make sure that your Windows Installation is up-to-date. Please note that it might take multiple trips to the Windows Update to get the updates.
    2. Please make sure that the Firmware for your SSD is up to date. Check the Samsung website for the updates.
    3. Please start with these Free Hardware Diagnostics over **HERE**. Please do not perform the Memtest as you have already performed them. Report back your findings. Also, run the Intel Stress Burn Test using this **GUIDE**.
    4. If the above fail, please run Driver Verifier according to this **GUIDE**.



    Let me know how it goes ^_^.
      My System SpecsSystem Spec

  5. #5


    Posts : 16
    Windows 8.1


    Install is up to date, ssd firmware is up to date and ssd is running fine (SMART status is OK too), memory came out fine (as mentioned before), furmark ran fine. Prime95 detected errors fairly quickly (as far as I know prime95 errors are mostly from heat, and I have a new heatsink on the way, but regardless they popped up within a few minutes which is worrying. Maybe it's the RAM that's overheating).

    I ran driver verifier, it caused a crash on launch during the login screen every time. Deleting the settings didn't help and recovery point failed (I made one before changing the settings). I ended up doing a 'system refresh'. I have attached the report generated by dm log collector for these minidumps.

    Thanks again blueelvis!
      My System SpecsSystem Spec

  6. #6


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Gorman ^_^,

    Below has been provided an analysis of the dump file :-
    Code:
    1: kd> !analyze -v*******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: ffffcf81ad644e80, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8015f1a9101, address which referenced memory
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8017b561138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
     ffffcf81ad644e80 
    
    
    CURRENT_IRQL:  2
    
    
    FAULTING_IP: 
    L1C63x64+7101
    fffff801`5f1a9101 4d8b36          mov     r14,qword ptr [r14]
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  AV
    
    
    PROCESS_NAME:  svchost.exe
    
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    
    TRAP_FRAME:  ffffd00021169dc0 -- (.trap 0xffffd00021169dc0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000286
    rdx=ffffe000f2a0c9b0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8015f1a9101 rsp=ffffd00021169f50 rbp=ffffcf81aa904fb0
     r8=0000000000000000  r9=fffff8015d2d24e4 r10=fffff8017b8a35c0
    r11=ffffe000f2a0c6e0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    L1C63x64+0x7101:
    fffff801`5f1a9101 4d8b36          mov     r14,qword ptr [r14] ds:00000000`00000000=????????????????
    Resetting default scope
    
    
    LAST_CONTROL_TRANSFER:  from fffff8017b36cae9 to fffff8017b360fa0
    
    
    STACK_TEXT:  
    ffffd000`21169c78 fffff801`7b36cae9 : 00000000`0000000a ffffcf81`ad644e80 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`21169c80 fffff801`7b36b33a : 00000000`00000000 ffffe000`f17dfa20 00000000`00000500 ffffd000`21169dc0 : nt!KiBugCheckDispatch+0x69
    ffffd000`21169dc0 fffff801`5f1a9101 : ffffe000`f17dfa20 ffffe000`f17df000 ffffe000`f19c33e8 ffffcf81`aa904fb0 : nt!KiPageFault+0x23a
    ffffd000`21169f50 ffffe000`f17dfa20 : ffffe000`f17df000 ffffe000`f19c33e8 ffffcf81`aa904fb0 ffffe000`f1b075c0 : L1C63x64+0x7101
    ffffd000`21169f58 ffffe000`f17df000 : ffffe000`f19c33e8 ffffcf81`aa904fb0 ffffe000`f1b075c0 fffff801`000001c0 : 0xffffe000`f17dfa20
    ffffd000`21169f60 ffffe000`f19c33e8 : ffffcf81`aa904fb0 ffffe000`f1b075c0 fffff801`000001c0 00000000`00000000 : 0xffffe000`f17df000
    ffffd000`21169f68 ffffcf81`aa904fb0 : ffffe000`f1b075c0 fffff801`000001c0 00000000`00000000 00000000`00000000 : 0xffffe000`f19c33e8
    ffffd000`21169f70 ffffe000`f1b075c0 : fffff801`000001c0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffcf81`aa904fb0
    ffffd000`21169f78 fffff801`000001c0 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffcf81`ad644e80 : 0xffffe000`f1b075c0
    ffffd000`21169f80 00000000`00000000 : 00000000`00000000 00000000`00000000 ffffcf81`ad644e80 ffffcf81`ad644d20 : 0xfffff801`000001c0
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    L1C63x64+7101
    fffff801`5f1a9101 4d8b36          mov     r14,qword ptr [r14]
    
    
    SYMBOL_STACK_INDEX:  3
    
    
    SYMBOL_NAME:  L1C63x64+7101
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: L1C63x64
    
    
    IMAGE_NAME:  L1C63x64.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51e4ee9f
    
    
    FAILURE_BUCKET_ID:  AV_L1C63x64+7101
    
    
    BUCKET_ID:  AV_L1C63x64+7101
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:av_l1c63x64+7101
    
    
    FAILURE_ID_HASH:  {242eeef8-3844-8cd4-efe1-718473ded7a0}
    
    
    Followup: MachineOwner
    ---------
    According to the dump file, the "L1C63x64.sys" is blamed which is your "Qualcomm Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.30)". Please update this driver and then check for BSOD's. Furthermore, according to the Dump File, Driver Verifier was not enabled.

    See if you still get the crashes if you remove your ethernet wire from the system. What is the temperature of the System?

    Also, the Prime95 tests could mean a hardware problem but first make sure your system is not over heating. This could be the possible cause because I have not seen a single WHEA_UNCORRECTABLE_ERROR in your dump files which is generally a faulty processor. You could also try a small underclock.

    Let me know how it goes ^_^
      My System SpecsSystem Spec

  7. #7


    Posts : 16
    Windows 8.1


    Have now installed "netl1c64x64" which still identifies as NDIS 6.30 so not I'm sure about that.

    When driver verifier was enabled it crashed maybe 4 or 5 times at login screen before I did a system refresh, not sure if dump files were generated for them, but if they were then they would be in that zip.

    Temps on prime95 hit 80C before I shut it off, right now I'm using the stock cooler which is not really adequate, but I have a noctua L12 in the mail due to arrive yesterday.

    I reduced the RAM clock speed all the way down (675MHz) and have not seen any crashes yet, it might have just been some bad RAM chips after all. I'll keep an eye out, and if it starts crashing again I'll try with ethernet unplugged.

    Thanks again blueelvis!

    EDIT: I was playing a game (no crashes all day! RAM settings are at 2133 and it seems to be going OK!) and I alt-tabbed out to see this Attachment 50201
    Last edited by gorman; 03 Sep 2014 at 09:27.
      My System SpecsSystem Spec

  8. #8


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by gorman View Post
    Have now installed "netl1c64x64" which still identifies as NDIS 6.30 so not I'm sure about that.

    When driver verifier was enabled it crashed maybe 4 or 5 times at login screen before I did a system refresh, not sure if dump files were generated for them, but if they were then they would be in that zip.

    Temps on prime95 hit 80C before I shut it off, right now I'm using the stock cooler which is not really adequate, but I have a noctua L12 in the mail due to arrive yesterday.

    I reduced the RAM clock speed all the way down (675MHz) and have not seen any crashes yet, it might have just been some bad RAM chips after all. I'll keep an eye out, and if it starts crashing again I'll try with ethernet unplugged.

    Thanks again blueelvis!

    EDIT: I was playing a game (no crashes all day! RAM settings are at 2133 and it seems to be going OK!) and I alt-tabbed out to see this
    The temperatures are very high for the processor mate. I wish that some hardware component has not been damaged in this. I would advise you to stop doing CPU Intensive tasks till the time your new Heatsink comes in. Reducing the RAM speed all the way to 675MHz (What was the original speed at which the RAM was running by the way? ). You could have just reduced it by 20-50Mhz slabs so that no crashes but performance wise it was strong as well.


    Let me know how it goes ^_^.
      My System SpecsSystem Spec

  9. #9


    Posts : 16
    Windows 8.1


    I'm very surprised the CPU can get that hot, I would have expected thermal throtteling or shutoff at that temperature!

    So far no crashes, I think speccy might be reporting the temperature incorrectly or inaccurately.
      My System SpecsSystem Spec

  10. #10


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by gorman View Post
    I'm very surprised the CPU can get that hot, I would have expected thermal throtteling or shutoff at that temperature!

    So far no crashes, I think speccy might be reporting the temperature incorrectly or inaccurately.
    Yes it is very hot. My Toshiba laptop goes beyond 100 degrees without shutting down :P
    Although it is under during extremely heavy load or when it is kept on a pillow but then it's heatsink seems like blowing dragon's breath :P


    Let me know how it goes ^_^
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
Persistent BSODs and Crashes
Related Threads
Hi I get frequent BSODs, AMD driver crashes, screen display errors, game crashes, running Windows 8.1 on my AMD A10-5700 APU w/ 8GB RAM. Videos in browsers (firefox, IE, and/or chrome) are common culprits, as are running certain games (recently, GTA IV). Sometimes the BSODs and driver crashes...
Multiple BSODs and graphics driver crashes. in BSOD Crashes and Debugging
So for about a month now I've been having blue screens while running certain games (Assetto Corsa, Project Cars) and other programs like the full screen apps downloaded from the store. At first I thought it was related to a possible HDD failure but after running several tests everything came back...
Solved Computer crashes/BSODs randomly in BSOD Crashes and Debugging
Hi there, I've got a small BSOD problem with my Win8.1 x64 installation. An hour ago my computer crashed while I wasnt near it (it only heard the restart peep). The last time it crashed I was able to note the error message, which stated: After googeling a bit I found out, that the BSOD...
Hello everybody, Frustrated Windows 8 user and busy college student here. Small background on this longstanding current problem: a couple years back I had to replace most of the main components in my HP desktop due to a motherboard defect that essentially destroyed the motherboardТs ability to...
I've set up two drive mappings on my Windows 8 machine to my NAS machine but they never stay when I reboot. When I reboot or start my machine, the drive mappings show a red "X" beside them in Explorer, but when I just single click on them they open up as you would expect them to. From that point...
Hello, I've been experiencing seemingly random BSODs, mostly during gaming but also after gaming or even before doing anything at all. Sometimes, but much less often, there's been random reboots or crashes without a BSOD. What I've tried so far. Updated drivers for graphics, network and...
Solved BSODs or Crashes While Playing Games in BSOD Crashes and Debugging
i dont know why these bsod s or crashes coming. i tried to update my drivers it didnt work. if you need more information just reply here i will answer it as soon as i see it
Eight Forums Android App Eight Forums IOS App Follow us on Facebook