BSOD from ntoskrnl when explorer.exe is open

Page 1 of 3 123 LastLast

  1. Posts : 16
    Windows 7 Home Premium 64bit
       #1

    BSOD from ntoskrnl when explorer.exe is open


    Hi,

    I've been getting some blue screen errors whilst browsing through explorer, i've run chkdsk /f /r on all my hard drives and no errors show.
    It seems to have started after installing some windows update, i've rolled back to an earlier backup but my PC still seems slightly unstable.

    Any advice is much appreciated!

    Thanks
    Ben
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi Coherent.

    ► Make it sure that the OCZ-AGILITY3 SSD is using the up-to date firmware. OCZ Toolbox: Firmware & BIOS Updates

    ► Uninstall The ISO Mounter. It is a must.

    No code has to be inserted here.

    It is failing there, as it is supposed to do. You enabled driver verifier which also identified it as the culprit behind the BSODs.

    ► Also update JMicron JMB36X Controller from ftp://driver.jmicron.com.tw/SATA_Controller/Windows/. It is old, the date goes back to 2010.

    Let us know the results.
    ___________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    BugCheck 50, {fffff8a21ba12688, 0, fffff88001306673, 2}
    
    
    Could not read faulting driver name
    Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushUserStream+53 )
    
    Followup: MachineOwner
    -------------------------------------------------------------------------------
    BugCheck A, {8, 2, 1, fffff80002ad9296}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+c6 )
    
    Followup: MachineOwner
    -------------------------------------------------------------------------------
    BugCheck C9, {215, fffff880059d6eab, fffff980076c4e10, 0}
    
    *** WARNING: Unable to verify timestamp for NIWinCDEmu.sys
    *** ERROR: Module load completed but symbols could not be loaded for NIWinCDEmu.sys
    Probably caused by : NIWinCDEmu.sys ( NIWinCDEmu+9eab )
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 16
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    Hi Arc,

    Thank you for your input!

    The firmware for my SSD was up to date but I have uninstalled the ISO mounter and updated the jmicron driver.

    My computer has been stable so far! Hopefully it stays this way

    Many thanks
    Ben
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    That's a good news, Ben :)

    Let us know how it is working, say after a couple of days :)
      My Computer


  5. Posts : 16
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    Unfortunately i've just experienced another BSOD.

    It was running so smoothly!
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Ben, can you update the BIOS to the version 1402 dated 2012.08.29?
    It is available in SABERTOOTH X58 - Motherboards - ASUS

    Also, do some hardware tests .....

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Let us know the results.
    ___________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff80002dcf9e2, fffff8800334d448, fffff8800334cca0}
    
    Probably caused by : ntkrnlmp.exe ( nt!FsRtlOplockIsFastIoPossible+a )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002dcf9e2, The address that the exception occurred at
    Arg3: fffff8800334d448, Exception Record Address
    Arg4: fffff8800334cca0, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!FsRtlOplockIsFastIoPossible+a
    fffff800`02dcf9e2 f6426840        test    byte ptr [rdx+68h],40h
    
    EXCEPTION_RECORD:  fffff8800334d448 -- (.exr 0xfffff8800334d448)
    ExceptionAddress: fffff80002dcf9e2 (nt!FsRtlOplockIsFastIoPossible+0x000000000000000a)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000200000068
    Attempt to read from address 0000000200000068
    
    CONTEXT:  fffff8800334cca0 -- (.cxr 0xfffff8800334cca0)
    rax=fffffa80062d1101 rbx=0000000000000000 rcx=fffff8a004fea7d0
    rdx=0000000200000000 rsi=0000000000000001 rdi=fffff8800334d910
    rip=fffff80002dcf9e2 rsp=fffff8800334d688 rbp=0000000000000001
     r8=0000000000000000  r9=0000000000000001 r10=fffff8800334d720
    r11=fffff8800334d640 r12=fffff8a004fea610 r13=fffff8a004fea690
    r14=fffffa80062d1370 r15=fffffa80062d1180
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    nt!FsRtlOplockIsFastIoPossible+0xa:
    fffff800`02dcf9e2 f6426840        test    byte ptr [rdx+68h],40h ds:002b:00000002`00000068=??
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000200000068
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfc100
    GetUlongFromAddress: unable to read from fffff80002cfc1c0
     0000000200000068 Nonpaged pool
    
    FOLLOWUP_IP: 
    nt!FsRtlOplockIsFastIoPossible+a
    fffff800`02dcf9e2 f6426840        test    byte ptr [rdx+68h],40h
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from fffff880012d3e33 to fffff80002dcf9e2
    
    STACK_TEXT:  
    fffff880`0334d688 fffff880`012d3e33 : 00000000`00000000 00000000`00000001 00000000`00000001 fffff880`0334d910 : nt!FsRtlOplockIsFastIoPossible+0xa
    fffff880`0334d690 fffff880`013ccac3 : fffff880`0334d910 fffffa80`062d1180 fffffa80`062d1100 fffffa80`062d1100 : Ntfs!NtfsFlushVolume+0xc13
    fffff880`0334d7c0 fffff880`0131f03f : fffff880`0334d910 fffffa80`062d1180 fffffa80`09f0fc60 fffffa80`062d1188 : Ntfs!NtfsShutdownVolume+0xd3
    fffff880`0334d840 fffff880`013d4e95 : fffff880`0334d910 00000000`00000000 fffff880`013ce9b0 00000000`00000000 : Ntfs!NtfsForEachVcb+0x167
    fffff880`0334d8e0 fffff880`011056af : fffffa80`05b3db70 fffff800`02c6a280 fffff800`02cc9990 fffffa80`09f0fc60 : Ntfs!NtfsFsdShutdown+0x145
    fffff880`0334db10 fffff800`02d1447c : fffffa80`05b36890 fffff800`02c74640 00000000`00000001 00000000`00000000 : fltmgr!FltpDispatch+0x9f
    fffff880`0334db70 fffff800`02d14612 : 00000000`00000001 00000000`00000001 fffff800`02c6a280 00000000`00000000 : nt!IopShutdownBaseFileSystems+0xac
    fffff880`0334dbf0 fffff800`02d152d6 : fffff800`02d150f0 fffff800`02c6a280 00000000`00000001 00000000`00000001 : nt!IoShutdownSystem+0x122
    fffff880`0334dc70 fffff800`02ace251 : fffff800`02d150f0 fffff800`02dbcd01 fffffa80`05589900 fffffa80`00000000 : nt!PopGracefulShutdown+0x1e6
    fffff880`0334dcb0 fffff800`02d62ede : 99569956`754e754e fffffa80`055899d0 00000000`00000080 fffffa80`054ed040 : nt!ExpWorkerThread+0x111
    fffff880`0334dd40 fffff800`02ab5906 : fffff880`0316a180 fffffa80`055899d0 fffff880`031750c0 29912991`1f741f74 : nt!PspSystemThreadStartup+0x5a
    fffff880`0334dd80 00000000`00000000 : fffff880`0334e000 fffff880`03348000 fffff880`0334c5b0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!FsRtlOplockIsFastIoPossible+a
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6
    
    STACK_COMMAND:  .cxr 0xfffff8800334cca0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_nt!FsRtlOplockIsFastIoPossible+a
    
    BUCKET_ID:  X64_0x7E_nt!FsRtlOplockIsFastIoPossible+a
    
    Followup: MachineOwner
    ---------
      My Computer


  7. Posts : 16
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    Hi Arc,

    BIOS has been updated and i've run test on my memory and GPU with no errors.

    Ill monitor and post back in a few days with the results.

    Thank you again!

    Ben
      My Computer


  8. Posts : 16
    Windows 7 Home Premium 64bit
    Thread Starter
       #8

    Sorry, forgot to update!!

    I've not had a BSOD since updating my BIOS.

    Thank you Arc!!!
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #9

    You are welcome, Ben :)

    Let us know for any further issue.
      My Computer


  10. Posts : 16
    Windows 7 Home Premium 64bit
    Thread Starter
       #10

    Unfortunatley I've been having a few issues again.
    Was so smooth for a while!!!!
    I've attached all the dumps and stuff, any advice is appreciate. As always!!

    Gonna check for new drivers in the meantime.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:35.
Find Us