Solved BSOD using PCI device, 0x124

[atalanov]

Hello,

I have a new system that I built and I am getting a BSOD. The system specs:
Intel Core i7-5960X Haswell-E 8-core 3.0 GHz
Asus Rog Rampage V Extreme Mobo
WD Black WD6001FZWX 6TB 7200 RPM 128MB Cache SATA drive
PNY Quadro K620 2GB Graphics card
LG Black 16X BD-R 2X BD-RE 16X DVD
Samsung SM951 512 GB SSD
128 (8x16) GB Ram, Corsair Vengeance LPX 2400

I am using a PCI device (Alazartech ATS850), bridged to the computer using a PCI-PCIE bridge from startech and PCIE extension cables, to take measurements using software provided with the ATS850 device. After taking measurements for about 5 minutes with the software, the computer crashes with a BSOD, saying that the system encountered an unrecoverable hardware error and giving a 0x124 address. The crash occurs about 80% of the time, and I have been able to take measurements for about 40 minutes before, where I stopped the measurements without the system crashing. It seems the system is not generating minidump files for these crashes (the minidump files present are from previous crashes).

Upon checking the Event Viewer after such a crash, there are no events leading up to the crash. I monitored the CPU/RAM usage and temperatures leading up to the crash and they all seemed fine.

Help is greatly appreciated, thanks.

 

[atalanov]

I tried it again, and this time the computer crashed about 20 seconds into the process and generated a minidump file. I have attached to this post a new .zip file with the updated information, which includes the new minidump file.

 

[axe0]

Remove Daemon tools & ASUS software and let us know if the crashes continue.

 

[atalanov]

Hi, thank you for your response. Since my last post I had removed the m.2 SSD which I believe is on the PCIe bus, which did not help. I uninstalled Daemon Tools and all ASUS software that I could find in Control Panel/Remove Programs. The BSOD still occurred, and a minidump was not generated. The BSOD states "Collecting data for crash dump" and then "Initializing disk for crash dump" and then the BSOD just stays there and doesn't do anything. What should be the next course of action? If helpful, I have attached another system log from directly after rebooting after the crash.

 

[axe0]

STOP 0x124 Troubleshooting

Read carefully before proceeding.

   Warning

If you're overclocking your system, revert back to stock clocks now.

   Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

 CPU TEST

Run Prime95 and/or IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums & http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

Make a photo of the result and post it.

TWO

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Help 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.

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.

THREE

 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

1. Short Drive Self Test
2. Short generic
3. 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.

Post screenshots/photos of the test results

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.
When above is done please make screenshots of the following

• the error scan,
• the health,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

FOUR

 GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 7 Help Forums

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

Make a photo of the result and post it.

 

[atalanov]

I ran all the tests. Because of the large amount of memory, the memory test took a little over a week. See the attached pdf.

It seems there were no errors or problems, except for the hard drive did not pass the short drive self test the first time for some reason. It passed it the second time, and it passed the short and long generic tests.

What should be the next thing to try to resolve this issue? Do you think the problem is the hard drive?

 

[axe0]

It would be better to run chkdsk C: /r command in admin command prompt again for a few times (2-3)

I hope you noted the temperatures?

 

[atalanov]

I set up check disk to run twice from command prompt, although since the disk was in the use because the OS was running, I had to restart and have checkdisk run on system startup.

Results are attached.

In regards to the temperatures during the original series of tests, I noted the CPU temps were stable around 60 degrees C for the entire duration of the CPU stress test.

 

[axe0]

/r recovers readable data and fixes errors as it includes parameter /f, however it needs to be done outside Windows hence why you need to reboot.

 

[atalanov]

The two pictures that I just posted with check disk results were run with the option /r.

What should I do further to try to fix this problem?

 

[axe0]

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?

 

[atalanov]

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.

 

[axe0]

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

   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.

 

[atalanov]

I ran sfc twice, with reboot in between. No errors.

Ran driver verifier for about 46 hours, no crashes.

 

[axe0]

Test your system once again and keep me posted on how it goes

 

[atalanov]

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.

 

[axe0]

Could you try to install the PCIE device on a different system and see if it crashes there.

 

[atalanov]

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.

 

[axe0]

That sounds like the slot on your pc is faulty.

 

[atalanov]

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.