Windows 10: BSOD On Just About Every Action

@axe0 The MemTest had 10 successful passes with no errors. The only other test mentioned was the Driver Verifier. Which spectacular backfired and required me to reset the computer to a previous state. I put down 'save documents' but evidently dmp files are not listed in the documents saved. I could try it again, but this time use a different method to turn the Verifier off, if you wish.

 

There are some ways to turn off driver verifier






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Sorry for late response, there was a medical emergency.
Will redo the Driver Verifier and post results shortly.

UPDATE
After I rebooted the PC to put Verifier into effect, it went through a 'scan and repair C drive' thing and then put me into the log in screen. The last time I used the Verifier I got BSOD within seconds. This time, it's been a few minutes and nothing has happened. It occurred to me that the scan and repair might have turned the Verifier off but the tutorial does not list a way to check to see if it is.

 

Alright so it finally crashed. Attached are the dmp files and BlueView screenshots.
Attachment 92219
Attachment 92220

 

You could check if driver verifier is enabled by entering (copy/paste) below command in an admin command prompt
Code: verifier /query[/quote] I'll leave the analysis to @Ztruker as he is the one that started troubleshooting.

 

Please post the results of verifier /query and verifier /querysettings from a Elevated Command Prompt, as verifier is not setup correctly:

Code: 2: kd> !verifier Verify Flags Level 0x00000000 STANDARD FLAGS: [X] (0x00000000) Automatic Checks [ ] (0x00000001) Special pool [ ] (0x00000002) Force IRQL checking [ ] (0x00000008) Pool tracking [ ] (0x00000010) I/O verification [ ] (0x00000020) Deadlock detection [ ] (0x00000080) DMA checking [ ] (0x00000100) Security checks [ ] (0x00000800) Miscellaneous checks [ ] (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 [ ] (0x00040000) Systematic low resources simulation [ ] (0x00080000) DDI compliance checking (additional) [ ] (0x00200000) NDIS/WIFI verification [ ] (0x00800000) Kernel synchronization delay fuzzing [ ] (0x01000000) VM switch verification [X] Indicates flag is enabled Summary of All Verifier Statistics RaiseIrqls 0x0 AcquireSpinLocks 0x0 Synch Executions 0x0 Trims 0x0 Pool Allocations Attempted 0x0 Pool Allocations Succeeded 0x0 Pool Allocations Succeeded SpecialPool 0x0 Pool Allocations With NO TAG 0x0 Pool Allocations Failed 0x0 Current paged pool allocations 0x0 for 00000000 bytes Peak paged pool allocations 0x0 for 00000000 bytes Current nonpaged pool allocations 0x0 for 00000000 bytes Peak nonpaged pool allocations 0x0 for 00000000 bytes[/quote] The dumps are similar to others you've uploaded, ntkrnlmp and AuthenticAMD. Neither was triggered by Driver Verifier.

Setup Driver Verifer again. Make sure you check the boxes specified in the tutorial then see what we get.

Attachment 92264

 

I'll have to do the test and post the results in a few hours

 

Alright so I ran the Verifier, got to the point where it would fail bootup due to it, used the command prompt to fix and got the results of verifier /query and verifier /querysettings
Attachment 92472
Attachment 92473

 

Verifier setup looks good. Can't read the small screen captures though.

Where is the DM_Log_collector output zip which "should" include a new dump?

For the future, redirect the output to a file then you can open the file in notepad and copy and paste it here.

Open command prompt.
Enter verifier /query > verifier.txt and press Enter.
Enter verifier /querysettings >> verifier.txt and press Enter.
Enter notepad verifier.txt and press Enter.

or you could string them all together in one command:

Copy this string:

verifier /query > verifier.txt & verifier /querysettings >> verifier.txt & notepad verifier.txt

then paste it into the Command Prompt window and press Enter. A notepad window will open.

Copy the contents of the notepad window to the clipboard (select all (Ctrl+A) then copy (Ctrl+C)).
Paste into a reply in this thread.

 

Attachment 92621Time Stamp: 07/27/2016 23:57:09.814


Verifier Flags: 0x00000610


Standard Flags:


[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.


Additional Flags:


[ ] 0x00000004 Randomized low resources simulation.
[X] 0x00000200 Force pending I/O requests.
[X] 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.


Verifier Statistics Summary


Raise IRQLs: 56859603
Acquire Spin Locks: 13228414
Synchronize Executions: 0
Trims: 0


Pool Allocations Attempted: 10292280
Pool Allocations Succeeded: 10292280
Pool Allocations Succeeded SpecialPool: 3148
Pool Allocations With No Tag: 41
Pool Allocations Not Tracked: 0
Pool Allocations Failed: 0
Pool Allocations Failed Deliberately: 0


Driver Verification List


MODULE: nvlddmkm.sys (load: 1 / unload: 0)


Pool Allocation Statistics: ( NonPaged / Paged )


Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0


MODULE: rt640x64.sys (load: 1 / unload: 0)


Pool Allocation Statistics: ( NonPaged / Paged )


Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0


MODULE: ndis.sys (load: 1 / unload: 0)


Pool Allocation Statistics: ( NonPaged / Paged )


Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0


MODULE: nvvad64v.sys (load: 1 / unload: 0)


Pool Allocation Statistics: ( NonPaged / Paged )


Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0


MODULE: nvhda64v.sys (load: 1 / unload: 0)


Pool Allocation Statistics: ( NonPaged / Paged )


Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0


MODULE: rtkvhd64.sys (load: 1 / unload: 0)


Pool Allocation Statistics: ( NonPaged / Paged )


Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0


MODULE: rtl8192su.sys (load: 1 / unload: 0)


Pool Allocation Statistics: ( NonPaged / Paged )


Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0


MODULE: dump_dumpata.sys (load: 0 / unload: 0)


MODULE: dump_atapi.sys (load: 2 / unload: 1)


Pool Allocation Statistics: ( NonPaged / Paged )


Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0


MODULE: dump_dumpfve.sys (load: 2 / unload: 1)


Pool Allocation Statistics: ( NonPaged / Paged )


Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0


MODULE: speedfan.sys (load: 1 / unload: 0)


Pool Allocation Statistics: ( NonPaged / Paged )


Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0


MODULE: nvstreamkms.sys (load: 1 / unload: 0)


Pool Allocation Statistics: ( NonPaged / Paged )


Current Pool Allocations: ( 0 / 0 )
Current Pool Bytes: ( 0 / 0 )
Peak Pool Allocations: ( 0 / 0 )
Peak Pool Bytes: ( 0 / 0 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0


Verifier Flags: 0x00000610


Standard Flags:


[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.


Additional Flags:


[ ] 0x00000004 Randomized low resources simulation.
[X] 0x00000200 Force pending I/O requests.
[X] 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.


Boot Mode:


Persistent


Rules:


All rules are using default settings


Verified Drivers:


nvlddmkm.sys
rt640x64.sys
ndis.sys
nvvad64v.sys
nvhda64v.sys
rtkvhd64.sys
rtl8192su.sys
dump_dumpata.sys
dump_atapi.sys
dump_dumpfve.sys
speedfan.sys
nvstreamkms.sys

And here's the dmp files from the log collector.

 

I'm at a loss at the moment. None of the dumps from the 27th were triggered by Driver Verifier.
Causes were ntkrnlmp, AuthenticAMD and svchost. Nothing I can point to to and say ah ha, that's it.

Try stressing the CPU and GPU, see if that gives a point of failure.

===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums

===================================================
Follow this tutorials to stress test your GPU:
FurMark - GPU Stress Test - Windows 10 Forums

If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..

 

Alright so I attempted to run Prime95 twice. The first time, it Blue Screened within 5 seconds of starting the test. The second, it went straight to immediate restart with no Blue Screen. As such, I only have the dmp files and screenshots involving the first crash.
Attachment 92910
Attachment 92912
The GPU Test went without any problems.

 

Code: BugCheck 124, {0, ffffe0011c03f8f8, 0, 0} Probably caused by : AuthenticAMD 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe0011c03f8f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.[/quote] The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

This is the error record:

Code: 1: kd> !errrec ffffe0011c03f8f8 =============================================================================== Common Platform Error Record @ ffffe0011c03f8f8 ------------------------------------------------------------------------------- Record Id : 01d1e9f164c68094 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 7/29/2016 23:32:03 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe0011c03f978 Section @ ffffe0011c03fa50 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : BUS error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000600f20 Processor ID : 0x0000000000000002 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe0011c03f9c0 Section @ ffffe0011c03fb10 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000002 CPU Id : 20 0f 60 00 00 08 04 02 - 0b 32 98 3e ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffe0011c03fb10 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe0011c03fa08 Section @ ffffe0011c03fb90 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSLG_GENERIC_ERR_*_NOTIMEOUT_ERR (Proc 3 Bank 5) Status : 0xf080000000080e0f[/quote] Similar problem on this Windows 7 system a few years ago. Read through all of it.

BSOD and Restarts

For that PC, the cause seems to have been defective RAM.
May need you to run memtest86+ again for 8 passes, only this time please take a picture of the results and post here. I know this is annoying but if you run it over night it's not too bad.

Just noticed, Driver Verifier is still enabled and active.
Code: 2: kd> !verifier Verify Flags Level 0x00000610 STANDARD FLAGS: [X] (0x00000000) Automatic Checks [ ] (0x00000001) Special pool [ ] (0x00000002) Force IRQL checking [ ] (0x00000008) Pool tracking [X] (0x00000010) I/O verification [ ] (0x00000020) Deadlock detection [ ] (0x00000080) DMA checking [ ] (0x00000100) Security checks [ ] (0x00000800) Miscellaneous checks [ ] (0x00020000) DDI compliance checking ADDITIONAL FLAGS: [ ] (0x00000004) Randomized low resources simulation [X] (0x00000200) Force pending I/O requests [X] (0x00000400) IRP logging [ ] (0x00002000) Invariant MDL checking for stack [ ] (0x00004000) Invariant MDL checking for driver [ ] (0x00008000) Power framework delay fuzzing [ ] (0x00040000) Systematic low resources simulation [ ] (0x00080000) DDI compliance checking (additional) [ ] (0x00200000) NDIS/WIFI verification [ ] (0x00800000) Kernel synchronization delay fuzzing [ ] (0x01000000) VM switch verification [X] Indicates flag is enabled Summary of All Verifier Statistics RaiseIrqls 0x421a3ad AcquireSpinLocks 0xe55f71 Synch Executions 0x3 Trims 0x0 Pool Allocations Attempted 0xe9dabb Pool Allocations Succeeded 0xe9dabb Pool Allocations Succeeded SpecialPool 0x1755 Pool Allocations With NO TAG 0x29 Pool Allocations Failed 0x0 Current paged pool allocations 0x0 for 00000000 bytes Peak paged pool allocations 0x0 for 00000000 bytes Current nonpaged pool allocations 0x0 for 00000000 bytes Peak nonpaged pool allocations 0x0 for 00000000 bytes[/quote] Probably not good to run Prime95 when verifier is still active. Please disable it then try Prime95 again. If you get the same error (AuthenticAMD) then go ahead and run memtest86+ again and post a picture of the result screen after at least 8 passes.

 

Disabled verifier, restarted, and tried stressing my CPU again. Once again, immediate Blue Screen. This time, a WHEA error. Something odd about Verifier still being on. Every other time, it Blue Screens me within 5 minutes. This time, it was on for almost an entire day? Either way, Prime95 caused an immediate Blue Screen.
Attachment 92937
I'll be putting memtest on, as soon as I find a flashdrive.

 

It's beginning to sound like you may have a defective CPU.