Windows 10: Multiple BSODs / New build / Lurking for a month

Hello,

So, I am have been having multiple BSODs from day 0 with my new PC build. I will try to be as thorough as I can to help you help me. I have been lurking and troubleshooting since early February, when my build began. I have clean installed (formatted primary drive every time, formatted secondary drives once) Windows about 3 times now chasing BSODs. I am at my wits end and am calling in for backup (I prefer to figure things out on my own since I then learn from it). My PC serves two roles, Gaming and Virtualization. Ideally, I would be dual booting Windows 10 for light gaming with my son and Debian for work/programming/virtualization.

Home built PC:
Mobo: Asus H170 Pro Gaming
CPU: I7 6700K
RAM: Corsair Vengeance LPX - 32GB
GPU: Nvidia GTX 970
PSU: Corsair HX850 (old, ~4yrs, did not replace for this build)
Primary HDD: Samsung 850 256GB
Secondaries: Samsung 840 256GB (old, from last system, zeroed before first boot with the new system)
WD Green 2TB (old, from last system, zeroed before first boot with the new system)

In February, I built the PC, installed Win10, setup dual boot with Debian, received several BSODs in Win10s (I do not have these dumps, but they were of the IRQL, memory corruption, --- memory related). So, I ran memtest on my RAM, did 2 passes, came back passed/no issues. I figured I would then get it stable with just Windows 10 before attempting a dual boot system. Fresh installed Win10, loaded all drivers from ASUS' support site, updated BIOS, configured Windbg, and started monitoring event viewer. Several similiar BSODs later, decided it may be the ASMedia USB3.1 driver. Removed it, allowed Win10 to install the ASMedia driver from Windows updates. Had a slight stability increase and pressed forward. I then stressed tested with Prime95 for 30 mins, FurMark for 30 mins, and ran memtest again for 3 passes. Still BSODing.
Ran driver verifier, narrowed it down to some old 32bit drivers for my mouse and VMWare Workstation, uninstalled both. Still BSODing. OK, let's do a fresh install, install the NIC firmware (Windows doesn't detect it) and let Windows push in the drivers, nothing from me. Ran memtest for 6 passes. Increased stability. Sweet. Setup dual booting with Ubuntu. On Windows, further installed Intel's Engine for my chipset, allowed NVidia to update to the current driver, installed Samsung Magician, and I am still BSODing, but with new (to me) exceptions. Now, I am getting KMODE and System Thread exception BSODs.

If it's any relevance, when I was dual booting with Debian (and now with Ubuntu), they too were complaining. Every time it could not list the fault and I didn't do my due diligence by reading the logs (I would get frustrated because I was already working and would switch to my laptop).

Attached is the zip file from your forum posting guidelines. I am ready to listen to some Ghetto Boys and take a bat to this PC.

Attachment 71022

Edit: I am currently running driver verifier, but it hasn't caught anything as of yet.
Edit2: BSOD directly after making this post. Attached is the *.dmp file with a *.txt extension.

Edit3: Noticed the updatelog from the forum tool used the wrong PS call. Attached is the output from Get-WindowsUpdateLog.
Attachment 71031

:)

 

No Refresh/re-rendering on parts of a program window

Hi,

I installed the latest 15063 today and after several hours of use the refresh issue seems to now be resolved. Finally after months of frustration!!

Hopefully there are no other problems lurking with the build.... everything seems good at the moment.

 

Multiple BSOD on new Ryzen build

I don't understand your answer, i'm french ^^ so if you can translate or add step, i have the same problem, i can't boot without a bsod with a problem of memory

 

Please remove the file of edit2, the content becomes unreadable when you change the extension.

