Getting regular BSOD's playing games, tried almost everything


  1. Posts : 3
    Windows 10
       #1

    Getting regular BSOD's playing games, tried almost everything


    Not sure where to begin, recently I have been experiencing Blue Screens and the cause appeared to be ntoskrnl.exe giving the error. I have tried updating all the drivers and even checking RAM but so far nothing seems to help, I removed a few dud drivers (AsUpIo.sys and AsIO.sys) which seemed to help but now it's still doing it.

    I also tried several Nvidia drivers which seemed to help at first but now it seems to happen more frequently.

    Really not sure what's causing the error now, short of reinstalling Windows 10 (which I'd want to avoid if possible) there isn't much else I can do
      My Computer


  2. Posts : 14,903
    Windows 10 Pro
       #2

    Hi Moonky,

    Welcome to the 10forums :)

    The crashes are 0xD1, an indication of a driver, it seems you've used driver verifier already although I'm wondering where you get those settings.
    Code:
      STANDARD FLAGS:
        [X] (0x00000000) Automatic Checks
        [X] (0x00000001) Special pool
        [X] (0x00000002) Force IRQL checking
        [X] (0x00000008) Pool tracking
        [ ] (0x00000010) I/O verification
        [X] (0x00000020) Deadlock detection
        [ ] (0x00000080) DMA checking
        [X] (0x00000100) Security checks
        [X] (0x00000800) Miscellaneous checks
        [X] (0x00020000) DDI compliance checking
    
      ADDITIONAL FLAGS:
        [ ] (0x00000004) Randomized low resources simulation
        [ ] (0x00000200) Force pending I/O requests
        [ ] (0x00000400) IRP logging
        [ ] (0x00002000) Invariant MDL checking for stack
        [ ] (0x00004000) Invariant MDL checking for driver
        [ ] (0x00008000) Power framework delay fuzzing
        [ ] (0x00010000) Port/miniport interface checking
        [ ] (0x00040000) Systematic low resources simulation
        [ ] (0x00080000) DDI compliance checking (additional)
        [ ] (0x00200000) NDIS/WIFI verification
        [ ] (0x00800000) Kernel synchronization delay fuzzing
        [ ] (0x01000000) VM switch verification
        [ ] (0x02000000) Code integrity checks
    
        [X] Indicates flag is enabled
    However since driver verifier was unable to flag any driver + pagefaults (drivers passing bad data to memory or passing data to corrupted memory) there are 2 options.
    1. Driver verifier didn't flag any driver because it didn't check the setting that was violating
    2. The pagefault was caused due to bad memory.

    I suggest that you start with running MemTest86+ for 8 straight completed passes or until errors show up as the tutorial describes.




    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 complete 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.


    Make a photo of the result and post it please.

    Addition:
    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
    If errors show up and you see them a lot later, no problem, the errors don't affect the test.
    Code:
    6: kd> k
     # Child-SP          RetAddr           Call Site
    00 ffffd001`869472f8 fffff803`5fbd62e9 nt!KeBugCheckEx
    01 ffffd001`86947300 fffff803`5fbd4ac7 nt!KiBugCheckDispatch+0x69
    02 ffffd001`86947440 00000000`00000000 nt!KiPageFault+0x247
      My Computers


  3. Posts : 3
    Windows 10
    Thread Starter
       #3

    axe0 said:
    Hi Moonky,

    Welcome to the 10forums :)

    The crashes are 0xD1, an indication of a driver, it seems you've used driver verifier already although I'm wondering where you get those settings.
    Code:
      STANDARD FLAGS:
        [X] (0x00000000) Automatic Checks
        [X] (0x00000001) Special pool
        [X] (0x00000002) Force IRQL checking
        [X] (0x00000008) Pool tracking
        [ ] (0x00000010) I/O verification
        [X] (0x00000020) Deadlock detection
        [ ] (0x00000080) DMA checking
        [X] (0x00000100) Security checks
        [X] (0x00000800) Miscellaneous checks
        [X] (0x00020000) DDI compliance checking
    
      ADDITIONAL FLAGS:
        [ ] (0x00000004) Randomized low resources simulation
        [ ] (0x00000200) Force pending I/O requests
        [ ] (0x00000400) IRP logging
        [ ] (0x00002000) Invariant MDL checking for stack
        [ ] (0x00004000) Invariant MDL checking for driver
        [ ] (0x00008000) Power framework delay fuzzing
        [ ] (0x00010000) Port/miniport interface checking
        [ ] (0x00040000) Systematic low resources simulation
        [ ] (0x00080000) DDI compliance checking (additional)
        [ ] (0x00200000) NDIS/WIFI verification
        [ ] (0x00800000) Kernel synchronization delay fuzzing
        [ ] (0x01000000) VM switch verification
        [ ] (0x02000000) Code integrity checks
    
        [X] Indicates flag is enabled
    However since driver verifier was unable to flag any driver + pagefaults (drivers passing bad data to memory or passing data to corrupted memory) there are 2 options.
    1. Driver verifier didn't flag any driver because it didn't check the setting that was violating
    2. The pagefault was caused due to bad memory.

    I suggest that you start with running MemTest86+ for 8 straight completed passes or until errors show up as the tutorial describes.




    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 complete 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.


    Make a photo of the result and post it please.

    Addition:
    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
    If errors show up and you see them a lot later, no problem, the errors don't affect the test.
    Code:
    6: kd> k
     # Child-SP          RetAddr           Call Site
    00 ffffd001`869472f8 fffff803`5fbd62e9 nt!KeBugCheckEx
    01 ffffd001`86947300 fffff803`5fbd4ac7 nt!KiBugCheckDispatch+0x69
    02 ffffd001`86947440 00000000`00000000 nt!KiPageFault+0x247
    Hey thanks for replying, I am not actually sure where I found the settings for verifier because I was searching so many places to find a fix that it's hard to keep track of where I found it.

    I've ran Memtest previously but it didn't really find anything, I will test it again and see if it does produce anything this time. Also I have since disabled something which I heard can cause memory leaks so we'll see if that helped.

    Will report back!
      My Computer


  4. Posts : 14,903
    Windows 10 Pro
       #4

    What exactly is it that you've disabled?
      My Computers


  5. Posts : 3
    Windows 10
    Thread Starter
       #5

    axe0 said:
    What exactly is it that you've disabled?
    Well I don't know if it was enabling or disabling but there was a registry fix I found with others that had the same problem so I changed that for now.

    Windows 10 High Ram Usage? Can't find a fix, need some guidance. : Windows10
      My Computer


  6. Posts : 14,903
    Windows 10 Pro
       #6

    Standard that setting is disabled, the page file isn't something that causes memory leaks (unless there is a bug), the way it works is to make your system keep running smooth without any interference.
    What you've said to the system is to empty the page file when you shut down, the page file works similar to the RAM only the page file is meant for programs that haven't been used for a longer period.
      My Computers


 

  Related Discussions
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 19:36.
Find Us




Windows 10 Forums