Windows 8 and 8.1 Forums


Repetitive random BSOD caused by ntoskrnl.exe

  1. #1


    Posts : 1
    Windowa 8.1

    Repetitive random BSOD caused by ntoskrnl.exe


    Hello everyone,

    I'm having this random BSOD that seems to be caused by ntoskrnl.exe, according to WhoCrashed.
    It occurred three times just while I'm trying to post this thread. I can't identify a specific event that triggers this BSOD. It happens while browsing the net, watching videos, playing games, even while editing this post to mention this info!

    System Information:

    computer name: MSI
    windows version: Windows 8.1 , 6.2, build: 9200
    windows dir: C:\WINDOWS
    Hardware: GT70 2OC/2OD, Micro-Star International Co., Ltd., MS-1763
    CPU: GenuineIntel Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Intel586, level: 6
    8 logical processors, active mask: 255
    RAM: 34241622016 total
    VM: 2147352576, free: 1928572928

    last two reports by WhoCrashed:

    On Fri 6/20/2014 10:38:51 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062014-11062-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800784B9A81, 0xFFFFD00024B91D20, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 6/20/2014 10:28:12 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062014-8640-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0x139 (0x3, 0xFFFFD000219CCFB0, 0xFFFFD000219CCF08, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The kernel has detected the corruption of a critical data structure.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    Thank you,

    - Dark180

      My System SpecsSystem Spec

  2. #2


    Posts : 660
    windows 8.1


    A few dumpfiles blames Probably caused by : hardware ( nt!KiDeliverApc+166 )

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff800784b9a81, ffffd00024b91d20, 0}
    Probably caused by : hardware ( nt!KiDeliverApc+166 )
    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: fffff800784b9a81, Address of the instruction which caused the bugcheck
    Arg3: ffffd00024b91d20, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    Debugging Details:
    ------------------
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
    FAULTING_IP: 
    nt!IopCompleteRequest+221
    fffff800`784b9a81 000f            add     byte ptr [rdi],cl
    CONTEXT:  ffffd00024b91d20 -- (.cxr 0xffffd00024b91d20;r)
    rax=0000000000060040 rbx=ffffe0007a5d1ca0 rcx=ffffe0007a377160
    rdx=00000000820f08e0 rsi=ffffe00088835340 rdi=000000000000000f
    rip=fffff800784b9a81 rsp=ffffd00024b92750 rbp=ffffd00024b928a8
     r8=0000000000000000  r9=0000000020206f49 r10=ffffe0007a3b3080
    r11=ffffe000880470a0 r12=fffff80078702180 r13=ffffe0007a3b3080
    r14=0000000000000001 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    nt!IopCompleteRequest+0x221:
    fffff800`784b9a81 000f            add     byte ptr [rdi],cl ds:002b:00000000`0000000f=??
    Last set context:
    rax=0000000000060040 rbx=ffffe0007a5d1ca0 rcx=ffffe0007a377160
    rdx=00000000820f08e0 rsi=ffffe00088835340 rdi=000000000000000f
    rip=fffff800784b9a81 rsp=ffffd00024b92750 rbp=ffffd00024b928a8
     r8=0000000000000000  r9=0000000020206f49 r10=ffffe0007a3b3080
    r11=ffffe000880470a0 r12=fffff80078702180 r13=ffffe0007a3b3080
    r14=0000000000000001 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    nt!IopCompleteRequest+0x221:
    fffff800`784b9a81 000f            add     byte ptr [rdi],cl ds:002b:00000000`0000000f=??
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  Steam.exe
    CURRENT_IRQL:  1
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    IRP_ADDRESS: ffffffffffffff88
    MISALIGNED_IP: 
    nt!IopCompleteRequest+221
    fffff800`784b9a81 000f            add     byte ptr [rdi],cl
    LAST_CONTROL_TRANSFER:  from fffff80078474416 to fffff800784b9a81
    STACK_TEXT:  
    ffffd000`24b92750 fffff800`78474416 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff800`78818930 : nt!IopCompleteRequest+0x221
    ffffd000`24b92860 fffff800`78472eaa : 00000000`00000100 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x166
    ffffd000`24b928e0 fffff800`78472779 : ffffe000`7a3b3080 81cf8c73`d3460ea4 7fffffff`ffffffff ffffe000`880470c0 : nt!KiSwapThread+0x2da
    ffffd000`24b92980 fffff800`78482dfa : ffffd000`24b92aa8 00000000`00000000 ffffe000`00000018 fffff800`788191c6 : nt!KiCommitThreadWait+0x129
    ffffd000`24b92a00 fffff800`788168d2 : ffffe000`7a377160 ffffd000`00000006 00000000`00000000 00000000`00000001 : nt!KeWaitForSingleObject+0x22a
    ffffd000`24b92a90 fffff800`7857b7b3 : ffffe000`7a3b3080 00000000`ffffffff ffffd000`24b92ad8 ffffe000`7a377160 : nt!NtWaitForSingleObject+0xb2
    ffffd000`24b92b00 00000000`778b2772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`089aed48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778b2772
    
    FOLLOWUP_IP: 
    nt!KiDeliverApc+166
    fffff800`78474416 80a3c0000000fd  and     byte ptr [rbx+0C0h],0FDh
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt!KiDeliverApc+166
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  hardware
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  6.3.9600.17085
    STACK_COMMAND:  .cxr 0xffffd00024b91d20 ; kb
    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
    ---------
    Please first test your memory, harddisk,videocard etc.

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

Repetitive random BSOD caused by ntoskrnl.exe
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, ...
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...
Hello everybody, my name is Patricio, and I have been experimenting some random BSOD with error 0x0000000a caused by driver ntoskrnl.exe. I have tried to pinpoint the driver by myself but i failed to see which one is causing this. I have reinstalled all motherboard drivers (AMD Southbridge + Video...
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
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.:cry: Attached with my dump files. Thanks in advance
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...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook