Windows 10: BSOD and restarts after bug control 0x0000000a and more random errors

I started the test. You're right... it's gonna take a loooong time... ;-)
Will there be a test log somewhere? I expect to have a rebooted windows in the morning...
forgive me my noobiness... left PC since the 1st pentium for Pro-Mac. Mac isn't pro anymore, so a switch is needed. Many will follow.

Thanx!

 

Hey everyone,

I did extensive testing with the memory. After testing all modules without errors, I went to the slots. Slot 3 gave an error on a module, and when I put in another in slot 3, all was normal again. Was about to pull out my hair, and just before smacking the whole thing 3 floors below on the street paves, I decided to strip the whole thing. Re-installing every single component, every single wire, making sure I had no bend pins on the Mobo, and while at it, removed the BIOS battery. After doing this carefully, and thoroughly, the system responds like it should again!!! The windows maintenance graph stays at 10, whilst fluctuating heavily earlier - even after 3 or 4 reinstalls.

Coming from Mac, this was a huge jump in the dark for me going through every single letter in the manual for re-assembling and re-wiring the PC. I'm astonished how troublesome on one side, but how flexible and customizable on the other side a PC can be.

I want to thank everyone for helping me getting on the right track, and starting to do thorough testing. Problem solved, no idea what the problem was, but finally I have something less to worry about.

Kindest regards!

Bob

 

Hey all,

I re-opened this old post since the problems started again, on a new windows install.

First of all, I memtested every single stick up to 8 passes in slot 1. No errors.
Then I tested all the sticks, up to 4 passes. No errors.

Then I did a stress-test with aida 64 for 2 hours. System stable, temperatures well within limits (maxed 76° or so)
I updated my realtek audio-driver, and installed the nvidia drivers from the nvidia official website.

After that, I started a furmark test to stress the GPU. After 15 minutes or so... bam, BSOD with the driver_irql_not_less_or_equal error...

Upon consulting the maintenance page I get this error in attachment. Could it be a PSU problem? The PSU always worked perfectly before I changed the MOBO's...

If you need other info from the logs, I'll be happy to provide it!
Any help very much appreciated!

 

Please update with a new zip file.
If possible please change the default language to English before using the DM log collector so that we can troubleshoot the logs using English search words.
BSOD - Posting Instructions - Windows 10 Forums

 

Thank you for the reply.

I changed the language to English like you asked, and ran the dm_log_collector.
If anything else needed, please let me know.

 

I conducted another Furmark test, as they seem to be certain to create a BSOD.
Another minidump attached, I hope it helps

 

Code: BugCheck 51, {1, ffffe38d53276000, 93d94020, 27c}Probably caused by : ntkrnlmp.exe ( nt!HvpReleaseCellPaged+1620b7 )[/quote] Code: BugCheck D1, {fffff803c29fa226, 2, 8, fffff803c29fa226}Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+23d )[/quote] Code: USBHUB3_DEVICE_ENUMERATION_FAILURE[/quote] USBHUB3.sys USB3 HUB Driver
Info - http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx Windows Update

Code: nvlddmkm.sys[/quote] nvlddmkm.sys nVidia Video drivers Download Drivers | NVIDIA
Get from OEM for laptops


Code: Event[269]: Log Name: System Source: Microsoft-Windows-WindowsUpdateClient Date: 2017-06-25T22:13:53.929 Event ID: 20 Task: Windows Update Agent Level: Error Opcode: Installation Keyword: Installation,Failure User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-F7TH2GR Description: Installation Failure: Windows failed to install the following update with error 0x80070103: NVIDIA - Display - 5/1/2017 12:00:00 AM - 22.21.13.8205.[/quote] Code: Event[476]: Log Name: System Source: Microsoft-Windows-WindowsUpdateClient Date: 2017-06-25T22:22:06.696 Event ID: 20 Task: Windows Update Agent Level: Error Opcode: Installation Keyword: Installation,Failure User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-F7TH2GR Description: Installation Failure: Windows failed to install the following update with error 0x80070103: INTEL - System - 10/3/2016 12:00:00 AM - 10.1.1.38.[/quote]

1) The Nvidia video driver was previously uninstalled. It may be conflicting with other software or needs to be rolled back.
Uninstall all Nvidia drivers/softwareThe best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website.

When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.
Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download

2) Uninstall Usbhub3.sys
Click Start, and then click Run.In the Open box, type devmgmt.msc, and then click OK.
Device Manager opens.
Expand Universal Serial Bus controllers.Note You might have to scroll down the list to find this item.Right-click the affected USB Root Hub, and then click Uninstall to remove it.
Restart the computer. After the computer starts, Windows will automatically scan for hardware changes and reinstall all the USB root hubs that you uninstalled.

 

thank you! I'm going to do this right away.
So does this mean I can rule out any faulty hardware?

 

Update: System seems stable now. Still testing fur mark and aida64 for a few hours, no BSOD. Let's hope this solves the problem.

For future reference, is this something I have to do every time on a new Windows install?
I'm puzzled as of why a clean install conflicts the hardware.

Could it be that the Windows Nvidia driver leaves conflicting traces when I install the drivers from nvidia.com?

Also, the usb3hub.sys - is it possible there is conflicting or old hardware?

Or is it just the new creator-update bug?

Thank you for the reply, and many, many thanks for helping me out!!!

Kind regards, and enjoy your weekend!

Bob

 

Hello there,

The BSOD ghost is completely back.
Multiple times a day even, so I started to dig again.

Here is what I did:

Ran a FULL memtest, for 10 passes... all in the blue
Then I did a verifier.exe, and the odd stuff is that I get a BSOD at bootup when my saitek drivers, or my CH Products drivers are selected. Having rudder pedals from saitek, and a joystick and thruster from CH Products, and separately giving a BSOD, is making me suggest there is something very wrong with my USB setup?

I attached some of the latest dumps this evening. Can somebody shed their expertise on this? I have this setup from April, and still struggling.

Thank You very much!

 

Hi Looneytoon1975 ,

It's been approximately 1 1/2 months since your last post.
The bsod mini dump indicate that you are using Windows driver verifier.
There was 1 misbehaving driver that appeared in the 4 bsod mini dump files.

1) Please fill in your system specs
Please follow this tutorial and download the tool.
The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.

System Info - See Your System Specs - Windows 7 Help Forums


In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.


2) Turn off Windows driver verifier
3) Open administrative command prompt and type or copy and paste:
4) sfc /scannow
5) dism /online /cleanup-image /restorehealth
6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

7) Open administrative command prompt and type: chkdsk /x /f /r
This may take many hours so plan to run overnight.
8) Post the results into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials


9) Run one of the SMART tests on your drives:
CrystalDiskInfo - Software - Crystal Dew World:
Download Center - Crystal Dew World
CrystalDiskMark - Software - Crystal Dew World
Software - Crystal Dew World

HD Tune: HD Tune website

Hard Disk Sentinel - HDD health and temperature monitoring: Hard Disk Sentinel - HDD health and temperature monitoring

When the SMART test has completed open the Microsoft snipping tool and make images of the results to post into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

Check the health,
scan for errors, no quick scan but full scan
run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

10) Uninstall and reinstall the joy stick driver: chdrvr03.sys

Updating a driver: Microsoft Community

11) After all of the above create a brand new restore point
12) make a back up image using Macrium:
Macrium Software | Your Image is Everything
13 ) place the backup image on another drive
14) turn on windows driver verifier with these test settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
15) make sure you know the 3 methods to turn off Windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials



Code: Event[8467]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-08-11T12:51:24.887 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-F7TH2GR Description: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.[/quote] chdrvr03.sys CH Products joysticks (and other flight-sim related controllers) http://www.chproducts.com/retail/downloads.html
Code: Event[3360]: Log Name: System Source: Service Control Manager Date: 2017-07-24T18:10:16.388 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-F7TH2GR Description: A service was installed in the system.Service Name: chdrvr03Service File Name: \SystemRoot\System32\drivers\chdrvr03.sysService Type: stuurprogramma voor kernelmodusService Start Type: starten op aanvraagService Account:[/quote] Code: chdrvr03 chdrvr03 chdrvr03 Kernel Manual Running OK TRUE FALSE 0 15,360 0 24/08/2012 11:10:59 C:\Windows\system32\drivers\chdrvr03.sys[/quote] Code: 31/07/2017 21:16 Windows Error Reporting Fault bucket AV_chdrvr01!unknown_function, type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 0a212d21-eac9-4482-a03a-f4e23a3422fb Problem signature: P1: d1 P2: 40 P3: 2 P4: 0 P5: fffff800c483da11 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\073117-3656-01.dmp \\?\C:\Windows\Temp\WER-4046-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1695.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16A4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16B5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_67ec5f945438c5d6e16efa01f30bcc06b563fce_00000000_cab_15b853cd Analysis symbol: Rechecking for solution: 0 Report ID: 6b54a66e-4739-4462-93d4-7ca99e994e4d Report Status: 268435456 Hashed bucket:31/07/2017 20:58 Windows Error Reporting Fault bucket AV_chdrvr01!unknown_function, type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 3180605b-7b0c-45d2-b537-1a46f7422516 Problem signature: P1: d1 P2: 40 P3: 2 P4: 0 P5: fffff809bb1fda11 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\073117-3671-01.dmp \\?\C:\Windows\Temp\WER-4046-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16A4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16B4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16C5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_7711619182f150e8e4c97ec1d8aff85dffc0ef75_00000000_cab_1640417d Analysis symbol: Rechecking for solution: 0 Report ID: ec439960-90ee-43ec-9e2c-b079270ee0ab Report Status: 268435456 Hashed bucket:[/quote]

 

Thank you for the reply.

Okay, here goes:

I did put my full specs in my profile.
After that, I followed the steps 1 through 6 and yielded this result:

Code: Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\Windows\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Windows\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\Windows\system32>[/quote] So then for step 07

Winninit:

Code: Checking file system on C:The type of the file system is NTFS.A disk check has been scheduled.Windows will now check the disk. Stage 1: Examining basic file system structure ...Attribute record of type 0x80 and instance tag 0x0 is cross linkedstarting at 0x4dab1c for possibly 0x3 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x0in file 0x1800a is already in use.The attribute of type 0x80 and instance tag 0x0 in file 0x1800ahas allocated length of 0x3d80000 instead of 0xbf2000.The total allocated size 0xd5d000 of attribute of type 0x80 and instancetag 0x0 in file 0x1800a is incorrect. The expected value is 2ea000.Correcting total allocated size in attribute record (80, "")of file B00000001800A.Deleted corrupt attribute list entrywith type code 80 in file 1800A.Unable to locate attribute with instance tag 0x0 and segmentreference 0x1100000001800e. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x1800E.Unable to locate attribute with instance tag 0x0 and segmentreference 0xe00000001801a. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x1801A.Unable to locate attribute with instance tag 0x0 and segmentreference 0xb000000018020. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x18020.Unable to locate attribute with instance tag 0x0 and segmentreference 0xb000000018023. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x18023.Unable to locate attribute with instance tag 0x0 and segmentreference 0xb000000018027. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x18027.Unable to locate attribute with instance tag 0x0 and segmentreference 0xb000000018029. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x18029.Unable to locate attribute with instance tag 0x0 and segmentreference 0x66e00000001802a. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x1802A.Unable to locate attribute with instance tag 0x0 and segmentreference 0xb00000001802b. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x1802B.Unable to locate attribute with instance tag 0x0 and segmentreference 0xc00000001802d. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x1802D.Unable to locate attribute with instance tag 0x0 and segmentreference 0xb00000001802f. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x1802F.Unable to locate attribute with instance tag 0x0 and segmentreference 0x14000000018030. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x18030.Unable to locate attribute with instance tag 0x0 and segmentreference 0xc000000018031. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x18031.Unable to locate attribute with instance tag 0x0 and segmentreference 0xc000000018035. The expected attribute type is 0x80.Deleting corrupt attribute record (0x80, "")from file record segment 0x18035.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x4d4043 for possibly 0x5c clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x35d73 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x35D73.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x4d7944 for possibly 0x81 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x360e7 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x360E7.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x1396e98 for possibly 0x3 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x4011e is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x4011E.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x1396f18 for possibly 0x3 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x40166 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x40166.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x1397598 for possibly 0x3 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x402bc is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x402BC.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x1368bd8 for possibly 0x1 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x45533 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x45533.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x1368bd9 for possibly 0x1 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x45535 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x45535.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x1368bda for possibly 0x1 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x45539 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x45539.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x1368bdb for possibly 0x1 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x4553c is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x4553C.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x237681c for possibly 0x1 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x581ed is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x581ED.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x237681d for possibly 0x1 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x581ef is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x581EF.Attribute record of type 0x80 and instance tag 0x4 is cross linkedstarting at 0x237681e for possibly 0x2 clusters.Some clusters occupied by attribute of type 0x80 and instance tag 0x4in file 0x581f1 is already in use.Deleting corrupt attribute record (0x80, "")from file record segment 0x581F1. 393728 file records processed. File verification completed. 8658 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 510132 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ...Cleaning up 1464 unused index entries from index $SII of file 0x9.Cleaning up 1464 unused index entries from index $SDH of file 0x9.Cleaning up 1464 unused security descriptors.Security descriptor verification completed.Inserting data attribute into file 1800A.Inserting data attribute into file 35D73.Inserting data attribute into file 360E7.Inserting data attribute into file 4011E.Inserting data attribute into file 40166.Inserting data attribute into file 402BC.Inserting data attribute into file 45533.Inserting data attribute into file 45535.Inserting data attribute into file 45539.Inserting data attribute into file 4553C.Inserting data attribute into file 581ED.Inserting data attribute into file 581EF.Inserting data attribute into file 581F1. 58216 data files processed. CHKDSK is verifying Usn Journal...Usn Journal verification completed.Stage 4: Looking for bad clusters in user file data ... 393712 files processed. File data verification completed.Stage 5: Looking for bad, free clusters ... 83421655 free clusters processed. Free space verification is complete.CHKDSK discovered free space marked as allocated in themaster file table (MFT) bitmap.Correcting errors in the Volume Bitmap.Windows has made corrections to the file system.No further action is required. 499526655 KB total disk space. 165174900 KB in 302499 files. 187152 KB in 58204 indexes. 0 KB in bad sectors. 477979 KB in use by the system. 65536 KB occupied by the log file. 333686624 KB available on disk. 4096 bytes in each allocation unit. 124881663 total allocation units on disk. 83421656 allocation units available on disk.Internal Info:00 02 06 00 e6 80 05 00 bf 7f 0a 00 00 00 00 00 ................c5 00 00 00 3d 00 00 00 00 00 00 00 00 00 00 00 ....=...........Windows has finished checking your disk.Please wait while your computer restarts.[/quote] Chkdsk:

Code: Chkdsk was executed in scan mode on a volume snapshot. Checking file system on C:The type of the file system is NTFS.Stage 1: Examining basic file system structure ... 375552 file records processed. File verification completed. 8499 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 491362 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ...Security descriptor verification completed. 57906 data files processed. CHKDSK is verifying Usn Journal... 38370192 USN bytes processed. Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 499526655 KB total disk space. 154637808 KB in 274886 files. 172076 KB in 57907 indexes. 0 KB in bad sectors. 497331 KB in use by the system. 65536 KB occupied by the log file. 344219440 KB available on disk. 4096 bytes in each allocation unit. 124881663 total allocation units on disk. 86054860 allocation units available on disk.----------------------------------------------------------------------Stage 1: Examining basic file system structure ...Stage 2: Examining file name linkage ...Stage 3: Examining security descriptors ...[/quote] I then went to the disk test. Screenshots attached.
Note: One very strange thing - SMART status wasn't available in both HD Tune and Sentinel - weird

After that, I got a sudden BSOD out of the blue, so I'll send the logs over as well.

I then fully deleted the CH control manager, but did not clean the registry, because I don't know if that's really needed, and went on to the verifier. Again, BSOD at startup. "Who crashed" says it was Saitek this time... so again, 2 different peripherals causing BSOD's

I hope you guys can figure this out. Thank you again for your precious time in helping me out.

Kind regards,

Bob

 

Which drive had the chkdsk corruptions?
Which drive did not have chkdsk corruptions?
Which drives were you unable to perform SMART testing?
Writing is disabled is correct.
Once these misbehaving drivers are fixed attempt the SMART drive testing on the drives that have not yet been tested.