About the windowsupdate.log, I don't understand much about it but you have a few Windows Update failure Windows Error Reports.
Code: 3/15/2016 12:11 AM Windows Error Reporting Fault bucket 125681010751, type 5 Event Name: WindowsUpdateFailure3 Response: Not available Cab Id: 0 Problem signature: P1: 10.0.10586.103 P2: 80248007 P3: 92A8E0C4-F39D-4464-966C-AD55A7FD5E64 P4: Install P5: 201 P6: 0 P7: 0 P8: UpdateOrchestrator P9: {9482F4B4-E343-43B6-B170-9A65BC822C77} P10: 0 Attached files: C:\Windows\Temp\WERCF15.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_10.0.10586.103_9e4dea1cb2c1b48565a8c4e918fdd74263e2e_00000000_137bffc9 Analysis symbol: Rechecking for solution: 0 Report Id: 7baeb6b5-ea42-11e5-bdc8-305a3a7f48e0 Report Status: 0 Hashed bucket: 51b1674b8237014b83f7c8e2e1e7087c 3/15/2016 12:11 AM Windows Error Reporting Fault bucket 125605098547, type 5 Event Name: WindowsUpdateFailure3 Response: Not available Cab Id: 0 Problem signature: P1: 10.0.10586.103 P2: 80070103 P3: 4A2305D9-E940-48E6-9CE4-D11964F7DC2F P4: Install P5: 200 P6: 0 P7: 80070103 P8: UpdateOrchestrator P9: {9482F4B4-E343-43B6-B170-9A65BC822C77} P10: 0 Attached files: C:\Windows\Temp\WERCE97.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_10.0.10586.103_cf748a21a9df66704971e8b42aa9f9e86f23eef_00000000_132bd28f Analysis symbol: Rechecking for solution: 0 Report Id: 7baeb6b3-ea42-11e5-bdc8-305a3a7f48e0 Report Status: 0 Hashed bucket: 2bfd6c65f7066bd8ed4910170c5ff3f4 3/15/2016 12:11 AM Windows Error Reporting Fault bucket 125603917371, type 5 Event Name: WindowsUpdateFailure3 Response: Not available Cab Id: 0 Problem signature: P1: 10.0.10586.103 P2: 80248007 P3: CF1A65E1-D207-4D5E-B310-77509030AAC1 P4: Install P5: 200 P6: 0 P7: 0 P8: UpdateOrchestrator P9: {9482F4B4-E343-43B6-B170-9A65BC822C77} P10: 0 Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_10.0.10586.103_981ccc1c1f11364785bf80a973efb7a55899863_00000000_132bd0e9 Analysis symbol: Rechecking for solution: 0 Report Id: 7baeb6b4-ea42-11e5-bdc8-305a3a7f48e0 Report Status: 0 Hashed bucket: 9825501d1f7d3929d9e88ca4e35e1edd 3/15/2016 12:11 AM Windows Error Reporting Fault bucket , type 0 Event Name: WindowsUpdateFailure3 Response: Not available Cab Id: 0 Problem signature: P1: 10.0.10586.103 P2: 80248007 P3: 92A8E0C4-F39D-4464-966C-AD55A7FD5E64 P4: Install P5: 201 P6: 0 P7: 0 P8: UpdateOrchestrator P9: {9482F4B4-E343-43B6-B170-9A65BC822C77} P10: 0 Attached files: C:\Windows\Temp\WERCF15.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_10.0.10586.103_9e4dea1cb2c1b48565a8c4e918fdd74263e2e_00000000_cab_1167cf14 Analysis symbol: Rechecking for solution: 0 Report Id: 7baeb6b5-ea42-11e5-bdc8-305a3a7f48e0 Report Status: 4 Hashed bucket: 3/15/2016 12:11 AM Windows Error Reporting Fault bucket , type 0 Event Name: WindowsUpdateFailure3 Response: Not available Cab Id: 0 Problem signature: P1: 10.0.10586.103 P2: 80070103 P3: 4A2305D9-E940-48E6-9CE4-D11964F7DC2F P4: Install P5: 200 P6: 0 P7: 80070103 P8: UpdateOrchestrator P9: {9482F4B4-E343-43B6-B170-9A65BC822C77} P10: 0 Attached files: C:\Windows\Temp\WERCE97.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_10.0.10586.103_cf748a21a9df66704971e8b42aa9f9e86f23eef_00000000_cab_1497cea7 Analysis symbol: Rechecking for solution: 0 Report Id: 7baeb6b3-ea42-11e5-bdc8-305a3a7f48e0 Report Status: 4 Hashed bucket: 3/15/2016 12:11 AM Windows Error Reporting Fault bucket , type 0 Event Name: WindowsUpdateFailure3 Response: Not available Cab Id: 0 Problem signature: P1: 10.0.10586.103 P2: 80248007 P3: CF1A65E1-D207-4D5E-B310-77509030AAC1 P4: Install P5: 200 P6: 0 P7: 0 P8: UpdateOrchestrator P9: {9482F4B4-E343-43B6-B170-9A65BC822C77} P10: 0 Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_10.0.10586.103_981ccc1c1f11364785bf80a973efb7a55899863_00000000_cab_05c7ce97 Analysis symbol: Rechecking for solution: 0 Report Id: 7baeb6b4-ea42-11e5-bdc8-305a3a7f48e0 Report Status: 4 Hashed bucket:[/quote] If you have driver verifier enabled,Please disable driver verifier

