BSOD's on start up


  1. FL630
    Posts : 4
    W10
       New #1

    BSOD's on start up


    Hi,

    Was pointed in this general direction as my regular forum couldn't help me with the multiple and consistant BSOD's on startup are plaguing me.

    They only happen on start up, sometimes just as the OS loads, sometimes once I'm on the desktop. If my desktop shows for about 30 seconds or so I know I'm stable.

    Sometimes I'll get a single BSOD on start, sometimes 4 or 5.

    I've had the following errors show:
    IRQL_NOT_LESS_OR_EQUAL
    KERNAL_SECURITY__CHECK_FAILURE
    SYSTEM_SERVICE_EXCEPTION (win32kfull.sys)
    MEMORY_MANAGEMENT
    BAD_POOL_CALLER
    PFN_LIST_CORRUPT
    PAGE_FAULT_IN_NONPAGED_AREA
    SYSTEM_SERVICE_EXCEPTION
    BAD_POOL_HEADER

    This is not an extensive list, I do get more but don't always load my camera in time to take a photo so I can remember. Many of these have appeared multiple times too.

    My PC spec is:
    i7-4790k (overclocked to a stable 4.6GHz @ 1.32v)
    Gigabyte Z97X Gaming-G1 Motherboard
    Asus Strix GTX 980 (overclocked and very stable)
    16GB (4x4GB) HyperX Savage DDR3 Memory
    240GB HyperX Savage SSD.

    I have run all of the CPU and stress tests multiple times and it does not BSOD. I have also run 4 passes of memtest to see if my RAM is good, and it seems to come back clean. Drivers are all up to date.

    Using Windows 10 Beta on slow release.

    I've attached the .zip as required.

    Cheers,
    FL630
      My Computer
    Quote Quote

  3. axe0
    Posts : 14,903
    Windows 10 Pro
       New #2

    Hi FL630,

    Welcome to the 10forums.

    I have taken a look at the most recent dump files and below is my analyse.

    Please remove MSI Afterburner and RivaTuner, both are known for causing BSOD's.

    Please move some files from the C partition to increase the free space to at least 10-15%.
    Every partition needs at least 10-15% free space so Windows can do its thing in the background.
    warning   Warning
    Less free space could cause BSOD's


    The 0x1A(MEMORY_MANAGEMENT) and the 0x4E(PFN_LIST_CORRUPT) are pointing to memory problems as they are usually caused by memory.
    The 0x50(PAGE_FAULT_IN_NONPAGED_AREA) has also memory problems as 1 of the usual causes.
    The 0xC2(BAD_POOL_CALLER) is caused by the GPU.
    Please follow instructions below carefully
    Code:
    Probably caused by : dxgkrnl.sys // DirectX graphics kernel

