Windows 8 and 8.1 Forums


BSOD caused by ntoskrnl.exe and hal.dll, need help!!

  1. #1


    Posts : 2
    Windows 8.1

    BSOD caused by ntoskrnl.exe and hal.dll, need help!!


    Hi All,
    I upgraded my PC from win8 to win8.1 and i get BSOD very frequently. Tried to solve it by update all drivers, but it doesn't helps.
    I ran memory diagnostic before, it show no errors. Please advice.

    Attached with my dump files.

    Thanks in advance

      My System SpecsSystem Spec

  2. #2


    Posts : 660
    windows 8.1






    Code:
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {901d503, d, 1, fffff801ed4bd23f}
    Probably caused by : hardware ( nt!KeClockInterruptNotify+34f )
    Followup: MachineOwner
    ---------
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 000000000901d503, memory referenced
    Arg2: 000000000000000d, IRQL
    Arg3: 0000000000000001, bitfield :
     bit 0 : value 0 = read operation, 1 = write operation
     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff801ed4bd23f, address which referenced memory
    Debugging Details:
    ------------------
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff801ed75d138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
     000000000901d503 
    CURRENT_IRQL:  d
    FAULTING_IP: 
    nt!KeClockInterruptNotify+34f
    fffff801`ed4bd23f 0000            add     byte ptr [rax],al
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    BUGCHECK_STR:  AV
    PROCESS_NAME:  System
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    TRAP_FRAME:  ffffd000b99b8ba0 -- (.trap 0xffffd000b99b8ba0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000901d503 rbx=0000000000000000 rcx=0000000000000015
    rdx=0000000000002930 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff801ed4bd23f rsp=ffffd000b99b8d30 rbp=01cf63690c220989
     r8=0000000000148e25  r9=000000010940ff85 r10=0000000000200000
    r11=0000000000000015 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz na po nc
    nt!KeClockInterruptNotify+0x34f:
    fffff801`ed4bd23f 0000            add     byte ptr [rax],al ds:00000000`0901d503=??
    Resetting default scope
    MISALIGNED_IP: 
    nt!KeClockInterruptNotify+34f
    fffff801`ed4bd23f 0000            add     byte ptr [rax],al
    LAST_CONTROL_TRANSFER:  from fffff801ed568ae9 to fffff801ed55cfa0
    STACK_TEXT:  
    ffffd000`b99b8a58 fffff801`ed568ae9 : 00000000`0000000a 00000000`0901d503 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
    ffffd000`b99b8a60 fffff801`ed56733a : 00000000`00000001 00000000`00000000 00000718`143ab000 ffffd000`b99b8ba0 : nt!KiBugCheckDispatch+0x69
    ffffd000`b99b8ba0 fffff801`ed4bd23f : 00000000`00000000 00000000`00328c12 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x23a
    ffffd000`b99b8d30 fffff801`edb9a67f : fffff801`ed409000 fffff801`ed4f3426 ffffe001`05a017b0 fffff801`ed409000 : nt!KeClockInterruptNotify+0x34f
    ffffd000`b99b8f40 fffff801`ed4d8363 : ffffe001`05a01700 fffff801`ed51073b ffff1ce7`0acb1412 00000000`00000000 : hal!HalpTimerClockInterrupt+0x4f
    ffffd000`b99b8f70 fffff801`ed55e42a : ffffe001`05a01700 ffffe001`0c19a880 00000000`00000000 ffffe001`0588a900 : nt!KiCallInterruptServiceRoutine+0xa3
    ffffd000`b99b8fb0 fffff801`ed55e80f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd000`b99aaad0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x11f
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KeClockInterruptNotify+34f
    fffff801`ed4bd23f 0000            add     byte ptr [rax],al
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nt!KeClockInterruptNotify+34f
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  hardware
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  6.3.9600.17041
    MODULE_NAME: hardware
    FAILURE_BUCKET_ID:  IP_MISALIGNED
    BUCKET_ID:  IP_MISALIGNED
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:ip_misaligned
    FAILURE_ID_HASH:  {201b0e5d-db2a-63d2-77be-8ce8ff234750}
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 133, {0, 501, 500, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2f626 )
    Followup: MachineOwner
    ---------
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    DPC_WATCHDOG_VIOLATION (133)
    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
    or above.
    Arguments:
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
     component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    Debugging Details:
    ------------------
    
    DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    BUGCHECK_STR:  0x133
    PROCESS_NAME:  System
    CURRENT_IRQL:  d
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    TRAP_FRAME:  ffffd0017f4b8b60 -- (.trap 0xffffd0017f4b8b60)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000010936 rbx=0000000000000000 rcx=ffffe001fe4712b8
    rdx=ffffe001fe4711a0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8018a2c53a0 rsp=ffffd0017f4b8cf8 rbp=ffffd0017f4b8e00
     r8=00000000b5d51421  r9=0000000001cf62ae r10=fffff802cc968f80
    r11=ffffe001f9005760 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    ndis!ndisMWakeUpDpcX:
    fffff801`8a2c53a0 488bc4          mov     rax,rsp
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff802cc813ad6 to fffff802cc7d3fa0
    STACK_TEXT:  
    ffffd001`7f4bfc98 fffff802`cc813ad6 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
    ffffd001`7f4bfca0 fffff802`cc734678 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2f626
    ffffd001`7f4bfd30 fffff802`cc61867f : 00000000`000000ff 00000000`c1597bdf ffffe001`f8a00db0 fffff802`00000000 : nt!KeClockInterruptNotify+0x788
    ffffd001`7f4bff40 fffff802`cc74f363 : ffffe001`f8a00d00 fffff802`cc78773b ffff2632`f389ebda 00000000`00000000 : hal!HalpTimerClockInterrupt+0x4f
    ffffd001`7f4bff70 fffff802`cc7d542a : ffffe001`f8a00d00 ffffd001`7f487180 00000000`0000002c ffffe001`fe4712b8 : nt!KiCallInterruptServiceRoutine+0xa3
    ffffd001`7f4bffb0 fffff802`cc7d580f : ffffd001`7f4b89e0 fffff802`cc7a5f9e 00000000`00000000 00001f80`004b0280 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd001`7f4b89d0 fffff802`cc7de1f3 : 00000000`00000008 ffffd001`7f4b8e60 fffffff6`00000000 ffffd001`7f4b8b60 : nt!KiInterruptDispatchLBControl+0x11f
    ffffd001`7f4b8b60 fffff801`8a2c53a0 : fffff802`cc6d9810 00000000`00000000 ffffd001`7f4b8e00 ffffe001`fe471278 : nt!KiPageFault+0xf3
    ffffd001`7f4b8cf8 fffff802`cc6d9810 : 00000000`00000000 ffffd001`7f4b8e00 ffffe001`fe471278 ffffd001`7f480f45 : ndis!ndisMWakeUpDpcX
    ffffd001`7f4b8d00 fffff802`cc7d70d5 : 00000000`00000000 ffffd001`7f487180 ffffe001`f8a00d00 ffffe001`f888a900 : nt!KiRetireDpcList+0x4f0
    ffffd001`7f4b8fb0 fffff802`cc7d6ed9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    ffffd000`2666b7e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+2f626
    fffff802`cc813ad6 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2f626
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  5318053f
    IMAGE_VERSION:  6.3.9600.17041
    BUCKET_ID_FUNC_OFFSET:  2f626
    FAILURE_BUCKET_ID:  0x133_DPC_nt!_??_::FNODOBFM::_string_
    BUCKET_ID:  0x133_DPC_nt!_??_::FNODOBFM::_string_
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0x133_dpc_nt!_??_::fnodobfm::_string_
    FAILURE_ID_HASH:  {12e2b1b6-39a2-9cfe-dc70-25086917b8e2}
    Followup: MachineOwner
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {0, 2, 1, fffff8031e15c180}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : hardware ( nt!KiInitialPCR+180 )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
     bit 0 : value 0 = read operation, 1 = write operation
     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8031e15c180, address which referenced memory
    Debugging Details:
    ------------------
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8031e1ca138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
     0000000000000000 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!KiInitialPCR+180
    fffff803`1e15c180 801f00          sbb     byte ptr [rdi],0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    BUGCHECK_STR:  AV
    PROCESS_NAME:  System
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    DPC_STACK_BASE:  FFFFF8031F7D7FB0
    TRAP_FRAME:  fffff8031f7d0ae0 -- (.trap 0xfffff8031f7d0ae0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=253a468272460000
    rdx=000003de00000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8031e15c180 rsp=fffff8031f7d0c70 rbp=fffff8031e15c180
     r8=0000000000000000  r9=0000000000400a02 r10=0000000000000002
    r11=fffff8031f7d0c40 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl zr na po nc
    nt!KiInitialPCR+0x180:
    fffff803`1e15c180 801f00          sbb     byte ptr [rdi],0 ds:00000000`00000000=??
    Resetting default scope
    MISALIGNED_IP: 
    nt!KiInitialPCR+180
    fffff803`1e15c180 801f00          sbb     byte ptr [rdi],0
    LAST_CONTROL_TRANSFER:  from fffff8031dfd5ae9 to fffff8031dfc9fa0
    STACK_TEXT:  
    fffff803`1f7d0998 fffff803`1dfd5ae9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff803`1f7d09a0 fffff803`1dfd433a : 00000000`00000001 ffffe000`92452880 ffffe000`00000000 fffff803`1f7d0ae0 : nt!KiBugCheckDispatch+0x69
    fffff803`1f7d0ae0 fffff803`1e15c180 : fffff803`1e1c3a00 ffffe000`92452880 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
    fffff803`1f7d0c70 fffff803`1e1c3a00 : ffffe000`92452880 00000000`00000000 00000000`00000000 fffff803`1f7d1000 : nt!KiInitialPCR+0x180
    fffff803`1f7d0c78 ffffe000`92452880 : 00000000`00000000 00000000`00000000 fffff803`1f7d1000 fffff803`1f7cb000 : nt!KiInitialThread
    fffff803`1f7d0c80 00000000`00000000 : 00000000`00000000 fffff803`1f7d1000 fffff803`1f7cb000 00000000`00000000 : 0xffffe000`92452880
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KiInitialPCR+180
    fffff803`1e15c180 801f00          sbb     byte ptr [rdi],0
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nt!KiInitialPCR+180
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  hardware
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  6.3.9600.17041
    MODULE_NAME: hardware
    FAILURE_BUCKET_ID:  IP_MISALIGNED
    BUCKET_ID:  IP_MISALIGNED
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:ip_misaligned
    FAILURE_ID_HASH:  {201b0e5d-db2a-63d2-77be-8ce8ff234750}
    Followup: MachineOwner
    
     


    Analyse based on canned speech of John carrona:

    Out of the last 18 memory dumps there were 11 different BSOD error codes. The differing error codesare usually symptomatic of a lower level problem within the system. They areusually caused by one of these things:
    - borked (broken) hardware (several different procedures used to isolate theproblem device)
    - BIOS issues (check for updates at the motherboard manufacturer's website)
    - overclocking/overheating - You'll know if you're overclocking or not. Ifuncertain we can suggest things to check.
    - compatibility issues (3rd party hardware/drivers)
    - low-level driver problems
    - or even malware (scanned for when we ask for hardware diagnostics from
    Initial Hardware Diagnostics or Hardware Diagnostics ).


    You can get ahead start on the hardware diagnostics if you'd like - they are located here: Hardware Diagnostics .

    But i suspect that it is hardware related, the latest dumpfile even mentioned Probably caused by : hardware ( nt!KeClockInterruptNotify+34f ), 2 other dumpfiles mentioned HAL.dll.

    If your system is still under warranty, I would recommend contacting your supplier and sending it in to have diagnostic tests done and have any bad hardware replaced.




      My System SpecsSystem Spec

  3. #3


    Posts : 2
    Windows 8.1


    thanks lifetec, this pc bought from Dell, I called them before.
    They ask me to run their own hardware diagnostic tool, But can't found any errors/faulty hardware.
    So I can't claim warranty from them.

    I tried to update my drivers and BIOS over and over again. It doesn't helps as well.
      My System SpecsSystem Spec

  4. #4


    Posts : 660
    windows 8.1


    To exclude other possibilities than faulty hardware, please update the older drivers, see below, on your system.

    You are using Trend Micro Internet security please check if you have the latest windows 8.1 compatible version.

    If the BSOD's continue after updating.
    You could run the Hardware Diagnostics and see if this test find any faulty hardware.
    But i would first contact Dell again because you still have warranty and mention that the analyses of your BSOD's names probably caused by Hardware and Hal.dll. ( reference this thread, send them the SF.zip).

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :
    Note: first check the support/driver downloadsite of your OEM model or system for the latest windows 8.1 drivers.

    lvrs64 fffff801`add20000 fffff801`add74000 Tue Oct 23 04:11:24 2012 (5085fccc) 00058cf8 lvrs64.sys
    lvuvc64 fffff801`ad87a000 fffff801`add01d80 Tue Oct 23 04:12:08 2012 (5085fcf8) 004912c7 lvuvc64.sys
    Driver Description: Logitech Camera driver
    Driver Description: Logitech USB Video Class Driver (WebCam)
    Driver Update Site: Logitech Support - Downloads, Manuals, FAQs & More

    btath_lwflt fffff801`ad861000 fffff801`ad879000 Fri Nov 02 06:35:44 2012 (50935bb0) 000209c1 btath_lwflt.sys
    btath_hcrp fffff801`acbb1000 fffff801`acbfd000 Tue Dec 18 10:54:54 2012 (50d03d6e) 0002e794 btath_hcrp.sys
    btath_bus fffff801`ad130000 fffff801`ad13d000 Mon Jan 21 10:18:42 2013 (50fd07f2) 00011722 btath_bus.sys
    btath_flt fffff801`abc6f000 fffff801`abc8b000 Thu May 23 08:10:29 2013 (519db2d5) 00020379 btath_flt.sys
    btath_rcp fffff801`ad285000 fffff801`ad2d1000 Fri Jun 21 11:11:54 2013 (51c418da) 0003154d btath_rcp.sys
    btath_avdt fffff801`acc39000 fffff801`acc64000 Thu Jul 25 12:10:29 2013 (51f0f995) 0002226f btath_avdt.sys
    btath_a2dp fffff801`aca78000 fffff801`acae0000 Thu Jul 25 12:11:51 2013 (51f0f9e7) 00053de8 btath_a2dp.sys

    Driver Description: Atheros Bluetooth Driver
    Driver Update Site: ATHEROS drivers for Microsoft Windows (Atheros?????) or ATHEROS drivers for Microsoft Windows (Atheros?????)

    HECIx64 fffff801`ac985000 fffff801`ac998000 Mon Dec 17 20:32:21 2012 (50cf7345) 0001803d HECIx64.sys

    Driver Description: Intel Management Engine Interface
    Driver Update Site: http://downloadcenter.intel.com/Default.aspx

    btmaux fffff801`ac9b0000 fffff801`ac9d5000 Tue Apr 23 13:28:02 2013 (51767042) 00025885 btmaux.sys
    Driver Description: Intel Bluetooth Auxiliary Service
    Driver Update Site: http://downloadcenter.intel.com/Sear...22bluetooth%22

    RTKVHD64 fffff801`ad2d2000 fffff801`ad611900 Tue May 14 15:45:12 2013 (51923fe8) 003461db RTKVHD64.sys
    Driver Description: Realtek High Definition Audio Function Driver
    Driver Update Site: Realtek

    athwbx fffff801`acc73000 fffff801`ad028000 Mon Jul 15 09:29:50 2013 (51e3a4ee) 003a9587 athwbx.sys
    Driver Description: Qualcomm Atheros AR9485WB-EG Wireless Network Adapter (Version: 10.0.0.274 is the first one after the release of Win8.1)
    Although I do not recommend drivers from places other than the manufacturer's website - this is the exception to that rule. Please scan with an anti-virus before opening any file that you download from the internet.
    Driver Update Site: Drivers for Atheros AR9485WB and Windows 8 (OEM drivers appear to be a version behind this one for Win8.1)

    VSApiNt fffff801`ae0eb000 fffff801`ae316000 Wed Aug 14 09:16:40 2013 (520b2ed8) 00230036 VSApiNt.sys
    TmPreFlt fffff801`ac9eb000 fffff801`ac9fa000 Wed Aug 14 09:27:38 2013 (520b316a) 000135e7 TmPreFlt.sys
    TmXPFlt fffff801`ae316000 fffff801`ae37c000 Wed Aug 14 09:27:40 2013 (520b316c) 0005c5a8 TmXPFlt.sys

    Driver Description: Trend Micro Internet Security
    Driver Update Site: Free Security Software Trials - Software Downloads - Trend Micro USA
      My System SpecsSystem Spec

BSOD caused by ntoskrnl.exe and hal.dll, need help!!
Related Threads
Solved Having randons BSOD caused by ntoskrnl.exe in BSOD Crashes and Debugging
:ar: THIS THREAD WAS SOLVED BY CHANGING THE MOTHER BOARD. THIS TOPIC WAS CHANGED TO TENFORUMS: Having randons BSOD caused by ntoskrnl.exe - Windows 10 Forums Since I bought my PC, randons BSOD appear (all of them caused by ntoskrnl.exe) >WHEA_UNCORRECTABLE_ERROR, ...
Hi guys, my desktop was perfectly fine a week ago and suddenly I got a BSOD or two per day (4 to 5 hours using my computer). All that I can remember is that I upgraded my GC driver 2 days before that and did some trick I didn't understand in the registry to help Battlefield 4 loading facter. I...
BSOD caused by ntoskrnl.exe randomly in BSOD Crashes and Debugging
Hi everybody, I have been experiencing some random BSOD with error 0x0000000a and 0x00000139 caused by driver ntoskrnl.exe. I have run my desktop for 1 year and seldom experienced such BSODs until this month. I have run memtest to 250% coverage and no errors are found. I also have run disk...
I just bought a brand new Asus g750jm-bsi7n23 and I keep getting a BSOD called DRIVER_POWER_STATE_FAILURE which is being caused by ntoskrnl.exe. It is getting really irritating, because I just dished out $1,300 on a new laptop and it has already crashed 3-4 times. Any help would be GREATLY...
BSOD caused by dxgmms1.sys / ntoskrnl.exe in BSOD Crashes and Debugging
I have freshly installed windows 8.1 Enterprise (x64) and also installed the latest drivers for everything. My configuration: ASUS P8Z77-M Intel i5-3570K 2X4GB DDR3 Kingston HyperX Predator ATI Radeon HD6950 2GB WD 1TB Caviar Black CoolerMaster 550W Real Power
BSOD probably caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hi folks - having some trouble troubleshooting a BSOD on a Lenovo Yoga 13. BSOD screen had dpc_watchdog_violation listed, but when running the minidump through Windbg I got to this: Probably caused by : ntoskrnl.exe ( nt+14dca0 ) Wasn't quite sure where to go from here seeing as that...
I have faced a BSOD for days when waking the laptop up from sleep, and then it takes 15 minutes to start up. Refreshing and resetting do not solve the problem. I have attached the SF zip file The crashes are usually caused by: On Tue 1/21/2014 3:10:37 AM GMT your computer crashed crash dump...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook