Sign in with
Sign up | Sign in
Your question

Freezing, Sound Looping, BSOD 0x000124

Tags:
  • Homebuilt
  • Blue Screen
  • World Of Warcraft
  • Systems
Last response: in Systems
Share
March 5, 2009 10:12:06 AM

Alright you guys, this has been an issue for a while, and thank you VERY much for any help. I built my PC about 6-7 months ago, and it seemed to be completely fine. I can't remember exactly when this started, but it's been going on for a while.

The problem: While playing World of Warcraft in Windows Vista, I get random BSOD's that display a stop error and the code 0x000124. When I play World of Warcraft on the same computer, but with Windows XP(I've reformatted this thing so many times), it still gets random freezes, but the sound loops indefinitely. The loop is just like, a half second of whatever sound was playing at the time of the freeze. It plays over and over(sounds kind of like a dance track, for lack of better example), until I hit the reset button on my computer.

Now, this only happens when I play World of Warcraft. I also play Team Fortress 2 regularly, and I've played Fallout 3 for many hours straight, with no problems. This has occurred ONCE while not playing World of Warcraft. I was watching a YouTube video, and the same sort of freeze occurred, and I had to hard reset my computer. I watch YouTube videos often though, and it only happened once. I'm not entirely sure if I had any applications open in the background. This freeze while playing World of Warcraft seems to happen completely randomly. It can occur after 20 minutes, or it can occur after two hours, or at any point in between.

I've tried opening the minidump file, but WndDebug gives me some error about the wrong symbol files being loaded or something. If you guys need to see it, I can try to attach it somehow.

This is NOT a problem with overheating. Lately I've been leaving NVIDIA System Monitor open, along with ASUS PC Probe II, while playing World of Warcraft. The last freeze occurred yesterday, and both cores in my GPU were under 70 degrees. My CPU was at 33 degrees(never gets above this even under intense load, like that provided by Prime95.) I also stress tested my video card for two hours straight yesterday, and it peeked at 80 degrees. I'll provide my system specs below. I would also like to note, that all of the voltages displayed by ASUS PC Probe II were stable.

This problem ONLY occurs in World of Warcraft, with the exception of one time. This problem occurs REGULARLY. At LEAST once a day. I can browse the internet for hours on end, watch videos, record music, along with anything else. The system seems completely stable otherwise.

My PC:
Motherboard: ASUS Striker II Formula
PSU: Thermaltake Toughpower 1000w
Video Card: NVIDIA 9800gx2
Sound Card: Onboard sound, it's a SoundMAX card that came with the motherboard.
CPU: Intel E8400
RAM: 4GB, 1GB each stick, in all 4 DIMMS. I can't remember the exact model number, but it's Kingston brand and it's on the list of supported RAM for my motherboard. The ASUS site is down right now, so I can get it to you guys later if you need it. I would also like to note that it passes memtest(I ran it overnight).
Hard Drives: A seagate and a maxtor. SATA.
Wireless Card: D-Link WDA-2320. It's a PCI card.

NOTHING IS OVERCLOCKED. I DON'T EVEN USE THE STUPID AI UTILITY THAT CAME WITH THE MOTHERBOARD.(Just thought I'd make that clear.)

And that's about it. I've tried to be as detailed as possible. If you have any further questions feel free to ask. Thank you guys again for taking the time to help me.

More about : freezing sound looping bsod 0x000124

a b B Homebuilt system
March 5, 2009 4:54:03 PM

Welcome to the forums!

Have you set the memory voltage?
Test the memory with memtest86+.
If you get errors, up the Nortbridge and memory voltage, since you are using 4 sticks.
m
0
l
March 5, 2009 5:30:51 PM

I've manually set the memory voltage to 1.8V, since my motherboard liked to set it to 2V for some reason. It's rated for 1.8V though, so there it stays. I have tested the memory, and it passes every time.
m
0
l
Related resources
a b B Homebuilt system
March 5, 2009 5:51:39 PM

Try with a sound card and turning off the wireless card.
m
0
l
March 5, 2009 6:04:57 PM

I just disabled Enhanced C1E in my bios. I also realized I turned plug and play OS off before, so I turned that back on. Do you think either of those would contribute to the problem? If my computer freezes again, I'll remove the sound card, but I can't play WoW without the wireless card.
m
0
l
March 5, 2009 9:17:14 PM

Here's some minidump information:
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 8648e3f0, Address of the WHEA_ERROR_RECORD structure.
Arg3: f2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: WoW.exe

CURRENT_IRQL: 0

STACK_TEXT:
805d8488 81fca8b5 00000124 00000000 8648e3f0 nt!KeBugCheckEx+0x1e
805d84dc 81ccb9a8 8648e3f0 86702008 86702008 hal!HalBugCheckSystem+0xe1
805d8508 81fca7c9 86702008 00000000 805d8544 nt!WheaReportHwError+0x1d0
805d8518 81fcaea7 00000003 86702008 00000000 hal!HalpReportMachineCheck+0x31
805d8544 81fc699f 805d3130 0a066230 0401062b hal!HalpMcaExceptionHandler+0xf7
805d8544 00000000 805d3130 0a066230 0401062b hal!HalpMcaExceptionHandlerWrapper+0x77


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x124_GenuineIntel__UNKNOWN

BUCKET_ID: 0x124_GenuineIntel__UNKNOWN

Followup: MachineOwner
---------
m
0
l
March 5, 2009 11:48:50 PM

Hmmmm,,just passing thru here ,,but is looks like a Hardware Abstraction Layer ,, HAL error,maybe need to test video card on another set up ,,???,, :) 
m
0
l
March 5, 2009 11:50:04 PM

AND,,,,,You do have the LATEST bios....:) 
m
0
l
March 6, 2009 9:46:04 AM

I don't think it's the video card, as I can play other games perfectly fine. Even games for graphically demanding than WoW, like Neverwinter Nights 2 or Fallout 3. I ran Prime95 for 8 hours while I slept, and the computer was fine when I woke up. I just don't understand why World of Warcraft, and ONLY World of Warcraft can do this. No luck on the WoW technical forum either.
m
0
l
March 6, 2009 11:18:00 AM

Im suspecting the wireless card. I've seen problems with the card driver conflicting with the microsoft wireless software that leads to a memory allocation error.
but its mainly cos WoW is an online game.
might be worth checking out by removing the card and driver, connecting via cable and playing for a coupla hours.
m
0
l
March 6, 2009 2:22:13 PM

Sadly, I can't play without the wireless card, as my router is in another room, and I can't move this computer in there. I do play other online games though, like Team Fortress 2, without any problems. I've been thinking though, and it seems WoW started freezing when I began playing it in windowed mode a couple of months ago. I don't remember any freezes when I played it in fullscreen. I think I'll switch back and see how it goes. Do you guys know what would cause it to crash my computer in windowed and not fullscreen? Also, this would probably be a lot easier to diagnose if I could reproduce it willfully. It is COMPLETELY random though, or so it seems.
m
0
l
November 23, 2011 6:17:18 AM

I don't know if you have fixed the problem by not, but have you tried disabling your sound card and tried to play without sound for a while to see if it conflicts with your sound card?
I had that problem with Bad Company 2 and fixed it that way.
Hope it helps (I have got the same problem as you with WoW, and to be honest I haven't yet tried that with the sound card, which is quite ridiculous).

m
0
l
November 23, 2011 6:19:04 AM

now* -.-
m
0
l
!