BSOD while playing World of Warcraft, error 0x00000124 (I think)

SinisterThougts · 24 Jun 2012

I've recently started Blue Screening about an hour or so into gameplay. It happened a few months ago, but when I didn't crash again I just thought the problem had fixed itself. It only seems to happen when playing World of Warcraft (WoW), I can play Skyrim, TF2, Diablo 3 and other games without any BSODs.

I've attached the BSOD files.

I'm running on Windows 7 Home Premium 64bit, it came pre-installed on a Samsung RV515. The laptop is about a year old and the only hardware change I can think of is my Toshiba Canvio (external hard drive) that has WoW and Diablo 3 on it. My hard drive is not overclocked. If you need any other information please let me know, and I'll be happy to provide it.

I'm not very experienced in any kind of computer maintenance and would greatly appreciate it if this could all be explained like I'm 5. :(

SinisterThougts · 24 Jun 2012

Using nirsoft's BlueScreenView I was able to look at my minidumps. It even let's me view the actual Blue Screen. Here's a copy-paste of what the blue screen looks like:

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: hal.dll

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000124 (0x0000000000000000, 0xfffffa8004e42038, 0x00000000b6000000,
0x0000000000010015)

*** hal.dll - Address 0xfffff80003612a3b base at 0xfffff80003600000 DateStamp
0x4ce7c669

I don't know where to go from here though.

SinisterThougts · 25 Jun 2012

Ok, so I'm going to re-install Windows 7 Home Premium in the morning, and just start from a blank slate, then I'll probably run Memtest if the problem persists. I sure hope I won't have to come back here.

SinisterThougts · 25 Jun 2012

I don't even know what to do anymore. I didn't have the Windows 7 CD so I tried a Microsoft tutorial where it had me set up an .iso of Windows 7 on a USB, and it reinstalled windows, but now the Drivers for my network adapter won't work, and I can't connect to the internet and when I use the driver updater it can't find any drivers on my computer and I just don't know what to do.

writhziden · 25 Jun 2012

SinisterThougts said:

I don't even know what to do anymore. I didn't have the Windows 7 CD so I tried a Microsoft tutorial where it had me set up an .iso of Windows 7 on a USB, and it reinstalled windows, but now the Drivers for my network adapter won't work, and I can't connect to the internet and when I use the driver updater it can't find any drivers on my computer and I just don't know what to do.

Ah, sorry, missed that. Do you have access to another computer?

Spybot Search and Destroy is not the best malware/spyware utility. Take a look at Good and Free system security combination. for better options.

Your Samsung drivers are out of date. Make sure to update the drivers for the software/device.

BugCheck 0x124

You have a 0x124 hardware bugcheck occurring frequently. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer.

WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.

If you are overclocking any hardware, please stop.
If you have an SSD, make sure the following are up to date:
- SSD firmware
- BIOS Version
- Chipset Drivers
- Hard disk controller drivers/SATA drivers
- If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
Run all but the advanced tests with SeaTools for HDDs.
SeaTools for Windows

SeaTools for DOS
Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
- Follow the steps for doing CPU stress test using IntelBurnTest
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through Stop 0x124 - what it means and what to try for the crash.