1. #1

    BSOD crash

    OS - Windows 10
    x64
    Windows 10
    OEM already activated
    Age of system (hardware): 3 years
    Age of OS installation - 2-3 months

    CPU: intel i5 4590
    Video Card: Gigabyte GTX 760
    MotherBoard -
    Gigabyte Z97M-DS3H
    Power Supply - Corsair CX500
    Attached Files Attached Files


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor

    Join Date
    May 2015
    Age
    21
    Posts
    315
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        1920 x 1080 @ 60 Hz
      • Operating System:
        Windows 10 Pro

    Re: BSOD crash

    Hi shark04,

    Please run chkdsk /r in an admin command prompt or admin powershell for both your partitions.
    Code:
    chkdsk C: /r
    chkdsk E: /r
    If asked to schedule the task or force to unmount, press Y.

    The eventlog shows a large amount of failed paging operations and sometimes corruption
    Code:
    Event[1650]:  Log Name: System
      Source: Microsoft-Windows-Ntfs
      Date: 2017-10-05T18:58:56.024
      Event ID: 98
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-BNCE043
      Description: 
    Volume C: (\Device\HarddiskVolume2) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
    
    Event[4668]:
      Log Name: System
      Source: NTFS
      Date: 2017-09-20T00:12:04.202
      Event ID: 134
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-BNCE043
      Description: 
    The transaction resource manager on volume \Device\HarddiskVolumeShadowCopy1 encountered an error during recovery.  The resource manager will continue recovery.
    
    
    Event[4669]:
      Log Name: System
      Source: Ntfs
      Date: 2017-09-20T00:12:04.203
      Event ID: 55
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-BNCE043
      Description: 
    A corruption was discovered in the file system structure on volume ??.
    
    
    The exact nature of the corruption is unknown.  The file system structures need to be scanned and fixed offline.


    EDIT:
    Please remove Driver Booster and revert any drivers it has installed either by reverting in device manager or by overwriting the drivers. Driver updaters are not ever needed, most of the drivers you need are from Gigabyte.
    Last edited by axe0; 10-12-2017 at 04:46 PM. Reason: Driver booster

  3. #3

    Re: BSOD crash

    Quote Originally Posted by axe0 View Post
    EDIT:
    Please remove Driver Booster and revert any drivers it has installed either by reverting in device manager or by overwriting the drivers. Driver updaters are not ever needed, most of the drivers you need are from Gigabyte.
    It makes no sense what you just said because i was getting the same blue screen with Gigabyte drivers and i don't understand how with a couple of restarts it goes full performance.

  4. #4

    Join Date
    Jul 2017
    Posts
    40

    Re: BSOD crash

    I've looked at the crash dumps provided and can see problems with the graphics driver in one of the threads.

    Code:
    0: kd> !dpx
    Start memory scan  : 0xffff878060d42068 ($csp)
    End memory scan    : 0xffff878060d44000 (Kernel Stack Base)
    
                   rsp : 0xffff878060d42068 : 0xfffff80055a3501c : nt!KiDispatchException+0x23c
    Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_63f40b686fe9309f\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    0xffff878060d42068 : 0xfffff80055a3501c : nt!KiDispatchException+0x23c
    0xffff878060d42080 : 0xfffff80055eabc68 : nt!ObpLookupObjectName+0xb18
    0xffff878060d42130 : 0xfffff80055eb1040 : nt!CmpParseKey
    0xffff878060d42138 : 0xffff878060d42a90 : 0xfffff80055eb1040 : nt!CmpParseKey
    0xffff878060d42170 : 0xfffff80055b82a1b : nt!memset+0xdb
    0xffff878060d42198 : 0xfffff80055eabc68 : nt!ObpLookupObjectName+0xb18
    0xffff878060d42238 : 0xfffff80055a6d509 : nt!ExAcquirePushLockExclusiveEx+0xe9
    0xffff878060d42358 : 0xfffff80055ea5145 : nt!HvpReleaseCellPaged+0x75
    0xffff878060d42428 : 0xfffff80055ea1d9f : nt!CmpCreateKeyBody+0x17f
    0xffff878060d42470 : 0xfffff80055e00380 : nt!CmpRegistryLock
    0xffff878060d42478 : 0xfffff80055a6e333 : nt!ExReleaseResourceLite+0xa3
    0xffff878060d424f8 : 0xffffbe0082f304f0 : !du"187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d42528 : 0xfffff80055a34d50 : nt!RtlGetExtendedContextLength+0x34
    0xffff878060d42538 : 0xfffff80055a35df2 : nt!RtlCaptureStackBackTrace+0x42
    0xffff878060d425e8 : 0xffffbe0083133780 : !du"Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d42638 : 0xffffbe00831337e4 : !du"4&1286464&0&0008"
    0xffff878060d426a0 : 0xffffbe008313378a : !du"PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d42718 : 0xfffff80055b8198e : nt!KiExceptionDispatch+0xce
    0xffff878060d42818 : 0xfffff80055b7b42f : nt!KiDispatchInterrupt+0xf
    0xffff878060d42820 : 0xfffff80055eb1040 : nt!CmpParseKey
    0xffff878060d42868 : 0xfffff80055eabc68 : nt!ObpLookupObjectName+0xb18
    0xffff878060d428f8 : 0xfffff80055b7fe57 : nt!KiPageFault+0x217
    0xffff878060d42900 : 0x0000000000000000 : Trap @ ffff878060d42900
    0xffff878060d42960 : 0xfffff80055b82a1b : nt!memset+0xdb
    0xffff878060d42a68 : 0xfffff80055eabc68 : nt!ObpLookupObjectName+0xb18
    0xffff878060d42a80 : 0xffff878060d42a90 : 0xfffff80055eb1040 : nt!CmpParseKey
    0xffff878060d42a90 : 0xfffff80055eb1040 : nt!CmpParseKey
    0xffff878060d42b48 : 0xfffff80055eafa31 : nt!ObpCaptureObjectName+0x151
    0xffff878060d42b58 : 0xfffff80055b6478d : nt!write_string+0x49
    0xffff878060d42b80 : 0xffffbe0083133780 : !du"Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d42b88 : 0xfffff80055b64487 : nt!woutput_l+0x6d3
    0xffff878060d42b98 : 0xffffbe0082f304c2 : !du"Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d42f98 : 0xfffff80055f3c42e : nt!NtOpenKey+0x12
    0xffff878060d42fa0 : 0xffffbe0082f304f0 : !du"187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d42fd0 : 0xffff878060d42fa0 : 0xffffbe0082f304f0 : !du"187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d42fd8 : 0xfffff80055b81413 : nt!KiSystemServiceCopyEnd+0x13
    0xffff878060d42ff8 : 0xfffff80055a0a000 : "nt!TmInitSystemPhase2 <PERF> (nt+0x0)"
    0xffff878060d43018 : 0xffffbe0082f304c0 : !du"\Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d43038 : 0xffffbe0082f30490 : !du"System\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&128..."
    0xffff878060d43050 : 0xffff878060d430c0 : 0xffffbe0082f30490 : !du"System\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&128..."
    0xffff878060d43058 : 0xfffff80055b606bd : nt!vsnwprintf_l+0x81
    0xffff878060d43070 : 0xffffbe0082f30490 : !du"System\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&128..."
    0xffff878060d43088 : 0xfffff80055a6e036 : nt!ObfDereferenceObjectWithTag+0xc6
    0xffff878060d430a0 : 0xffffbe0082f30490 : !du"System\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&128..."
    0xffff878060d430c0 : 0xffffbe0082f30490 : !du"System\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&128..."
    0xffff878060d430c8 : 0xfffff80055b60631 : nt!vsnwprintf+0x11
    0xffff878060d43108 : 0xfffff80055a1cbc8 : nt!RtlStringCchPrintfExW+0xb8
    0xffff878060d43138 : 0xffffbe0082f304c2 : !du"Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d43148 : 0xfffff80055b79760 : nt!KiServiceLinkage
    0xffff878060d43160 : 0xffff878060d43178 : 0xfffff80055e38cc1 : nt!_RegRtlOpenKeyTransacted+0xb1
    0xffff878060d43178 : 0xfffff80055e38cc1 : nt!_RegRtlOpenKeyTransacted+0xb1
    0xffff878060d43198 : 0xfffff80055e3918e : nt!_CmGetDeviceInstanceKeyPath+0x8a
    0xffff878060d431a8 : 0xfffff80055eb7016 : nt!ObpRemoveObjectRoutine+0x86
    0xffff878060d431b8 : 0xffffbe0082f304c2 : !du"Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d431f8 : 0xffffbe0082f30490 : !du"System\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&128..."
    0xffff878060d43208 : 0xfffff80055e38bf2 : nt!SysCtxRegOpenKey+0x3a
    0xffff878060d43248 : 0xfffff80055e38627 : nt!_CmOpenDeviceRegKeyWorker+0x177
    0xffff878060d432a0 : 0xffffbe0082f304c2 : !du"Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d432a8 : 0xffffbe0082f30490 : !du"System\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&128..."
    0xffff878060d432d0 : 0xffffac88a2654cd0 : !du"PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d43308 : 0xfffff80055e37cc8 : nt!_CmOpenDeviceRegKey+0xe0
    0xffff878060d43318 : 0xffffac88a2654cd0 : !du"PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d433b8 : 0xfffff80055e3aadd : nt!PiPnpRtlCacheObjectBaseKey+0x41
    0xffff878060d433e0 : 0xffffac88a2654cd0 : !du"PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d43408 : 0xfffff80055e39478 : nt!_CmGetDeviceRegPropWorker+0xf8
    0xffff878060d43410 : 0xffffac88a2654cd0 : !du"PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d43428 : 0xfffff80055e37fa2 : nt!PiPnpRtlCmActionCallback+0xf2
    0xffff878060d43490 : 0xffffac88a2654cd0 : !du"PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d434a0 : 0xffffbe0080dc27f0 : !du"\Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d434a8 : 0xffffbe0080dc2820 : !du"187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d434c8 : 0xfffff80055eace4c : nt!ObCloseHandleTableEntry+0x28c
    0xffff878060d434f8 : 0xfffff80055b7b42f : nt!KiDispatchInterrupt+0xf
    0xffff878060d43528 : 0xfffff80055e37eb0 : nt!PiPnpRtlCmActionCallback
    0xffff878060d43538 : 0xffffac88a2654cd0 : !du"PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d43558 : 0xfffff80055e37e25 : nt!CmGetDeviceRegProp+0x115
    0xffff878060d43568 : 0xffff878060d43658 : 0xfffff80055e5fd17 : nt!PiGetDeviceRegProperty+0x87
    0xffff878060d43608 : 0xfffff80055eaee0b : nt!NtClose+0xcb
    0xffff878060d43630 : 0xffffac88a2654cd0 : !du"PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008"
    0xffff878060d43658 : 0xfffff80055e5fd17 : nt!PiGetDeviceRegProperty+0x87
    0xffff878060d43660 : 0xfffff80055d4b4e8 : nt!ExpTaggedPoolLock
    0xffff878060d43668 : 0xfffff80055b81400 : nt!KiSystemServiceCopyEnd
    0xffff878060d436c8 : 0xfffff80055c895a7 : nt!ExAllocatePoolWithTag+0x207
    0xffff878060d437c8 : 0xfffff80055e5f80c : nt!IoGetDeviceProperty+0xcc
    0xffff878060d437e8 : 0xfffff80055d4b4e8 : nt!ExpTaggedPoolLock
    0xffff878060d43808 : 0xfffffe185360fa03 : win32kbase!DrvGetPruneFlag+0xbf
    0xffff878060d43848 : 0xfffffe18535ef393 : win32kbase!DrvSetDisconnectedGraphicsDevice+0x73
    0xffff878060d438a8 : 0xfffffe474000e4a0 : !du"\Device\Video0"
    0xffff878060d438b8 : 0xfffffe18535da2e4 : win32kbase!DrvEnumDisplayDevices+0x304
    0xffff878060d438d0 : 0xfffffe474000e4a0 : !du"\Device\Video0"
    0xffff878060d438e8 : 0xfffffe18535ee9e5 : win32kbase!DrvUpdateGraphicsDeviceList+0x205
    0xffff878060d43978 : 0xfffff80055b7b987 : nt!SwapContext+0x317
    0xffff878060d439e0 : 0xfffffe18537052c8 : !du"MaxObjectNumber"
    0xffff878060d43aa8 : 0xfffffe18535ee72f : win32kbase!NtUserEnumDisplayDevices+0x6f
    0xffff878060d43af8 : 0xfffff80055b81413 : nt!KiSystemServiceCopyEnd+0x13
    0xffff878060d43b00 : 0xffffac88a91337c0 : Trap @ ffff878060d43b00
    The device referenced multiple times is:
    Name NVIDIA GeForce GTX 760
    PNP Device ID PCI\VEN_10DE&DEV_1187&SUBSYS_360B1458&REV_A1\4&1286464&0&0008


    Please update your NVidia driver by first of all uninstalling everything of Nvidia using DDU and then reinstall just the driver and PhysX selecting the option to do a clean install.
    See if this makes a difference.

  5. #5
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor

    Join Date
    May 2015
    Age
    21
    Posts
    315
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        1920 x 1080 @ 60 Hz
      • Operating System:
        Windows 10 Pro

    Re: BSOD crash

    Quote Originally Posted by shark04 View Post
    Quote Originally Posted by axe0 View Post
    EDIT:
    Please remove Driver Booster and revert any drivers it has installed either by reverting in device manager or by overwriting the drivers. Driver updaters are not ever needed, most of the drivers you need are from Gigabyte.
    It makes no sense what you just said because i was getting the same blue screen with Gigabyte drivers and i don't understand how with a couple of restarts it goes full performance.
    The root of your issue is not with drivers, different drivers won't help but drivers from bad sources can make things worse.

    @Analysts & helpers, from a different thread of the OP at another forum it is explained that the nvidia GPU is not the (sole) cause. The GPU has previously been swapped with a different one, it's also been tested with the iGPU of the CPU per the OP.

    See: Blue screen after boot, fixes with restarts - Windows 10

    Ok so I fresh installed Windows 10, all drivers are up to date, changed the stick of ram/slot, tried new GPU, PSU and other components from other pc same result

    About the problem: Everytime i boot up my pc it lags and if i leave it there i get a blue screen with the tag: KMODE_EXCEPTION_NOT_HANDLED. It fixes when i restart the pc 2-3 times or maybe 1 time it's a random thing.
    ( I GOOGLED IT and none of the fixes works, literally i tried everything)

    And none of my components are dying, as i've been previously been asked.

    This pc is like 2-3 years old components haven't got a problem with them ever and i've been running with this issue like a couple of months but i didn't have the time to send it to IT as it fixed with 2-3 restarts (strange)
    Last edited by axe0; 10-13-2017 at 06:23 AM. Reason: Relevant information added
    philc43 says thanks for this.

  6. #6

    Re: BSOD crash

    Quote Originally Posted by axe0 View Post
    Quote Originally Posted by shark04 View Post
    Quote Originally Posted by axe0 View Post
    EDIT:
    Please remove Driver Booster and revert any drivers it has installed either by reverting in device manager or by overwriting the drivers. Driver updaters are not ever needed, most of the drivers you need are from Gigabyte.
    It makes no sense what you just said because i was getting the same blue screen with Gigabyte drivers and i don't understand how with a couple of restarts it goes full performance.
    The root of your issue is not with drivers, different drivers won't help but drivers from bad sources can make things worse.

    @Analysts & helpers, from a different thread of the OP at another forum it is explained that the nvidia GPU is not the (sole) cause. The GPU has previously been swapped with a different one, it's also been tested with the iGPU of the CPU per the OP.

    See: Blue screen after boot, fixes with restarts - Windows 10

    Ok so I fresh installed Windows 10, all drivers are up to date, changed the stick of ram/slot, tried new GPU, PSU and other components from other pc same result

    About the problem: Everytime i boot up my pc it lags and if i leave it there i get a blue screen with the tag: KMODE_EXCEPTION_NOT_HANDLED. It fixes when i restart the pc 2-3 times or maybe 1 time it's a random thing.
    ( I GOOGLED IT and none of the fixes works, literally i tried everything)

    And none of my components are dying, as i've been previously been asked.

    This pc is like 2-3 years old components haven't got a problem with them ever and i've been running with this issue like a couple of months but i didn't have the time to send it to IT as it fixed with 2-3 restarts (strange)


    Ok so I used DDU to clean install the latest driver+physx only and now it doesn't give me BSOD anymore but it lags like hell, same fix with restart.
    Also i installed latest iGPU driver and it runs perfect on it from a couple of boots i gave it.

    I tried to downgrade gpu driver to 358.98 and ran Aida64 system stability check and gave me a DRIVER_CORRUPTED_EXPOOL nvlddmkm.sys BSOD, buuut on the same driver version I restarted my pc and it runs smooth now ( i did the test on a laggy/bad boot)

Similar Threads

  1. [SOLVED] [Win 10 x64] BSOD Crash 0x7f (8)
    By kvizerad in forum BSOD, Crashes, Kernel Debugging
    Replies: 9
    Last Post: 08-15-2017, 03:10 PM
  2. BSOD crash while gaming.
    By TimonHD in forum BSOD, Crashes, Kernel Debugging
    Replies: 2
    Last Post: 10-30-2015, 04:37 AM
  3. Crash, No BSOD [Windows 8.1 x64]
    By Marthenil in forum BSOD, Crashes, Kernel Debugging
    Replies: 0
    Last Post: 07-26-2015, 05:03 AM
  4. Windows 8.1 crash ,BSOD
    By haim3307 in forum BSOD, Crashes, Kernel Debugging
    Replies: 10
    Last Post: 06-01-2015, 11:43 AM
  5. BSOD crash
    By Quintal999 in forum BSOD, Crashes, Kernel Debugging
    Replies: 1
    Last Post: 12-08-2012, 11:57 AM

Log in

Log in