A thing to mention, if you get BSODs I need a new zip for analysis to see if there are any patterns or signs that can lead to a solution. We need a complete log, not just dump files, because the other logs may contain data that cannot be missed.
What was the temperature for the GPU when stress tested?
The BSODs are still present. Got one earlier today (June 18th) but again a minidump was not generated for some reason; the BSOD paused on initializing disk for crash dump and did not continue (see pic of BSOD). I have attached a new zip of the scan/log (I believe that is what you are referring to).
GPU temps were stable at about 80-81 degrees C, and reached a max of 82 degrees C.
I have a few thoughts with the given description, but it is difficult to confirm anything with a 0x124 even when we have a dump. 0x124 crashes do usually not provide much information other than a report of the error (the problem itself is a different thing from the cause).
- The device is faulty, though that normally gives BSODs in a higher chance rate
- The software is improperly communicating with the device
Please run following tests, SFC is for checking your file system to see if any corruption may be present preventing dumps from being written and Driver Verifier should cause a BSOD generating a dump, it is the only time we want a BSOD to happen. I suggest that you run first SFC and then driver verifier.
Diagnostics Test
System File Check
Please try following:
- Open an admin command prompt
- Copy/paste "sfc/scannow" (without quotes) and press enter
- When it finished reboot your system
- Open again an admin command prompt
- Enter sfc/scannow again
If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
Make a photo of the result and post it.
Diagnostic Test
DRIVER VERIFIER
WarningPlease 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.
NoteYour 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.
I ran sfc twice, with reboot in between. No errors.
Ran driver verifier for about 46 hours, no crashes.
Did you mean test it to see if the BSOD still occurs, or to run the CPU, RAM, etc tests?
I just tested for the BSOD and it still occurs as before.
I installed the PCI device via the PCI-PCIe interface to a PCIe slot on another system (not hand-built) running windows 10. The measurement software supplied with the device runs mostly fine. It ran several times for up to one hour at which point I terminated the software and restarted it. It then ran for about 36-48 hours before it froze, but it did not crash the computer (only the measurement software froze). I started it again and it has been running now for about 36-48 hours and the software is not frozen. Running this on the original computer, I would have gotten bluescreens of death several times by now, so it's definitely better on the other computer, but I need to run this on the original computer.
Some updates on running it on another PC: the program froze twice, both times about approximately 40-48 hours (this seems somewhat consistent).
I attached the device back to the original PC, and this time to a different PCIe slot. Upon testing the device, the PC bluescreened on the first test and generated a minidump this time (previously it was not doing this). Since then, I have had no issues running the device continuously for several days.
Would you be able to look into this new bluescreen? I am unsure if it's still related to PCI device. I have attached another log.
Quote