BSOD playing World of Warcraft, error 0x00000124

[captainphatty]

I just built a new PC, and I am getting the dreaded error code 0x00000124. I have attached the DM Log Collector information.

While reading through other threads, one of the first steps suggested was to run Prime95 to stress test the CPU. I did that before but I did not watch the temps, but I did not get any errors after 2 hours. I was trying again but this time running Core Temp 1.0 RC6. My CPU temp shot up to 100 degrees C. According to this page (CPU Temperature - What are the Maximum and Normal CPU Temps?) the max my CPU should be at is 67 degrees C. I am afraid to run that utility in fear I am going to damage something. Is it safe to continue to run that test?

I am using the stock cooler on my CPU (Intel Core i7 4770k), and I am not overclocking anything.

 

[Thedoctor44]

This bugcheck means a fatal hardware error has occurred. Unfortunately the WHEA error record doesn't have enough information to point to a cause.
However from what you've said your CPU temperature is too high.
I recommend getting a new cooler or a bigger case as your CPU should not go that high.
A new case and a cooler might be a good idea if you have a small case.

Any more problems let me know

 

[captainphatty]

I went ahead and replaced the stock thermal paste on my cooler, and my temps are idleing around 33-34, and maxing at 64-65 when I am running a ton of stuff including games. I am still getting the same BSODs, the most recently one when I had no apps open at all, so I don't think it is a heat issue. Also FYI, my case has plenty of cooling, it is a Cooler Master 922 HAF.

I attached a new DM Log Collector file in hopes it would shed more light on my issue. Any help is greatly appreciated

 

[Thedoctor44]

I think we ought to do some more hardware tests.

Stress test your graphics card with Furmark

I recommend running it for around 30 minutes

   Warning

Furmark will increase the temperature of your GPU rapidly so keep and eye on your temperatures

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Post back the results.

 

[captainphatty]

1. Furmark ran for 30 minutes, passed. Attached a screenshot of Furmark and the log, the log didn't seem to have any of the actually burn in test info, but the screenshot should help.


2. Memtest86 run for 8 passes, took almost 35 hours! I guess testing 32GB of RAM takes a long time #FirstWorldProblems. I did not see any log files created, but I attached a picture of the test I took before stopping it.

3. Disk Check found no errors. I ran SFC and it found nothing as well.

4. I ran all the tests in SeaTools (S.M.A.R.T. Check, Short Drive Self Check, and Long Generic) they all passed.

I was kind of hoping one of these tests would fail so I would be able to find the issue with my system, but everything passed, and no blue screens during any of the tests inside Windows.

 

[Thedoctor44]

Right, I have actually encountered cases where someone's system bugchecks with 0x124 and they don't have anything wrong with their hardware.
In fact I've had that personally.
With that said lets try driver verifier.


Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point Manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[captainphatty]

Finally got back to work on this machine. The verifier in Windows 8 seems to be a little different than your guide, and doesn't have some of the options it mentions. I wanted to make sure I am setting this up right before I get it up and running. I attached screens of the options windows.

By the way, thanks so much for your help!

 

[captainphatty]

I went ahead and guess on which settings to choose. I checked everything that had "standard" as a flag type, since the Windows 7 guess said "standard settings", and also IRP logging since that was in the guide as well. I am attaching a new dm log collector file, let me know if you need anything else.

 

[Thedoctor44]

Sorry I missed the thread.

There's only a 0x124 bugcheck that's new.
It still can't identify what is causing it.

I have one more idea.
Upload the list of all the third party drivers Using NirSoft DriverView:

• Download and execute Driverview
• View > Hide Microsoft Drivers
• Edit > Select all
• File > Save Selected Items
• In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
• Zip the .txt file and upload it.

 

[captainphatty]

Attached.

 

[captainphatty]

The only thing I didn't recognize on this list is the secdrv.SYS, I am honestly not sure what is using that. It is some kind of anti-disc copying protection from what I am reading.

 

[Thedoctor44]

Can you remove speedfan, I've been told it can cause issues.
Whether or not that is true I don't know but it's worth a test.

Hmm, do you have Command and Conquer installed?

 

[captainphatty]

I went ahead and removed speedfan. I don't have much installed, attached is my Programs list. Just to note, this error has occurred without anything installed on the machine, I basically had a clean install and was doing Windows Updates round 1 when it first happened.

 

[Thedoctor44]

EDIT: Sorry I forgot, I'll take a look.
How long did you run Prime95 for last time?
I recommend around 2 hours.

 

[captainphatty]

That list is already uploaded a few posts back.

I don't recall how long I ran Prime95, should I run it again?

 

[Thedoctor44]

Your Intel Management Engine driver could do with an update.
Go here to update it.

https://downloadcenter.intel.com/Se...dType=Drivers&keyword=intel+management+engine

 

[captainphatty]

I'm installing the update now.

Should I continue to run Verifier?

 

[Thedoctor44]

No you can disable it.

 

[captainphatty]

This has to be the most frustrating troubleshooting issue I have even run into.

I guess it is time to start the RMA process, perhaps the Motherboard first?

 

[Thedoctor44]

Upload the new dump files. RMA isn't going to fix anything if hardware isn't the issue.