• Open an admin command prompt
• Enter "verifier/reset" (without quotes)

There is enough data to say that you have hardware problems,

• Clean install doesn't help,
• Driver verifier doesn't flag any drivers,
• Some dumps show 'hardware' as 'probable cause'.

Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80195d37a36, ffffd00021806890, 0} Probably caused by : hardware ( nt!IopDereferenceVpbAndFree+46 ) Followup: MachineOwner[/quote] Please boot into the BIOS and let me know what the 3.3v, 5v and 12v values are.

Please make sure the firmware of your SSD's are up to date.

Please run CPU-Z | Softwares | CPUID, open it and make screenshots of the following tabs

• CPU
• Mainboard
• Memory
• SPD*
• Graphics

*SPD shows the details of each module, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each module.Please post each screenshot in your next reply/replies.






Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



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





Diagnostics Test

HDD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

• Short Drive Self Test
• Short generic
• Long generic

If the short generic fails, no need for the long generic.


Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk
Disk Check - Windows 7 Help Forums



Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

 

Alright, ran all tests except for memtest. Last time, at 6 passes, this took ~30 hrs. I will initiate memtest after this post, however. All tests came back fine.
SSD Firmware: Current for both.
Bios Voltages:
3.3v - 3.296
5v - 5.000
12v - 12.096
SeaTools: Passed all 3 tests
CheckDisk came back ok for all 3 drives.
HDTune error check came back clean on all 3 drives. Attached are the screenshots for CPU-Z and HDTune.

Attachment 71140

 

What are the XMP possibilities in the BIOS?

 

There are two options for XMP:
Disabled (Current value)
Profile 1 - XMP DDR4-2133 13-15-15-28-1.20v

I have tried both options before in the past without any noticeable difference. On Monday of this week, I had selected Profile 1 and last night, prior to running memtest, I had put it back to Disabled. Do you still want me to run memtest? I had to quit the test to check the XMP BIOS settings.

 

I only want to make sure no OC'ing is present *Smile
OC'ing pushes the component (a bit), this may cause problems on unstable systems which is why I want to make sure there is no OC'ing.

 

No worries friend, no OCing present. It's a slight mismatch because of the K-series CPU and non overclocking mobo, but it is what it is. Are there any other tests you want me to run? Any likely suspects yet?

 

For now only everything of hardware that can cause memory corruption is a suspect,

• Hard drive,
• RAM,
• Mainboard,
• PSU, power problems can cause various of problems
• GPU (vram, didn't see anything about vram, this can be ignored)

You could also run a live linux, without installation, it runs only on the memory so if it crashes either the memory or the mainboard is the cause. This can be used for as long as you want.
Live linux distro download: Download - Linux Mint

 

Alright, will do. I think I have a Debian live usb laying around on my desk. I'll try this tonight.

 

A lot of errors within the first 30 minutes Most were unidentifiable by report, but a few seemed likes issues loading gnome aptk. I started memtest and will let it go for 8+ passes. Expect it not to be complete until the end of the weekend.

 

Welp, 9 passes, no problems.

 

Please make sure no unnecessary peripheral is connected to rule such connections out.

Do you get problems when you remove the secondary hard drives?

I want to work to a system with as less as possible connected, this would make it easier to find the root cause.
You may want to read following guide for stripping down your system, it is the same I want to work to but it contains extra stuff that may be useful.
Hardware Stripdown Troubleshooting