STACK_TEXT:  
ffffd001`4d97dc28 fffff801`54359aec : 00000000`000000c2 00000000`00000099 ffffc001`c3ff8308 00000000`00000000 : nt!KeBugCheckEx
ffffd001`4d97dc30 fffff801`53e2f935 : ffffe000`20601140 fffff801`53e91772 ffffe000`20601140 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd001`4d97dc70 fffff801`53e92f8b : ffffc001`c3ff82f8 00000000`00000001 00000000`000000c3 ffffe000`20601140 : nt!VerifierFreeTrackedPool+0x41
ffffd001`4d97dcb0 fffff800`d8476111 : 00000000`00000000 ffffe000`26bcbe00 ffffe000`20601140 ffffe000`26d87840 : nt!ExFreePool+0x2c3
ffffd001`4d97dd90 fffff800`d8404fb1 : ffffc001`c3ff8450 ffffe000`26bcbe00 ffffe000`26bcbe00 ffffd001`4d97dfa9 : dxgkrnl!operator delete+0x11
ffffd001`4d97ddc0 fffff800`d8409a27 : ffffc001`c3fd61b8 ffffd001`4d97dfa9 ffffc001`c3fb0f10 fffff800`d8476111 : dxgkrnl!DMMVIDPNPRESENTPATH::`vector deleting destructor'+0x21
ffffd001`4d97ddf0 fffff800`d8403f54 : 00000000`00000001 ffffc001`c3ffbec0 ffffe000`26bcbe00 ffffd001`4d97dfa9 : dxgkrnl!DoublyLinkedList<DMMVIDPNTARGET>::Clear+0x5b
ffffd001`4d97de20 fffff800`d847b2ed : ffffc001`c3fda110 ffffd001`4d97dfa9 00000000`00000001 fffff800`d8476111 : dxgkrnl!DMMVIDPNTARGETSET::`vector deleting destructor'+0x14
ffffd001`4d97de50 fffff800`d8403e74 : 00000000`00000001 ffffe000`26bcbe00 00000000`00000001 fffff800`d8404fb1 : dxgkrnl!DMMVIDPN::~DMMVIDPN+0xb9
ffffd001`4d97de80 fffff800`d8403d2e : 00000000`00000000 00000000`00000000 ffffc001`c3fb0e40 fffff800`d84803ce : dxgkrnl!DMMVIDPN::`vector deleting destructor'+0x14
ffffd001`4d97deb0 fffff800`d840709c : ffffd001`4d97df78 ffffe000`26bcbe00 ffffe000`26be0010 ffffd001`4d97e090 : dxgkrnl!ReferenceCounted::Release+0x3a
ffffd001`4d97dee0 fffff800`d84a39fc : ffffc001`c322b450 ffffe000`26bcbe00 ffffd001`4d97dfa9 ffffe000`26bcbe00 : dxgkrnl!auto_rc<DMMVIDPN>::reset+0x34
ffffd001`4d97df10 fffff800`d847c073 : ffffe000`26be0010 fffff800`d840a38a 00000000`00000004 00000000`00004403 : dxgkrnl!_BtlPreAcquireSharedAccess<&CCD_BTL_ACTIVE_PATHS_COLLECTOR::_CollectAllPathsAdaptersCallback>+0x28c
ffffd001`4d97e010 fffff800`d848e2db : 00000000`00000000 ffffd001`4d97e0e0 00000000`00000000 fffff800`00000000 : dxgkrnl!DXGGLOBAL::IterateAdaptersWithCallback+0xcf
ffffd001`4d97e070 fffff800`d84867dc : 00000000`00000000 00000000`00000000 ffffd001`4d97e150 fffff800`d849215a : dxgkrnl!CCD_BTL::RetrieveAllPaths+0x4b
ffffd001`4d97e0f0 fffff800`d8492446 : 00000000`00200010 00000000`00000000 00000000`00000001 fffff800`d8410d17 : dxgkrnl!CCD_TOPOLOGY::RetrieveAllPaths+0x40
ffffd001`4d97e120 fffff800`d849215a : 00000000`000000f4 fffff800`d849215a ffffd001`4d97e428 00000000`00200010 : dxgkrnl!DxgkGetPathsModality+0x216
ffffd001`4d97e2f0 fffff800`d8491e1c : 00000000`00000001 ffffd001`4d97e459 00000000`047f8fce 00000000`00000000 : dxgkrnl!GetRequestedPathsModality+0x8a
ffffd001`4d97e3d0 fffff800`d84917f6 : ffffd001`00000001 00000000`00000004 ffffd001`4d97e5a4 00000000`00000001 : dxgkrnl!QueryDisplayConfigInternal+0xe8
ffffd001`4d97e4a0 fffff961`865ea904 : 00000000`40000001 ffffd001`4d97e600 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkQueryDisplayConfig+0xa6
ffffd001`4d97e510 fffff961`8634301e : 00000000`00000000 ffffd001`4d97e670 ffffd001`4d97ead0 00000000`00000000 : win32kbase!DrvQueryDisplayConfig+0x84
ffffd001`4d97e570 fffff961`86342f97 : 00000000`00000000 00000000`00000000 ffffd001`4d97e718 00000000`00000000 : win32kfull!IsNativeOrientationPortrait+0x5a
ffffd001`4d97e6f0 fffff961`86605779 : 00000000`00000000 00000000`00000000 ffffd001`4d97ead0 00000000`00000002 : win32kfull!xxxUserReinitializeAutoRotation+0x117
ffffd001`4d97e790 fffff961`863426e8 : 00000063`7057f710 00000063`7057f810 ffffd001`4d97eb80 00000000`00000000 : win32kbase!RemoteConnect+0x389
ffffd001`4d97e840 fffff801`53d77863 : ffffe000`26d87840 00000063`7057f710 00000000`00000000 00000000`00000020 : win32kfull!NtUserRemoteConnect+0x208
ffffd001`4d97eb00 00007ffb`ee8fbaba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000063`7057f6c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`ee8fbaba



    Diagnostic Test

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.


    Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia.



    Diagnostic test

     GPU TEST


    Run Furmark to test your GPU. Furmark tutorial

    Note   Note
    Run Furmark for around 30 minutes


    warning   Warning
    Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high
      My Computers
    Quote Quote

 

  Related Discussions
BSOD on cold start up
in BSOD Crashes and Debugging

Hi The BSOD, that happens on a cold start up (when the computer has been turned off overnight) has been happening on random occasions ever since I built the computer. I've reinstalled windows, twice. I had thought it might be a hardware issue and...
BSOD at Start-Up
in BSOD Crashes and Debugging

Hi, This morning, I attempted to start my desktop PC and it gave me a BSOD with the error KERNEL_SECURITY_CHECK_FAILURE and it prompted an automatic restart. The restart went without any problems and the desktop is functional and I haven't...
BSOD at start up
in BSOD Crashes and Debugging

Hello, When I boot my pc for the first I always get an BSOD or my pc is just stuck and won't do anything. When I hit the reset button it starts up like it supposed to do. And everything is just fine even when I restart it. But if it is off for...
Had BSOD upon computer start
in BSOD Crashes and Debugging

So i had a BSOD upon computer startup, not sure what caused it my diagnostics says it was norton but i'm kind of suspicion on this as i have never had a issue with all the years i have used it, i collected the info from your own diagnostics...
Crashed BSOD now cannot start
in BSOD Crashes and Debugging

Hi, I cannot provide the debug data as I can't get it off my computer which keeps crashing. I just moved to the UK from NZ a week ago and have been using my laptop without any issues here until tonight to prepare for my job I start on Monday. ...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

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




Windows 10 Forums