There were 2 misbehaving drivers identified.
It's unclear whether one of these is a recurrent driver or not with the time zone change.
So if you have already replaced the driver just replace the new misbehaving driver.
The driver if unstable would likely reappear using windows driver verifier.
Identify replacement drivers.
Uninstall and then reinstall these drivers:
chdrvr03.sys
SaiMini.sys
Please add these joystick products and other peripherals as needed to complete the information section about your computer hardware

Sea tools has the option for SMART, short and long generic.
In addition to the 3 software smart tests please run the Sea Tools on the HD
Run Sea tools for windows on your drive using SMART, short and long generic tests:


How to use SeaTools for Windows
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows
http://www.seagate.com/support/downloads/seatools/


The Memtest86+ testing needs to be performed so that there are images in the thread.
There is 32 GB RAM so please run 16 GB at one time for testing.
There needs to be at least 8 passes for each test.
It does not go by time but by passes to perform proper testing.
There are too many false negatives for testing less than 8 passes.
A false negative is a pass when the RAM malfunctions.
So the testing method is critical.
It is estimated that it will take 1 -2 hours /GB RAM
Just 1 error is a fail and then you can abort testing.
Then test each RAM 1 at a time all in the same DIMM. Each test must be for at least 8 passes to reduce the incidence of false negatives.
If RAM fail when tested as a pair and then pass when tested individually the DIMM or MB needs to be tested by placing RAM that has passed in each DIMM on the MB.
The testing is by the process of elimination.
For each RAM test please use a camera or smart phone camera to take a picture and post images into the thread.




Code: 14/08/2017 20:55 Windows Error Reporting Fault bucket 0xc9_23b_VRF_IMAGE_SaiMini.sys, type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 218bbc22-48fc-4cea-ab60-7ee00d36eebb Problem signature: P1: c9 P2: 23b P3: fffff8014ad71f30 P4: ffffd087824f1010 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081417-4640-01.dmp \\?\C:\Windows\Temp\WER-5187-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BC5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BD5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BE5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c9_eb71a85ef75eb7c3f2a871fcdd987fb725961_00000000_cab_15b03316 Analysis symbol: Rechecking for solution: 0 Report ID: a9f85cc1-5145-4c7e-bbb8-de0ae7898a2f Report Status: 268435456 Hashed bucket:14/08/2017 20:15 Windows Error Reporting Fault bucket 0xc9_23b_VRF_IMAGE_SaiMini.sys, type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 2aae5c61-338e-4328-9369-c06259cd1410 Problem signature: P1: c9 P2: 23b P3: fffff80b4d131f30 P4: fffff28ac5d86ca0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081417-4671-01.dmp \\?\C:\Windows\Temp\WER-5125-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CAF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CAF.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CC0.tmp.txt \\?\C:\Windows\Temp\WER3EFE.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c9_c4c97b1faeeb3c8a3b5b7ce73a829bc8ac345_00000000_cab_15750ea1 Analysis symbol: Rechecking for solution: 0 Report ID: 0952ee35-c026-4eaa-8cf0-e24008165d30 Report Status: 268435456 Hashed bucket:14/08/2017 20:25 Windows Error Reporting Fault bucket 0xc9_23b_VRF_IMAGE_SaiMini.sys, type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: ebade4c1-d50b-4436-89b1-ed2f4fd7004d Problem signature: P1: c9 P2: 23b P3: fffff80883581f30 P4: ffffed0a5d192ca0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081417-4625-01.dmp \\?\C:\Windows\Temp\WER-5093-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1ADB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B96.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B97.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c9_a2865cd63dcc3e4ae369e1ad526cda37b649e611_00000000_cab_15cc57d4 Analysis symbol: Rechecking for solution: 0 Report ID: f5a8cc19-cf65-4219-8383-5242144d4841 Report Status: 268435456 Hashed bucket:14/08/2017 20:39 Windows Error Reporting Fault bucket 0xc9_23b_VRF_IMAGE_SaiMini.sys, type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: f112fa8e-6e06-4232-9051-c1545bb2b1ee Problem signature: P1: c9 P2: 23b P3: fffff80d6d8d1f30 P4: ffffc881ce2681e0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\081417-4515-01.dmp \\?\C:\Windows\Temp\WER-4984-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C80.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CCF.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CD0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c9_b0aaaac8d11fd5e4e1a2b194d7354aa5c3d6297_00000000_cab_1670342f Analysis symbol: Rechecking for solution: 0 Report ID: 831576f4-b31a-4900-8ea4-02e1e3f6395a Report Status: 268435456 Hashed bucket:[/quote] Code: SaiMini SaiMini SaiMini Kernel Manual Running OK TRUE FALSE 4,480 5,888 0 06/11/2015 14:23:06 C:\Windows\system32\drivers\SaiMini.sys[/quote] SaiMini.sys Saitek Magic Mini driver Drivers and Sofware for Saitek Pro Flight Sim Products | Saitek.com
Code: 31/07/2017 21:16 Windows Error Reporting Fault bucket AV_chdrvr01!unknown_function, type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 0a212d21-eac9-4482-a03a-f4e23a3422fb Problem signature: P1: d1 P2: 40 P3: 2 P4: 0 P5: fffff800c483da11 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\073117-3656-01.dmp \\?\C:\Windows\Temp\WER-4046-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1695.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16A4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16B5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_67ec5f945438c5d6e16efa01f30bcc06b563fce_00000000_cab_15b853cd Analysis symbol: Rechecking for solution: 0 Report ID: 6b54a66e-4739-4462-93d4-7ca99e994e4d Report Status: 268435456 Hashed bucket:31/07/2017 20:58 Windows Error Reporting Fault bucket AV_chdrvr01!unknown_function, type 0 Event Name: BlueScreen Response: Niet beschikbaar Cab Id: 3180605b-7b0c-45d2-b537-1a46f7422516 Problem signature: P1: d1 P2: 40 P3: 2 P4: 0 P5: fffff809bb1fda11 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\073117-3671-01.dmp \\?\C:\Windows\Temp\WER-4046-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16A4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16B4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16C5.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_7711619182f150e8e4c97ec1d8aff85dffc0ef75_00000000_cab_1640417d Analysis symbol: Rechecking for solution: 0 Report ID: ec439960-90ee-43ec-9e2c-b079270ee0ab Report Status: 268435456 Hashed bucket:[/quote] chdrvr03.sys CH Products joysticks (and other flight-sim related controllers) http://www.chproducts.com/retail/downloads.html
Code: chdrvr03 chdrvr03 chdrvr03 Kernel Manual Running OK TRUE FALSE 0 15,360 0 24/08/2012 11:10:59 C:\Windows\system32\drivers\chdrvr03.sys 768[/quote]

 

Hi zbook,

All the info about the disk diagnostics are all on the main windows installation disk: i.e. Samsung SSD 950 PRO 512GB
Also, I already added the peripherals used in the "other-info"-box at the bottom of the page.

I came around this tread lately. Could this be of any importance in troubleshooting my problem?
CH Control Manager fix or alternative? BSOD incompatibility with SSD : hotas

As for the drivers, is there a way to remove the files from my PC? I uninstalled CH-CTrL manager (which is known to be very uncompatible with W10) but the chdrvr03 remains in the verify list.

I performed a full memtest86+ already (all modules in all slots for more than 10 passes), with no errors returned. Since this is a painfully lengthy process, is it really necessary to perform these tests again with the 16Gb pairs?

Thanx for your help!

Bob

 

In post #15 there was a Memtest86+ error that disappeared when retested.
Was that related to malfunctioning RAM or DIMM/MB or was that a fitting problem or dust?
The bsod so far have been Nvidia recurrent, USBhub, SaiMini.sys, and chdrvr03.sys.
The options are to retest the RAM/DIMM/MB or wait to see if there are more bsod.
For any driver that has bsod it will be better to uninstall the driver to improve the troubleshooting.
So if you no longer use the joy sticks, peripherals, software, etc. use device manager or control panel to uninstall them.
File explorer search can then be used to see if there is any reinstalled or residual software.
Windows has a default feature to automatically update non-Microsoft drivers.
This feature can be turned off:
Enable or Disable Driver Updates in Windows Update in Windows 10 Windows 10 Windows Update Activation Tutorials
If there are any incompatibility issues they are likely to appear using windows driver verifer.
Create a brand new restore point.
Restart windows driver verifier and post any new bsod mini dump files:
BSOD - Posting Instructions - Windows 10 Forums