D975XBX2 + Nvidia 8800 Series + Any sound + Vista32 = BSOD (STOP 0x00000124)

Tuesday, April 10, 2007 12:39 AM

0

Welcome to the pain train -- all aboard. I have seen literally hundreds of posts around the net' with folks using 8800 class Nvidia cards and the Intel D975XBX2 mobo's struggling with BSOD's reporting STOP 0x00000124 (Bugcheck 124) errors. I strongly believe we all have similar problems in that with any audio device + configurations similar to what is listed below we end up with BSOD's either immediately after boot or within certain games and programs in a seemingly random pattern. Most of my bugchecks are occuring with AudioSG.exe which is the surrogate process for 3rd party audio drivers within Windows Vista. With audio disabled my experience within Vista is solid. Read that no BSOD's. I have found that with the Audigy it's minutes to repro a BSOD and with the onboard Sigmatel it takes longer. I want to start this thread as a list of what folks have tried -- please omit "me too" posts. We all feel your pain but let's get a good list of what folks have tried to get going. Please only folks with 8800 class cards since we have a seperate Forceware driver set.

What I have tried to no avail resulting in 0x00000124 BSOD's

- Latest drivers across the board. Feb 20 (WHQL) and March 1 (Beta) NVidia drivers

- Stock only drivers - that is what came on the Vista DVD.

- Increasing the voltage for my CPU, MCH, and Memory slightly

- Running Memory at 667Mhz. Testing memory with Vista. Running with 2GB only.

- Running w/o Intel Matrix RAID

- Similar to others I have no BSOD's within Windows XP SP2.

My Configuration:

Intel D975XBX2 "Bad Axe 2"

Bios BX97520J.86A.2663.2007.0305.1750

Core Duo E6600 (2x2.4Ghz 4MB L2) Stepping 6

2×1GB A-DATA DDR2800 1.8V

2x512MB A-DATA DDR2800 1.8V

EVGA 8800GTS 640MB ACS3 Edition

3 x 250GB WD Sata2 with Intel Matrix Raid 5 - Boot Volume

1 x 250GB WD Standalone - XP SP2 Volume

Onboard Sigmatel 92xx

Creative Soundblaster Audigy 2ZS

Windows Vista Ultimate 32 bit
- Reply
- Quote

All Replies

Monday, April 16, 2007 11:35 PM

0

I have a new Vista Ultimate machine. I get the 0x00000124 error seemingly completely at random. Like you I have loaded the most up to dat edrivers but they make no difference.

I have thoroughly stress tested the RAM, the CPU and the RAM & CPU together - they're fine even at the overclocked rates..

I suspect the Creative drivers but I have no hard evidence for that. Could be nVidia but I'll swear it's one or other of them. My 'impression' is that when Vista shows a highlighted option or simlar it BSODs. It's always 0x00000124.

Config:

Asus P5B Deluxe P965
Core 2 Duo 6700 @ 3GHz
2 x 1GB Corsair 8500 Dominator RAM clocked at 900MHz
1 x 150GB WD Raptor
1 x 500GB WD Caviar
Gainward 8800GTS
Creative XFi Xtreme Music
Windows Vista Ultimate 32 bit
- Reply
- Quote
Tuesday, April 17, 2007 3:17 AM

0

Sorry to hear of your experiences Steve. Intel recently released a Bios update for my motherboard and now I can only reproduce the Bugcheck with Windows Media Player and not consistently. Games like "Supreme Commander" no longer result in a BSOD. I have also installed the "leaked" 101.70 beta drives from Nvidia which may also be accounting for some of the increased stability I am seeing.

Regardless with my Creative Audigy-2 enabled it's still BSOD city for me so the Sigmatel onboard sound solution on my motherboard appears to have much better reliability with Vista. If you have onboard sound I suggest disabling your XFi and running with the onboard sound for awhile to see if things improve.

From the kernel crash dumps I have looked at the root cause here imho appears to be some nasty interaction with OpenAL (Vista sound stack) and the 8800xxx drivers from NVidia. Most often for me the offending process is audiodg.exe or some other sound related executable.
- Reply
- Quote
Wednesday, April 18, 2007 9:24 PM

0

I submitted a bug report to nVidia. Today both they and the builder of my PC advised me to install the US, albeit not WHQL signed, 158.18 drivers instead of my UK nVidia up to date 100.65 drivers.

So far, all day, I haven't had a single BSOD.

My fingers are crossed.

Thanks.

Steve
- Reply
- Quote
Thursday, April 19, 2007 7:03 AM

0

I've tried various versions of the nvidia drivers, and am now using the 158.18 drivers. Various editions of the drivers have had different stability, but none (inc. 158.18) haven't completely irradiated the problem. I also have the latest drivers for my onboard/offboard audio.

Relevent hardware includes:
GA-965P-S3 Motherboard (onboard Realtek audio)
SoundBlaster Audigy 2 ZS
nVidia GeForce 6200

It does seem to be some combination between video/audio drivers, but I really can't make sense of it. The issues only seem to occur when i'm viewing video/audio (doesn't matter if it's divx/mp3/wma/wmv/etc, or what player i use - winamp, windows media player, vlc, etc.). When I disabled my audio (both sound blaster and onboard realtek), I didn't experience any crashes, although I only ran that for a day or two. Using the sound blaster seemed more unstable than when I used the realtek - both would crash, but I'd get further into my video/audio before it would happen.
- Reply
- Quote
Friday, April 20, 2007 9:09 PM

0

Hi, I´m Ariel from Argentina, have the same problem, I´ve sent an email to Realtek, but they told me it was a problem from video card, but when I disable realtek hd onboard, my pc works perfect.
Tried all version of drivers, and crash always, my temporal solution was unistalling audio driver and use the driver from windows and sometimes it works...
I don´t know if it a problem from video or sound, I thought it was the second, but I see that other sound cards have the same problem, sorry, I don´t have a solution

mi config is
mother MSI P965 Neo
2gb DDR2 Kingston 667 mhz
Video Card Asus chip GeForce 7300gs
Realtek HD audio
- Reply
- Quote
Saturday, April 21, 2007 12:57 AM

0

I can confirm as well that I cannot reproduce the BSOD's with the latest 158 NVidia drivers. It does appear that the NVidia drivers were at the root cause of these problems. Either sound option for me, Creative or Sigmatel is working well.

-Ken
- Reply
- Quote
Saturday, April 21, 2007 2:34 AM

0

So, Kyle - just confirming - you WERE having the issue while using BOTH your on-board or creative sound cards BEFORE the 158 drivers?

Weird - anyone using realtek sound who's problems have been solved with the 158 nvidia drivers?
- Reply
- Quote
Saturday, April 21, 2007 6:46 AM

0

the nVidia 158 driver crash all the time, realtek hd 165 crash all time, what happends?? don´t want back to win XP
- Reply
- Quote
Saturday, April 21, 2007 10:37 AM

0

Just an update to say that although the 158.1 .............. and then it crashed with a 0x00000124 error !!! I was typing this and listening to a live radio transmission.

The Windows error report gave the problem as being with the "video device driver" and recommended updating to the latest graphics drivers and then changing performance settings to "best performance".

It gave a link to Error Message: STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER (Q293078)

No mention of 0x00000124, which does always come with 3 more detailed STOPs in brackets after it.

Come on nVidia you seem to be a major player here, you and MS should be jointly prioritsing this, so let's get this sorted.

Steve
- Reply
- Quote
Sunday, April 22, 2007 7:22 AM

0

I've just noticed some REALLY bizarre behaviour - I've had XP sitting in the background (dual-boot) since I installed vista, but hadn't really been using it much.

I wanted to use XP to do some video-related tasks that kept crashing in Vista (with the stop 0x124), but now I'm noticing the PC also crashes in XP when playing back audio/video (similar to vista).... only.... it's not a blue screen... it just restarts (and yes, I've unchecked the "automatically restart" box in XP)... is this related, or am I just going nuts?
- Reply
- Quote
Sunday, April 22, 2007 9:19 AM

5

Diabling "C1E" in BIOS took care of this problem for me.

You can locate C1E under your CPU-settings in BIOS.

Do a google search on the C1E to learn what it is.
- Reply
- Quote
Sunday, April 22, 2007 11:04 AM

0

Thanks, Hobz. I'll just look harder... in the right area.

Steve
- Reply
- Quote
Sunday, April 22, 2007 12:05 PM

0

Hobz - that did nothing for me.

Anyone else got any bright ideas?
- Reply
- Quote
Sunday, April 22, 2007 2:22 PM

0

Done this and have disabled system sounds in Control Panel. So many 0x00000124s happened at the same time as a system sound.

Thanks.

Steve
- Reply
- Quote
Monday, April 23, 2007 1:22 AM

0

Yes. That is correct. Before the 158 drivers I could generate BSOD's on this hardware with both the onboard Sigmatel (NOT Realtek on my mobo) and my aging but trusty Audigy-2 SoundBlaster PCI. It was much easier to crash with the Creative card than the onboard sound but I could do so with both -- particularly with either Windows MovieMaker or with the new game Supreme Commander. I am now happily doing both without issue using the 158 drivers and my onboard sound.
- Reply
- Quote
Monday, April 30, 2007 1:18 AM

0

Sorry for my english
I have a solution, course have same problem.
Its Realtek 883 only problem.
Error code 124 - then audio sample rate is not 24 bit\48000 as default in Realtek 883 properties.
You can change default format to 44100 16 bit manually and listen 44100 music, but if you watch 48000 movie - same error code. You may know whitch exacly sample rate uses aplication and change every time sample rate manually.
Win XP changes sample rate automaticcaly - vista can't.
- Reply
- Quote
Tuesday, May 01, 2007 6:49 PM

0

Sobriquet,

Can you provide the remainder of the bugcheck code (the values in paren after 124).

A suggestion would be to check the power configuration of all your peripherals. Are they being managed down*, and if so, will the problem reproduce?

* uncheck bot boxes in device manager / device / properties / power management

also in Device Manager, when /View, /Show hidden devices, under non-plug and play drivers - any yellow bangs or other problems?
- Reply
- Quote
Thursday, May 03, 2007 2:01 AM

0

I've reinstalled Vista as the 64bit version, and it seems to be working fine now. It crashed once (x124) before I installed the updated (158) nVidia drivers. I also seemed to be having issues with one of my drives, which I've now replaced - I'm not sure if this was related or not.

I'm trying to take it slowly to make 100% sure the problem is gone, and as such my soundblaster card isn't back inside the machine yet... when I'm confident the issue has disappeard with the 64bit install, I'll start plugging things back in one at a time...

So, *fingers crossed*, hopefully it's gone??

Thanks for your help, though - I had suspected power issues as well, but had no idea what I could do to check/fix it if it was.
- Reply
- Quote
Friday, May 04, 2007 4:42 PM

0

Hobz wrote:

Diabling "C1E" in BIOS took care of this problem for me.

You can locate C1E under your CPU-settings in BIOS.

Do a google search on the C1E to learn what it is.

This might be a bit premature but this worked for me as well....as far as I can tell. I was having a problem with BF2142 and I would get a BSOD everytime it would start loading a new game and sometimes before then. I too would have a problem with WMP and even Windows Live Messenger.

After disabling the C1E in my BIOS, SO FAR, it's working. I'm almost afraid to say it's fixed for sure because I'm afraid that it might not be. Anyway someone else mentioned that they started having the problem in XP too...well this could certainly cause a problem in both XP and Vista since (at least in my case and evidently Hobz's case too) it's BIOS related.

So far I've tried everything that caused it to reboot before and now it's not doing it so it looks like it's fixed but I'll need time to know for sure.
- Reply
- Quote

Saturday, May 05, 2007 9:51 PM

I just wanted to add that I have the same problem

MSI P6N SLI MoBo with Realtek on-board and an eVGA 8800 GTS

Ive tried EVERY nvidia driver and multiple Realtek drivers.
I noticed that i get the BSOD a lot less when using generic MS audio driver instead of the Realtek one.

I've been fighting with this problem since I built my machine about 6 weeks ago.

Sunday, May 06, 2007 4:33 AM

Ok, I *was* a little premature.

The problem has occured again...

0x00000124 (0x0000000000000000, 0xfffffa80019e5040, 0x00000000b2000018, 0x0000000002000e0f

twice now

0x00000124 (0x0000000000000000, 0xfffffa80019e5560, 0x00000000b2000000, 0x0000000000000175

may have been related to my fusionhdtv driver, but who knows

I'm using:

The latest nVidia drivers (158)
The stock-standard microsoft realtek drivers
No Audigy card (physically removed from my PC)
I've disabled C1E in BIOS

Also, tomack - since you asked - none of my devices appear to be having issues under the device manager (even showing hidden devices). But I can't find the power management settings your describing for any of my devices? Does this only show up on particular types of devices?

I'm begining to suspect it *IS* actually some faulty hardware component, although I'd love a software-related fix. Does anyone know of any good (preferably free/gpl) programs I can run outside windows (i.e. from a boot disk) to test specific hardware for issues? (i know of memtest86 for testing ram, and I've used that - no problems found)

Sunday, May 06, 2007 6:36 AM

Interestingly, I didn't BSOD until I loaded the nVidia 158.18 drivers. Now it seems to happen randomly -- sometimes 10 minutes after booting, sometimes several hours. I thought it may have something to do with running Second Life, but, after extensive sessions without ever going into SL, no soap -- it still happens. My configuration is somewhat different from others in this post. Here's my rig:

MSI Neo2 Platinum motherboard (theoretically Vista is not supported on this mobo, but it hopped on just fine and was running nearly flawlessly -- until I updated the video driver. It's not possible to hang USB external drives off the mobo USB ports with this motherboard but they're happy as clams running off add-on USB 2.0 boards, by the way.)

4 Gb PC-3500 RAM

nVidia GeForce 7800 GS

2 Maxtor 500 Gb SATA drives

Here is the hex dump sequence I see:

0x0000124

Then, in parentheses:

0x00000000

0x85207028

0xB2000000

0x00070F0F

Again, I've NEVER seen a BSOD on this machine until I updated the video drivers on this box. Just for fun, I've disabled the RealTec onboard audio and will keep my fingers crossed.

Monday, May 07, 2007 8:03 AM

I can help you out there.....at least for memory. D/l the latest version of Memtest86. It will take about an hour to an hour and a half to run the standard tests. Then it starts over again and it continues to loop, but if you get through one test without any errors, you're memory should be fine. Vista also has a memory checker, but I don't believe it's as good as Memtest86. Make sure you d/l the latest one which came out in January and I'd download the ISO image so it will boot of your CD/DVD-ROM. http://www.memtest86.com/download.html

Monday, May 07, 2007 12:02 PM

You must have missed the bit where I said "i know of memtest86 for testing ram, and I've used that - no problems found"

Thanks, though! I was hoping there might be something LIKE memtest86 that could test other hardware?

Anyway, it's anoying, but this problem doesn't seem to be consistent - it'll happen every time I try and open a video / play music one day, and the next day, I'll be listening to music and watching tv/videos all day! Grr...

Monday, May 07, 2007 1:10 PM

Well, I disabled the onboard audio and the machine has been blue screen free for about 24 hours. Fingers crossed hoping that did the trick. FYI, I failed to mentioned I'm running an AMD Athlon 64 4000+ processor.

I'm still very much of the opinion that nVidia screwed something up with the latest version of the video driver. This never happened until I downloaded the latest version (158.18).

Monday, May 07, 2007 9:51 PM

My problem seemed to solve itself after installing 158.18 and disabling C1E.. so far it's been very stable for a couple of weeks.

You can get a stress tester for the CPU from Orthos. Can't remember the download location unfortunately.

Steve

Monday, May 07, 2007 10:04 PM

It seems disabling C1E in my BIOS fixed the problem.
Although I have no idea why.

Monday, May 07, 2007 11:00 PM

That's exactly what fixed my problem. I don't know why either...it doesn't make any sense to me but the HALT command in the CPU must somehow interfere with the sound subsystem in Vista...maybe an IRQ...I don't know, but it definitely interferes!

Wednesday, May 09, 2007 4:01 AM

I landed on this thread and although I am not a techie, I have something that might be of interest. I get the same crash. My sytem is a DELL XPS 410 with the 2.44GHZ Intel dual core and NVIDIA 8600 GTS graphics card (with the latest update 158.18). I notice that the crashes only occur with Media Player 11, whether off a web site or straight from the application. When I use Quick time (just test with some free itunes podcast) I get no problem whatsoever. Even the itunes radio. Dell thinks it's the video card and they gave me a cash credit for the hassle, it's up to me if I want to change cards. But for now, I would rather stick with a directx10 especially since I think the entire issue is related to Windows Media player, since the crash also occurs when running the "dreamScene" ***. Any thoughts? And has anyone tried Real Player with the NVIDIA 8000 series?

Wednesday, May 09, 2007 4:44 AM

Two days and counting with no BSOD after disabling the onboard audio. I think I'm willing to say that was the problem -- must be some sort of conflict between the 158.18 nVidia driver and the RealTec audio on my motherboard. The problem never happened with earlier versions of the video drivers.

Note to eckel: Thanks for the info about your BSOD in Media Player. I never saw the crash running WMP on my Vista box. The problem occurred randomly, sometimes while the machine was sitting idle.

Wednesday, May 09, 2007 10:03 AM

I've had these issues with all sorts of media players. I used to mostly use WinAmp when I had Vista32, but apparently there are issues with Vista64 & Winamp, so I haven't installed it yet. I experienced crashes with VLC, Windows Media Player, FusionHDTV player, and occasionally just with system sounds. Since Vista64, the crashes have definitely become less, but they've definitely happened without using media player...

Still, 3 days now and no crashes.... but I'm still not convinced the problem is solved...

Wednesday, May 09, 2007 10:18 AM

I had this problem and as I said elsewhere it disppeard with 158.18 and with disabling C1E. More to the point of the above threads I run WMP11 and Real Player (altho' I'd rather not run RP....) with absolutely no problem whatsoever, so it's not a simple media player issue either.

That's my four penneth.
Steve

Wednesday, May 09, 2007 3:26 PM

And again, I speak to soon...

I'm really not understanding this, but it seems what Dmitri said a while back about audio bit rates has something to do with it. I found a video that crashed my computer with the same error twice - once in Media Player, then again in VLC. I then changed the bit rate (under the sound control panel, properties of the speakers, under the advanced tab) to the same bit rate as the video, and it doesn't seem to crash.

I tried this once before, and the same thing happened. But then after changing the bitrate back, the problem didn't re-occur, so I put it down to chance.

Does this make any sense at all???!?

Thursday, May 10, 2007 2:04 AM

I run 158.18, but I have not disabled C1E. But I have no problems with Quick time and Audigy (although I am now on windows sound only). My question is: has anyone crashed with Quick time and NVIDIA driver (before disabling C1E) and if that is not the case, maybe it should be looked into by NVIDIA. What is it in Media Player that makes my system crash (124) while watching video and not watching video in Quick time?

Thursday, May 10, 2007 10:55 PM

Customer is having problems... So far had him reseat ram, disable C1E, now having him take out Sound card. This happens immediately when Windows boots up...... His specs are as follows. Power Supply: 1000W PC Power & Cooling (Quad SLI/8800 GTX SLI Compatible) (Turbo-Cool Edition) Processor: Intel Core 2 Extreme QX6700 2.6GHz Quad Core (1066MHz FSB) (8MB Cache) Motherboard: eVGA Core 2 Quad (Chipset: nForce 680i) (SLI Compatible) (Quad Core Conroe) Memory: 4GB DDR2 Corsair at 1066MHz Dominator (Dual Channel) (Extreme-Performance) Floppy / Media: Sony 1.44MB Floppy (Black Edition) Hard Drive 1: 320GB Western Digital (16MB Cache) (7200 RPM) (SATA) Hard Drive 2: 320GB Western Digital (16MB Cache) (7200 RPM) (SATA) Raid Option: Setup my two hard drives in a Raid 1 Mirror (Hard Drive Data Clone Backup) Optical Drive 1: Sony DVD±R/RW/CD-R/RW (DVD Writer 18x / CD-Writer 48x) Optical Drive 2: Lite-On DVD±R/RW/CD-R/RW (DVD Writer 18x / CD-Writer 48x) (LightScribe Edition) Network Card: High Speed Network Port (Supports High-Speed Cable / DSL / Network Connections) Modem: - No Thanks Video Card: 2x SLI Dual (nVidia GeForce 8800GTX 768MB (By: eVGA) (PCI-Express) TV Tuner: - No Thanks Sound Card: Creative Labs Sound Blaster X-Fi XtremeGamer (Up to 7.1 Channel) (Recommended) Physics Card: - No Thanks Cooling: Extreme Liquid Chilled (CPU & Video Card(s) Tuning) (Blood Red Coolant) Case Lighting: Blizzard Internal Lighting (Blue Edition) (Cold Cathode Tubes) Round Cables: - No Thanks User Manual: FREE! Personalized Elite Digital Storm Binder (Paperwork/Benchmarks/CDs/Manuals) Windows OS: Microsoft Windows Vista Ultimate

Friday, May 11, 2007 12:33 AM

Dell bios update handled my problem, finally.

Friday, May 11, 2007 4:46 AM

I think I'm going to buy another sound card tomorrow and see if maybe may problems stay gone. I love creative, but I think they're the root cause... I'll post again with my findings...

-EW

Friday, May 11, 2007 6:02 AM

Three days and counting with no blue screens since I disabled the onboard RealTec sound stuff via my BIOS setup. I'm running Bose speakers, which attach via USB to the back of the computer so, fortunately, I still have sound. I'm cautiously optimistic that this solved the problem for me. Since disabling the onboard audio, I've been in and out of Windows Media Player a bunch of times, having viewed a variety of videos and listening to local and Urge audio. So far, so good.

Methinks someone in the QA department at nVidia never bothered to test the new driver with a motherboard using onboard audio. As mentioned in previous posts I've done, I saw no blue screens until I loaded the 158.18 version of the nVidia drivers.

It's difficult to type with my fingers crossed. If I can go a week without any blue screen, I'll uncross them.

Friday, May 11, 2007 3:40 PM

There's no need for that hopefully. If you're having the same problem I am and others here, then if you disable the C1E in your BIOS under CPU options...or somewhere in that area...it's different with each board of course. If it's the C1E problem, then buying another sound card won't help as my X-Fi card did it with Vista x64....that is gave me the BSOD with that STOP error along with playing videos through WMP.

Since I've disabled the C1E in the BIOS, I haven't had one BSOD...well actually I did have one but it was related to a program incompatibility and nothing at all do with this and I fixed it when I uninstalled the program, but I digress. If you haven't disabled the C1E, try it. Your system won't have any adverse affects to it.

Then there's other people that it's only with the Forceware drivers and some with both, the C1E and Forceware drivers. I'm fortunate as my Forceware drivers are pretty solid.

EvrWccn wrote:

Well, I have an ASUS P5N-SLI Premium MoBo, with Nvidia 8800GTS, and Creative SB X-FI Extreme Gamer Card. Running Vista Ultimate...
Been getting the 0x124 error for quite a while, but only when I watch a video. I disabled my X-Fi card in Device Manager, and... no BSOD... of course I have no sound now
I think I'm going to buy another sound card tomorrow and see if maybe may problems stay gone. I love creative, but I think they're the root cause... I'll post again with my findings...

-EW

Friday, May 11, 2007 11:10 PM

The C1E is disabled in my bios... and the only time I get the 0x124 bsod is when I am trying to watch a video...
I disabled my sound card and I was able to watch all kinds of videos without a problem... I then re-enabled my sound card and... bam!!! bsod!

I'm going to try a generic dynex sound card right now... keeping my fingers crossed... I'll let you know how it turns out...

-EW

Bowen wrote:

EvrWccn wrote:

Friday, May 11, 2007 11:44 PM

Well, back to the drawing board... I just tried a Dynex sound card and got bsod again... what's more interesting is I also got a 0x0000008E error code once I rebooted... disabled the sound card and everything works fine again... except no sound

Saturday, May 12, 2007 2:00 PM

Strange. I suppose the Dynex sound card interferes with the video driver the same way onboard audio support does. At this point, you may be stuck having to purchase an external speaker setup that connects via USB. I'm running Bose external speakers that do so and am going on five days without a BSOD after disabling the onboard audio.

Alternatively, I suppose you could wait it out to see whether nVidia realizes this is a problem and corrects it in the video driver. Christmas and the apocolypse are coming as well. Not sure which one will arrive first.

Saturday, May 12, 2007 10:56 PM

hmm.... USB speakers eh... might as well give it a try... i'll get some tonight or tomorrow and let you know how it goes...

Sunday, May 13, 2007 9:45 PM

Is there any solution to this? Whenever it crashes (completely random, but always when I try to play BF2142), there are always some things that are the same:

stop: 0x00000124 (0x00000000, [This constantly change, but "0x8" is always the same], 0xB2000000, 0x00000175)

This is becoming quite annoying. I'm assumming it's the same problem, but I don't know what to do to fix it. I have:

8800GTX, feb. 20 driver

Realtek HighDef Audio, jan. 2 driver

intel quad core

vista 32bit

Which of the solutions accurately works?

Sunday, May 13, 2007 11:11 PM

Sounds like you're going through pretty much the same agony as the rest of us. After disabling the onboard RealTek support (via the BIOS setup utility) the problem went away for me. It's been about six days now and no BSODs after making this change.

Of course, the side effect of all this is that you'll no longer have any audio if you use the motherboard-based audio support. I get around this problem by using USB-based Bose speakers. Others have reported that the blue screens continue even after purchasing audio cards.

Looks like nVidia never bothered to test the latest video driver on a machine with onboard audio support.

Tuesday, May 15, 2007 4:43 AM

Well, I think I may have fixed my problem.
First let me start by explaining what I have done already and what my computer's specs are...

ASUS P5N32-SLI Premium MOBO
NVidia 8800 GTS Graphics Card
X-Fi Extream Gamer Sound Card
2GB Corsair DDR2 Mem
And a bunch of other junk...

Steps that I tried:
1. Update all drivers to most current (x-fi and nvidia)
2. Swap sound cards (no onboard sound with my mobo)
3. Disable C1E in bios
4. Disable Virtualization in bios
5. Updated bios to latest bios
6. Swapped out Nvidia card for ATI 1650 Pro

None of the above steps worked...
What I did that seems to have fixed the problem...

I used the ASUS overclocking utility and overclocked my system by 20%....
I treid 10% first but still got the BSOD when I watched a video...
After overclocking 20% I've been BSOD free for the past 33 videos that I've watched... I've never been able to watch that many vids without a BSOD...

I'll post again tomorrow to report whether or not I get any more BSODS.... I've got a lot of vids to watch... lol...

-EW

Friday, May 18, 2007 1:39 AM

To throw another twist into this mess. I built 5 identical machines. Only one of them has this problem. It only happens when playing streaming media online with WMP. Tried swapping hard drives with one of the other machines but still had the same problem. loaded XP and it works fine, no blue screen. Only in Vista (32), only on one machine and only when listening to streaming audio online with WMP. WMP by itself will play for hours. Board is an Asus P5B, Video is Nvidia 7600 series.

Friday, May 18, 2007 10:07 PM

Well, it's been about 2 or 3 days since this last post. I have not had a single 0x124 error when watching videos... I'm guessing that by overclocking (which increases the FSB and Core voltage) the problem was solved.... Good luck to anyone else who has this problem...

-EW

EvrWccn wrote:

Friday, May 18, 2007 10:34 PM

I've not done anything with overclocking but had no blue screens for about a week after disabling the onboard sound (I'm using an MSI K8N Neo2 Platinum motherboard).

Just for the heck of it, I re-enabled the onboard sound before declaring victory. Within 15 minutes, splat -- a nice healthy blue screen of death, same old hex values. The machine was sitting quietly -- no videos running, just doing nothing -- had the desktop displayed.

I've again turned off the onboard audio and all's quiet on the blue screen front for the last several hours. I'm going to go ahead and declare success on this one -- there's something screwy about how the nVidia driver interacts with the MoBo audio.

Sunday, May 20, 2007 9:03 PM

jlitvak wrote:

I've not done anything with overclocking but had no blue screens for about a week after disabling the onboard sound (I'm using an MSI K8N Neo2 Platinum motherboard).

Have you tried installing an add-in sound card?

Sunday, May 20, 2007 9:10 PM

Fishbate wrote:

Have you tried disabling the C1E in the BIOS yet? That worked for me and I was having the exact same problem your having in addition to a couple more. I too would get a BSOD when playing streaming WMP videos and I'd also get a BSOD when playing BF2, BF2142 and sometimes COD2. Immediately after I disabled the C1E in the BIOS, all those BSOD's stopped and they haven't returned since and that was about two weeks or so ago.

Don't worry, you won't miss the C1E. It's just a HALT command used for the CPU to save energy when it's in hibernation mode. While I'd like to have it enabled, it's really no biggie. This is a new feature with the C2D and C2Q (Quad) procs and while I'm not sure, I think AMD mobo's will be getting this as well.

Sunday, May 20, 2007 10:22 PM

No. My speakers are connected via USB.

Tuesday, May 22, 2007 10:01 PM

I thought I had, but I double checked it today and it was enabled. I disabled it and it appears to have worked. I am going to reload Vista - will post back if the problem continues.

Tuesday, May 22, 2007 10:41 PM

Reloading the whole operating system seems like pretty major surgery to me. Just try running your current install with the motherboard audio disabled.

Wednesday, May 23, 2007 7:18 PM

Started the audio stream before I went home last night, came in this morning and it was still playing. Thanks for the solution.

Wednesday, May 23, 2007 7:23 PM

jlitvak wrote:

Reloading the whole operating system seems like pretty major surgery to me. Just try running your current install with the motherboard audio disabled.

It is the easiest way to reset all of the things that I tried to get this working. With a clean reload I can get everything setup the way I want it before I put it into production.

Thursday, May 24, 2007 2:47 PM

Fishbate wrote:

Started the audio stream before I went home last night, came in this morning and it was still playing. Thanks for the solution.

Sure, NP but as much as I'd like to take the credit, it was Hobz who first thought of it. If your audio is working, then your other problems that was causing BSOD's will likely work as well.

Friday, June 01, 2007 9:46 PM

Might first verify if the System BIOS is updated to at least revision 2.3.1. The latest is http://ftp.us.dell.com/bios/DXP061-020402.EXE

Monday, June 04, 2007 6:17 AM

I've got substantially the same problem:
D975XBX2
GEFORCE 7600 GT
On-board audio
Vista Ultimate
....
During games or audio-video media playback, I randomly get a BSOD. System runs fine the rest of the time, including audio-only (WMP, Rhapsody, Real).
Also has not yet happened using Media Center to play DVDs.
I am going to try the BIOS thing.

Monday, June 04, 2007 1:21 PM

There's a new version of the nVidia driver available. Don't know if they fixed the BSOD problem with it but it may be worth a spin. I've downloaded it and it seems to be OK but I figured I shouldn't tempt the gods so I haven't re-enabled my onboard sound.

Tuesday, June 05, 2007 6:38 AM

psychicfriend wrote:

I installed the latest BIOS update for the Motherboard from Intel, and that seems to have done it: at least I got thru 45 minutes of gameplay just now (and then exited normally because it's late) ,where previously I only got through 15 max before a BSOD.
The Intel BIOS readme file specifically called out a fix to sound-related event handling problems, and all the clues in the crashes I was having pointed to being sound related (i.e. the machine only ever crashed when a sound was being played, and when it crashed, it would always keep playing the last 100-200 ms of sound in a loop, even while the memory was being dumped).
Hope you all have the same fortune.

Wednesday, June 06, 2007 7:06 PM

Nope, the new driver didn't do the trick either..

Running 8600GT on a GIGABYTE 945P-S3 motherboard with Realtek HD audio integ. so obviously similar setup as most people here.

I tried the C1E thing, disabling the audio controller, all that... only thing that seems to work so far is disabling all sound recording devices in the sound control panel, but I need it so it's no good..

I guess I'll try and put my old ATI card back.. it's a shame, the 8600 is a good one...

edit: nope, disabling the mic doesn't work. neither does disabling the integ hd audio from the bios integrate peripherals page..

Saturday, June 09, 2007 5:38 PM

Hi sorry i know this is the wrong place to post but i need help!

i have vista home basics for a day and now there is no sound on my pc

can any one help?

Sunday, June 10, 2007 12:11 AM

OK, what are you system specs and do you have onboard sound or an add-in card. Also, you have tried d/ling the drivers online and then installing them? What kind of sound card do you have and I take it since you're using Vista Basic that it's 32-bit. I don't think they make Vista Basic 64-bit.

Did the sound work at first on Vista or was it working and then stop working? Like I said before....try manually installing the drivers and see if that fixes it.

Tuesday, June 12, 2007 4:26 AM

I don't think it ought to be assumed that only 9X975XBX2 Intel boards are the only ones invlolved in this problem...

>Windows Vista Home Premium (32-Bit)

>Intel Core 2 Extreme QX6700 2.66GHz Processor

>GeForce 8800 GTX 768Mb GPU (Forceware v158.24 Driver)

>Corsair XMS2 5400 2Gb DDR2 SDRAM

>WD Caviar SE16 WD5000KS 500Gb SATA HDD

>Dell 0UY253 BTX Motherboard

>nForce 590 SLI Intel Edition Chipset

>nVidia MCP55 High Definition Audio (SigmaTel C-Major 92XX Driver)

However, the common denominator seems to be integrated audio and 8800's for sure! Oh, by the way, I am getting the STOP: 0x00000124 BlueScreen, and those are the specs of my computer. But, besides making what is basically a "me too" post, I thought I'd add my particular case because it seems to be somewhat singular.

1. I do get the BlueScreen while trying to play movies in Windows Media Player 11. This happens only sometimes. Sometimes it happens three times in a row (after restarting three times and reopening the files three times, respectively). But sometimes I can play the same video files, or files in sequence even, without problems. A quixotic problem for sure! However, everything seems to be going alright using DivX Player. Seems is the operative word here, as the uncertainty principle seems in geat effect where this error is concerned!

2. I also get the BlueScreen when using Autoplay menus (the ones that start up after inserting installation discs. Most commonly encountered with games, but also some software. For example, Starcraft, Doom 3, Command & Conquer 3, and I believe Halo also caused it as well. The menus for Halo 2, Oblivion, Quake 4, Age of Empires 3, Battle for Middle Earth, Battle for Middle Earth 2, and F.E.A.R. do not seem to cause them, however. Therefore, my observations seem to indicate that only menus that feature very loud sounds, especially the kind that make noise effects when mousing over options or buttons, cause the BlueScreen. Of course, a la Uncertainty Principle, I could be wrong about any of the latter menus.

3. I can also confirm that the third address in the brackets (I believe it is the third...or maybe the second...) always starts with 0x8...you know which one I'm talking about.

4. I have not ever, had this happen for no apparent reason...yet. In my case, the BlueScreen always happens during one of the two circumstances I've listed above. I've never had this happen otherwise. I sometimes leave my computer on overnight and it has always been as I left it the morning after.

Well, there are my thoughts.

Tuesday, June 12, 2007 2:31 PM

I've been seeing these bluescreens a lot less recently, but I think it's probably because I've been watching less video (essay writing time!). The last two times it's happened it's been while watching youtube videos in firefox (so, completely unrelated to VLC or Windows Media Player).

I updated the nVidia drivers soon after the 1st of my recent 2 crashes, but since it's crashed again since then, that obviously hasn't helped!

Tuesday, June 12, 2007 10:59 PM

I bought an Alienware that has the 680i Motherboard with the integrated RealTek HD audio card and Windows Vista, this setup always causes at random times a BSOD of 0x00000124.

The only solution that I have found is to disable the motherboard HD audio card from RealTek.

I have the latest drivers posted on the net, P27, Nvidia Forceware and RealTek R.167 and it still causing this error.

How do we know that Microsoft and RealTek is working on a solution to this problem?

I emailed Realtek but never got a response.

Tuesday, June 12, 2007 11:52 PM

Hey, i´ve sent an email and they told that it was a problem from graphic card drivers but i dont think so, bsod appear when audio is enable, would Vista work if I buy a pci audio card?

Thursday, June 14, 2007 2:12 PM

Judging by the experiences of other people in this thread (including me), probably not...

I think a couple of people have had some success with usb speakers (i.e. NOT pci or on-board sound). I haven't personally tried that yet, but it might be worth giving it a go...

Saturday, June 16, 2007 3:23 AM

Bluescreen Stop 124

0x0000124

0x00000000
0x85207028
0xB2000000
0x00070F0F

Will most likely be resolved by:

http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=23&Level=4&Conn=3&DownTypeID=3&GetDown=false

next most likely is to update the BIOS & CMOS - contact motherboard manufacturer

finally, ensure latest and correct nVidia drivers for Vista:

http://www.nvidia.com/content/drivers/drivers.asp

If all three of the foregoing have been done and still not resolved AND you have a kernel (preferred) or complete memory dump, please open a case with MS PSS, and post your case # (SRZ or SRX) here as a reply post.

Phone Support
Wait Time: Will vary
Hours of Operation
90-day no-charge support begins on the following dates:
From the date you place your first support request.
For Windows Vista, from the date you activate the product.

(866) 234-6020

or Web Support

https://support.microsoft.com/oas/default.aspx?ln=en-us&x=12&y=6&prid=10300&gprid=436974

Saturday, June 16, 2007 1:54 PM

Descendant7 wrote:

I don't think it ought to be assumed that only 9X975XBX2 Intel boards are the only ones invlolved in this problem...

>Windows Vista Home Premium (32-Bit)

>Intel Core 2 Extreme QX6700 2.66GHz Processor

>GeForce 8800 GTX 768Mb GPU (Forceware v158.24 Driver)

>Corsair XMS2 5400 2Gb DDR2 SDRAM

>WD Caviar SE16 WD5000KS 500Gb SATA HDD

>Dell 0UY253 BTX Motherboard

>nForce 590 SLI Intel Edition Chipset

>nVidia MCP55 High Definition Audio (SigmaTel C-Major 92XX Driver)

3. I can also confirm that the third address in the brackets (I believe it is the third...or maybe the second...) always starts with 0x8...you know which one I'm talking about.

Well, there are my thoughts.

Do you still get a BSOD if you completely disable the sound in Device Manager? If not then it's most definitely related to the sound. It stopped the BSOD's for me completely, but then that's not a fix at all. The way mine was fixed was by disabling the "C1E" function in the BIOS. This doesn't work for everyone, but it worked perfectly for me. I have read that some people's problem stopped with newer or certain Forware drivers and yeah, it does look like the 8800 GTX is a key player in all of this.

Sunday, June 17, 2007 1:04 AM

I think you're right. I happened to me with an MSI K8N Neo2 Platinum board running an AMD 4000+ processor. As soon as I disabled the onboard audio, the problem went away. Hasn't happened once since.

Sunday, June 17, 2007 2:19 AM

Bluescreen Stop 124

0x0000124

0x00000000
0x85207028
0xB2000000
0x00070F0F

Will most likely be resolved by:

http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=23&Level=4&Conn=3&DownTypeID=3&GetDown=false

next most likely is to update the BIOS & CMOS - contact motherboard manufacturer

finally, ensure latest and correct nVidia drivers for Vista:

http://www.nvidia.com/content/drivers/drivers.asp

(866) 234-6020

or Web Support

https://support.microsoft.com/oas/default.aspx?ln=en-us&x=12&y=6&prid=10300&gprid=436974

Sunday, June 17, 2007 7:05 PM

Well, I'll be pickled! I just had a STOP: 124 error while playing Command & Conquer 3, when I was at the end of a load screen in multiplayer! This is the very first time this has happened to me for a reason other than what I described above. Well, I thought I could anticipate this problem, but who knows when it could happen now. For the record, this is b***s***. Total. F***ing. B***s***.

Let's see...using the Problem Reports and Solutions, I count that this has happened to me 38 times now. Man I wish I knew who's responsible for this garbage, and above all, who is supposed to be doing something about this and isn't. I disabled my integrated sound and played some videos, and I had no crash (I can't really say this is a definitive answer for me, but I'll certainly take the evidence the rest of you seem to have regarding the sound devices). Unfortunately, I need sound, or my games become unplayable. Oh and videos become unwatcheable. Except I'm not even watching any movies on this computer because then my computer will crash! I just hope this doesn't start happening often during gaming.

However, I'd be really curious to hear whether this crash has happened to anyone who has their integrated sound. Not because that's what I want, but because it would be a good idea to let everyone know if that happens.

Wednesday, June 20, 2007 1:13 AM

Yea... so i have the 680i, 8800gtx and the newest bios... any1 got a real good answer and not another "i have that same problem"??? so ive been pretty much pissed off with my build because of that damn BSOD on multi media stuff so if any1 have an answer to this problem dont be shy to tell us.

Wednesday, June 20, 2007 3:24 AM

Disabling the C1E instructions in the BIOS fixed the BSOD for me. I have the Nvidia 680i motherboard with RealTek HD audio built in.

Also using Bios version P27.

Tuesday, June 26, 2007 7:48 PM

Hobz wrote:

Diabling "C1E" in BIOS took care of this problem for me.

You can locate C1E under your CPU-settings in BIOS.

Do a google search on the C1E to learn what it is.

My system set up here is as follows

Intel Core Duo

Nivdia 8500 GT

Hauppauge Win-TV 67xxx

Creative X-fi Xtreme audio

On Board Realtek HD audio

Vista Home premium 32bit

The system used to bsod everytime you tried to play and audio cd or view a video, then it gradually decreased to bsoding every 5 minutes and then failing to boot at all. We discovered that the system worked without issue disabling all audio but this was not a viable option. We bought the xfi in a hope that it was just onboard audio crashing the pc however it bsod'd with the PCI solution as well. Disabling onboard sound, upgrading to the latest nvidia drivers and disabling c1e in bios as so far stopped the bsod.

Thanks to the solutions posted here! I can now use my pc again!

Though can someone explain to me how this solution is working? I take it it’s the nvidia drivers to blame?

Tuesday, June 26, 2007 7:49 PM

Hobz wrote:

Diabling "C1E" in BIOS took care of this problem for me.

You can locate C1E under your CPU-settings in BIOS.

Do a google search on the C1E to learn what it is.

My system set up here is as follows

Intel Core Duo

Nivdia 8500 GT

Hauppauge Win-TV 67xxx

Creative X-fi Xtreme audio

On Board Realtek HD audio

Vista Home premium 32bit

Thanks to the solutions posted here! I can now use my pc again!

Though can someone explain to me how this solution is working? I take it it’s the nvidia drivers to blame?

Wednesday, June 27, 2007 2:45 AM

After Tom's post above, I:

installed the realtek update
updated my bios again (Previously updated, but gigabyte since released a new version - revision 10 - I don't have my model number handy, but it's there earlier in the thread somewhere)

(C1E was previously disabled in bios, but did nothing on its own - I haven't tried re-enabling it, and probably won't!)

and I've been a week without a single bluescreen. I've also been watching plenty of video in media player, vlc, youtube, etc... all of which had previously caused bluescreens.

I'm still not 100% convinced the problem has gone, but this is probably the longest period i've seen without a bluescreen where I've actually been using my computer normally.

Friday, June 29, 2007 7:15 PM

Okay, partly another "me too", but also this may broaden the scope a bit... or maybe refine it? I have the following system:

CPU: Intel E6300

MOBO: Asus p5b-e

RAM: 3GB Corsair XPS2 ddr2 800 (2 sticks 512 + 2 sticks 1gb)

VIDEO: nVidia 7950GT

HDD: WD 250 SATA

AUDIO: ADI 8-channel HD Integrated

OS: Vista home premium, 32

First, thank you guys for all the good information, and please keep it coming! I have narrowed things down I think quite a bit based solely on advice offered here. I don't, however, know how to pull the specific error numbers from the system logs to verify if I'm going through exacly the same issue, so any help there would be awesome. I started with your suggestions because I figured I couldn't hurt anything by trying them.

So, starting with a summary... I think It all boils down to the integrated audio for me too. Following is a list of what I did, in backwards order:

8) Disabled microphone and line-in (I read that this worked for somebody here, was that all there is to disabling the recording portion of the driver?) Hoping this works and allows me to use sound on the system because it's awefuly lonely with nothing but the droning of pc fans to keep you company. So far I have about an hour of iTunes use behind me with no BSOD on this attempt.

7) Disabled audio driver completely... seems to have done it so far. I have been able to play iTunes repeatedly and World of Warcraft for about 4 hours totally error free.

6) Uninstalled audio driver, and let microsoft default take over. No luck.

5) Upgraded bios from 11xx to 1201 (wasn't that long ago that I upgraded this, but wow such a jump in rev. #s already!). Left the c1 cpu setting enabled for the time being since it didn't seem to work for me.

4) Updated nVidia to 158.xx (interestingly, nVidia lists this driver as the same for the 8 series cards too... so to me the error points more to driver than hardware, right? And probably keeps me right in the same issue category as you all, which is why I am writing)

3) Ensured updated audio drivers, which I did update not long ago. They were up to date. So on a hunch I thought maybe this update was close to the onset of my BSOD woes, so I "downgraded" back to a previous version. Having no success with that, and an almost instand BSOD, I updated back to current.

2) Disabled the c1 setting for my cpu. Seemed to work for about a day, but next day WHAM, right out of the gates with a BSOD! Left this disabled in case it was only partly responsible.

1) Reseated RAM, no worky.

Couple of notes...

a) My BSOD is pretty random, sometimes coming 10 minutes into a World Of Warcraft session, and other times not happening at all over a 4 hour session. My very first BSOD was within iTunes, while playing a video. I was able to repeat this twice on the same video, and then a while later (another day) the video worked flawlessly throughout. Some days system is very stable, other days not at all. Vista reports my stability index (on a scale of 1-10) as about a 5... 50% really sucks if you ask me. All times the BSOD is so fast before an automatic reboot that I can't read anything on it.

b) Whenever it crashes, I have to wait a short period, and sometimes even reset the bios before the system will come back up. If I try to restart right away I usually get into a reboot loop. If I check memory right away, it sometimes shows that the memory as failing, and sometimes says I have a hardware error and can't continue (this is with the vista memory check, and why won't it tell me which hardware failed???). A 10 minute wait or a bios reset and all memory and hardware then checks out!

c) I don't overclock, and "memory speed select" is set to auto (which either sets it at 800, or downgrades, never more). This board also has an "auto overclock" feature for the cpu, I have had this disabled for some time. I have verified with Asus and Crucial that the ram and board are compatible.

d) The only thing on the system that gets even warm is the chipset. It has a heatsink of course, and is sometimes almost too hot to touch. Reviews and boards have said this is common even in stable systems.

e) I have two case fans, one in back and one right above the ram... both blowing out. I also of course have the cpu stock fan. Air is always fairly cool from all three. System monitors report average of 100 F on cpu and mobo.

That's the most accurate info I can remember or am capable of offering at this time. Any suggestions you guys might have would be greatly appreciated. As long as things stay stable, I'll leave the recording features of my audio disabled, but eventually I would really like it back! Thanks again everyone!

Saturday, June 30, 2007 8:05 AM

First of all, my build doesn't stay stable in XP, either. In XP, it crashes randomly, without even a blue screen, even when the automatic restart is disabled. Upon installing Vista, at least I got a blue screen, which I found soothing. And yes, it's the 0x0000124.

I think it has little to do with nVidia, Intel chipset, or any of that. It's just something to do with a combination of some Core 2 Duo chips and various motherboards with various audio drivers. That's because I've had this same exact problem (in XP, I didn't have Vista installed in one of them) in two builds whose only common components were an E6300 processor and G.Skill memory (passes memtest fine). One was completely stable. And yes, I actually installed the same E6300 processor chip in all three of them to test them out, and more and more I think about it, the more the Core 2 Duo seems to be at fault.

A Gigabyte 945 w/ integrated graphics, HD Audio, and ATI X1600 works completely fine with the processor, but underclocks the CPU because it only supports 800 FSB. However, I don't think FSB is much of an issue, because on my other two boards (ASUS P5B Deluxe w/ WiFi and MSI I forget but it's an nVidia chipset) it restarts randomly no matter what the FSB is, and no matter what the graphics card is (ATI X1600, ATI X1950). If I had an extra CPU lying around, I could confirm this. This issue has really tired me out to the point where I'm toying with the idea of buying a new E4400 processor just to get things stable again.

It's just that my $40 integrated graphics mATX motherboard was stable and my $140 and $200 premium motherboards crash randomly. You know, puts a lot of faith in Intel. I love the Core 2 Duo, but this problem has truly been tiresome.

Saturday, June 30, 2007 3:03 PM

I just wanted to let everyone know that I have been chasing this Vista BSOD issue now for about two months. I have tried new sound cards, different memory, rebuilding from scratch, C1E disabled (with test MSI BIOS) and nothing worked for me.

The other day I caught a post on /. (http://hardware.slashdot.org/article.pl?sid=07/06/26/2152246) regarding some bugs in early Intel Core 2 Duo processors. Microsoft released a microcode reliability update to resolve some stability issues (http://support.microsoft.com/?kbid=936357). On a whim I applied this patch and my Vista BSOD STOP 0x00000124 issues have been resolved. I am interested if others have tried this patch and if you do install it, if it resolves your problem as well.

BladeDSS

Sunday, July 01, 2007 5:53 AM

I applied the intel update just minutes ago. I am posting from my wife's mac because just seconds ago it crashed again. After the update I had to restart of course, and after the restart the system reported that my sound driver had been modified and needed to be reinstalled. I tried to reinstall, but about 10% through the system hung again... without the driver being enabled yet. I have heard people say that their crashes came more and more frequently till it quit working altogether. It seems as though the crashes on mine are getting more frequent. I hope doomsday is not approaching my machine. I'm frustrated to say the least. I'll try reinstalling the sound driver again tomorrow, as it's late and i'm grumpy now.

I think I'll go watch some elves hack up some orcs... that should help.......

......thanks in advance for any advice anyone has left to offer!

Wednesday, July 04, 2007 12:26 PM

Hi all,

I've been keeping a close eye on this thread for a while. For 4 months now, I have been trying to get my system running and have had the same trouble as most of you concerning the Stop Code 0x00000124.

Although I am running my E6600 with an 8800GTS on an Asus P5W64 (with AD 1988b onboard sound), I think the problem is the same. Every single component of my System was exchanged during the last 4 months to no avail (except the processor). No Bios previous to May of 2007 helped. Any Sound-Device (Audigy 2 or onboard) resulted in more or less sporadic 124-BSOD's as you all have already described. I have tried every combination of system settings and drivers, reducing the pc to a minimum of components, to no avail. Using Teamspeak2 actually helped create quickly reproducable BS's for "testing" purposes. As with the rest of you, disabling the sound device helped.

The exact same system with the same drivers and Software (Vista Business MSDNAA 32bit) works fine on the pc of my neighbour - which was even more frustrating. But, just before selling my pc in bits an pieces, I also stumbled across the Microcode Update. For me, this seems to have solved the problem. Asus, just as many other mb-manufacturers also brought out new Bios versions (which include the new microcode - post May 2007) for most mb's.

I do not think that at this stage, this is still an Nvidia-Sound-Vista problem for one simple reason: on a fresh install without the nvidia drivers the bluescreen turns up just as often (using the Teamspeak2 software which is Vista compatible). It might be a way for some of you to test if your problem is solvable with the microcode update.

Regards - and keep hanging in there!

Edit: Yes, my System was also unstable in XP as well (even though not nearly as unstable as in Vista). Usually Prog's would crash with some sort "memory write error". This seems "backtrackable" to the microcode as well.

Saturday, July 07, 2007 9:52 PM

Try this...

http://support.microsoft.com/kb/936357/en-us

Sunday, July 08, 2007 6:41 PM

It's not just an Intel or dual core issue..
I'm still on XP-Pro, running an AMD FX-55 chip have a 7900 GT KO card, an X-FI soundcard and have BSOD's as well. So far in addition to reading all the posts on this site I've:
-Removed my soundcard and drivers, enabled onboard audio in the bios, loaded the AC97 drivers and still get the BSOD.
-Re-installed XP,
-Deleted and re-installed the last three drivers from Nvidia and still get the blue screen.
-Can't find C1E in the bios let alone disable it and I have an evga nforce 4 mainboard.

Lately I've been thinking...
Memory leak?... why else the physical memory dump? (0x000007) My page file is big enough.
But then I'm getting 'Stop' warnings upon reboot that it's my device driver that caused the problem.
Another thing. I don't get the BSOD's when gaming, only when watching video in Firefox or DivX, or PowerDVD.
Reminds me of the old days with the 'Detonator' drivers and IRQ conflicts, Good grief!

Monday, July 09, 2007 4:21 AM

This email thread has bugcheck with a stop code of 0x124. If you have a different stop code, please open up a new thread so people can help you out.

Also, please pay attention to the hexidecimals. For the "0x000007" BSOD, you are missing two digits, so it'll be difficult to gather anything from that.

If I had to guess, it's 0x0000007A or 0x0000007E

0x7A is usually a HDD issue or IDE/SATA cable going bad...

Good luck...

Monday, July 09, 2007 2:44 PM

I applied the stability patch, re-booted and thoroughly checked my system. This update has completely cured the radom crashes and my PC is 100% stable.

I have unchecked CE1 in the BIOS which did give stability in the past.

It would seem that the problem has nothing to do with video/audio drivers but with certain combinations of hardware and some Intel CPU's. I am delighted that Microsoft has now provided a solution.

Thanks for your help.

Monday, July 09, 2007 2:55 PM

stability patch? where can i download it?

Monday, July 09, 2007 3:26 PM

http://www.microsoft.com/downloads/details.aspx?FamilyID=eacdfdeb-c1f1-4404-8c50-5d039f5d172d&displaylang=en&Hash=UMjpwT%2fJHexj2O7fUIucK1IAXZd31xWR%2f%2fFHNvwBYcqqh0VoGIiTBHz%2fVc2uq8of4troyhMsO09cwrzct7d0lg%3d%3d

It refuses to install on my Vista 32 bit.

Any ideas? Spyware Doc disabled during installation.

Thanks.

Steve

Monday, July 09, 2007 6:13 PM

http://support.microsoft.com/kb/936357/en-us

Tuesday, July 10, 2007 5:16 AM

I have similar setup (ASUS P5W DH Deluxe + Nvidia 8800 Series + Vista32 + QX6700 Quad Core) and indeed have been struggling with the same 0x00000124 problem for months. I've worked on ASUS, Nvidia, Realtek with no luck.

I recently worked around the problem by disabling C1E (about a month ago).

A couple of days ago I tried the Intel Errata patch and I am was able to re-enable C1E since then!! Issues with the Intel processors seem to have been at the root of the problem since the beginning. I wish someone at ASUS/Nvidia/Realtek could have pointed me in the way of a Intel issue ealier.

Now if Nvidia would just get fully functional 8800 drivers out there I would finally have a fully functional Vista system.

-Phil

Tuesday, July 10, 2007 8:53 AM

Ok, I have the very same problem.

It start about 2 months ago for no reason at all, and happens completely at random.

I can use my PC for hours without any problem, other times I dont get more then 2 mins.

Browsing the net seems fine, playing games is major pain

The hotfix is no good for me since I'm running an AMD 4600+ and not an Intel cpu.

My BIOS does not have a 'C1E' option to dissable.

I have tried all the latest / oldest / in between drivers I can find.

Updated the BIOS, still no 'C1E' option .. What does this do anyway ??

Different hardware I have tried, consist of:

7800GTX, 8800GTX, 6100GT, Onboard 6100

AMD X2 4600+, AMD XP3500

Audigy 2 ZS, Onboard AC97

4 different types of DDR memory sticks

450 watt / 550 watt PSU's

Pioneer / LG DVD drives

Seagate IDE / SATA HD drives

Windows XP / Vista 32

No matter which comination of hardware I have used, it always ends the with the same 0x124 error.

The stupid thing is though, I have an MSI mainboard with the same NV4 / AC97 chipset,

and it works 100% fine with all the hardware list above, no matter what drivers I install it with.

Anyone able to help with an AMD fix would be great.

Tuesday, July 10, 2007 11:51 AM

I have pretty much the same configuration you do and was able to get rid of the problem by disabling the onboard AC97 device (I won't swear to it, but it feels like that's the AMD equivalent of C1E). I've heard mixed results about whether this will take care of the entire problem because the Audigy board may also cause conflicts. I use Bose speakers which are driven via USB -- no additional sound card.

I also found on another machine I have with an nVidia 7800 that if I simply didn't download the nVidia driver from the nVidia Web site, I have no problems. I'm using an nVidia driver that comes down as part of the normal Vista automatic update process and have had nary a BSOD. A little will power to resist getting the latest stuff from nVidia seems to go a long way.

Tuesday, July 10, 2007 12:37 PM

Actually, it installed after a reboot , so I'm off to re-enable C1E.

In case anyone's interested:

"Disabling C1E means the CPU cannot go into a power saving halt state. It

isn't a problem, and many systems do not even support this feature. When

C1E is enabled the CPU can disable parts which are not in use, waking them up

again when needed."

Steve

Tuesday, July 10, 2007 1:24 PM

Thanks for the info Steve, I suspected it was something like that.

On that note though, would the AMD 'Cool and Quiet' be a similar feature ?

My BIOS does have an option to turn 'C&Q' on or off, maybe I will give it a go.

But for now, I just spent the last 4 hours re-installing from a completely re-partitioned / formatted HD.

I will not be installing a single driver update, other then the ones supplied through Windows Update.

Doubt this will fix my problem, but I've got nothing else to try.

Wednesday, July 11, 2007 11:54 AM

incredible..... it works!

thanks

Wednesday, July 11, 2007 3:42 PM

KB 936357 is now on Windows Update

http://support.microsoft.com/kb/936357/en-us

Thursday, July 12, 2007 12:35 PM

Well after a couple more days testing things and tweaking stuff etc etc, I still could not fix this problem.

I have removed the motherboard and replaced it with a new one of different chipset completely.

That fixed it .. lol

Tuesday, July 17, 2007 12:52 AM

had a problem, when I try to run the patch, it says that doesn´t work with my system (Vista Ultimate 32 bits)

Tuesday, July 17, 2007 1:34 AM

I have also recently been getting this error in Vista Ultimate 64bit completely randomly.

" The system has encountered an uncorrectable hardware error
STOP:0x00000124(0x0000000000000000, 0xFFFFFA80019A8D10, 0x00000000B2000000, 0x000000000070F0F)"

This is my system:
7800GT graphics card
AMD 3700+ CPU
Creative Xfi-xtreme music soundcard
1gb RAM
ASUS A8N-SLI mobo
OS: Vista 64bit Ultimate

I have tried updating all my device drivers, updated my bios, disabled onboard sound, updated windows.

Can anyone help me?

Tuesday, July 17, 2007 2:13 AM

Keep in mind that the patch is for Intel processors. I suspect it won't run if you've got an AMD.

Tuesday, July 17, 2007 2:51 AM

Why cant i see my post?

Well i'll post it here again anyway:

I have also recently been getting this error in Vista Ultimate 64bit completely randomly.

"The system has encountered an uncorrectable hardware error
STOP:0x00000124(0x0000000000000000, 0xFFFFFA80019A8D10, 0x00000000B2000000, 0x000000000070F0F)"

PC specs:
windows Vista64bit ultimate
7800gt graphics card
Asus A8N -SLI mobo
1gb ddr400ram
600watt psu
AMD3700+ cpu
Creative X-fi xtreme music soundcard

Tuesday, July 17, 2007 3:51 PM

Hi, I have a 6300 intel processor, I had the same problem (BSOD) on XP but the patch works perfect

Thursday, July 19, 2007 3:19 AM

Please can somebody help? Is there anything that can be done about this error?

Saturday, July 21, 2007 3:11 PM

I have the E6600 Intel Dual Core CPU and when I attempted to install the patch, it said it didn't apply. I'm therefore assuming that microcode fix is only for the E6300; but that doesn't help my situation much since I too have been experiencing the 0x00000124 Stop Screens along with random system freezes. I don't have the C1E option in my BIOS, so that is not a solution either. I've been battling this for 4 months now. I haven't disabled the on-board Audo yet; but that's next. The problem is so random that it can go for days without a problem; and then boom it will lock-up several times in a short span of time. I'm seriously frustrated. All drivers are completely up to date as well. It may be time to take nVidia, Intel, and MS to task over this since there seems to be an awful lot of us having the same problme and none of these manufacturer seems to really care.

Tuesday, July 24, 2007 2:00 AM

Can anyone help me?

These are some more errors i'm getting:
0x00000124(0x0000000000000000,0xFFFFFA80019A5BF0,0 x00000000B2000000,0x0000000000070F0F
and
0x00000124(0x0000000000000000,0xFFFFFA80019A8870,0 x00000000B2000000,0x0000000000070F0F

Really need help.

Tuesday, July 24, 2007 10:25 AM

After weeks of searching for a fix, I have found absolutely nothing.

No-one is willing to admit they have a problem with thier drivers / chipset.

So I contact the manufacturers of my MB and talked to them about his problem.

They told me to send the MB back to them and they would be happy to replace it with a new one.

I sent the MB back to them and a couple days later I got a new one back of the exact same model / brand.

Its working 100% without a crash, using all the same drivers as the old MB.

Maybe its a faulty chipset that only effects a small number of people.

I suggest you do the same and get a new MB also if you can.

Thursday, July 26, 2007 10:56 AM

Are you absolutely sure it's the motherboard? The last few times i've tried to get hardware replaced it's been like going through hell and back...It's a lot of effort i want to be fairly sure before i try it.

Thursday, July 26, 2007 2:11 PM

Yeah I'm sure its the MB ..

I have 2 identical PCs here, and I tried all the hardware in both of them.

My main PC works fine with all the components from both machines, using the same drivers on both PCs.

My second PC will crash to the 0x124 error, no matter what components are installed in it.

Both my MBs are Albatron with nForce 4 chipset, AC97 audio.

1 works 100% with everything, the other is flakey even with nothing extra plugged in, reguardless of which OS / Drivers.

I called Albatron and they told me to send the MB back to get a new replacement.

The new MB is the same as the old one, but this one works 100%

Sunday, August 12, 2007 8:25 PM

SOLUTION FOR ME.

I had this same exact problem my friends. 0x00000124.

I have a DFI SLI DR Expert and an 8800GTS. For me, I had to do a good CMOS reset. Until I did this I couldn't even boot my computer past the Vista loading screen, even at laxxed settings. No amount of turning the computer off overnight or changing clock speeds or anything made any difference.

Do the following... turn off computer, turn power switch off on the back of your power supply, jump the cmos jumper, wait 10 minutes, push the power button a few times with the computer still off and the power supply off to discharge any power still in the system, move the cmos jumper back, push power button a few more times, THEN turn power supply switch back on, wait 10 minutes, then power on system, go into bios and load defaults, then try to boot with defaults loaded. That may do it for you. It worked for me. NO MORE PROBLEM

Sunday, August 12, 2007 8:47 PM

Fingers cross, but don't get your hopes up. I've been having exactly the same problem with my machine: Running a Microstar Neo 2 Platinum motherboard with an AMD 4000+ processor. Note that I'm running an AGP nVidia 7800GS. Just when I think I have a good solution, whammo, I get a batch of BSOD 124s. I'll try something, go a couple weeks, think all is well, then they start up again.

I noticed that after a BSOD 124, my BIOS seemed fried as well. Mine was unable to find its hard drives. I thought maybe the problem was a bad BIOS battery. After replacing it, I jumped the BIOS exactly as you describe. All OK for a day (or maybe a few) then the BSODs start up again. No software or hardware modifications. Maybe you'll have better luck than me. I've tried all the disabling, etc. others have recommended on this thread, pulled boards, the works. It has gotten to the point that I'm wondering if it's one of the IDE controllers or the nVidia chipset drivers (this board uses the v3 nVidia stuff, which is pretty old).

I did notice that things go to hell mighty fast if you use the drivers from the nVidia Web site. I seem to have somewhat better luck with the driver updates that come from Windows Update.

Just for the heck of it, I cracked the machine one last time, made sure all the cards were properly seated and power connections nice and snug. No problems found. Then, because I have nothing else to do on a balmy Saturday, I reloaded Vista Ultimate.

I'm 24 hours with no BSODs. We shall see.....

Monday, August 13, 2007 5:45 AM

READ THIS CAREFULLY ALL WHO ARE HAVING THIS AND RELATED BLUESCREEN PROBLEMS IN VISTA (AND XP):

I definately think that most of those complaining of this issue need to reset their CMOS with the jumper. For me, If I overclocked just a little bit too far on the FSB, I get partition corruption and have problems booting windows. CMOS GOT SCREWED!

Even after doing an Acronis parition restore (but before jumping cmos), the corruption still remains and I still can't boot windows. It is only after jumping CMOS, Formatting the corrupted partition THEN doing the acronis restore will everything be back to normal and all corruption and boot problems are gone.

I think that some of you could have corrupt partitions that need to be formatted like I did, then your data restored to the newly formatted and created partition. If you have multiple partitions, then you should do this method on all of them just in case. It has fixed all of my random bluescreen problems and the inability to boot windows problems in windows Vista.

I was getting several random bluescreens including but not limited to:

DRIVER IRQL NOT LESS OR EQUAL

USB BUG CODE DRIVER

0x00000024

0x00000124

Bad Pool Caller

All random, but the bad pool caller only when I accessed certain areas on my partitions.

I ultimately DO NOT THINK IT IS YOUR SOUNDCARDS AT ALL (many of you have the onboard Realtek which is the same or similar to what I have on my DFI SLI-DR Expert). This is something that if disabled may mask the symptom, but the symptom is still hiding.

RESET CMOS WITH JUMPER PROPERLY following my instructions in my previous post exactly, THEN REFORMAT YOUR PARTITIONS AND RESTORE YOUR DATA.

NOTE: On your partitions that contain data only (IE: they aren't your primary boot drive), just restore the data files, do not do a complete "partition restore" as this will just bring the corruption right back. Just restore the data files to the root of the partition.

DOUBLE NOTE: Make sure your system is at DEFAULT bios settings. NOT OVERCLOCKED AT ALL IN ANY SENSE AT ANY TIME DURING THE TROUBLESHOOTING.

This will solve a lot of your problems people.

Wednesday, September 05, 2007 9:27 PM

Ok so here is my problem same as you guys random BSOD'S Stop 0x124 Error so i can tell you its deffinetly not your Creative Sound cards or on board sound or any of that *** i was having my BSODS before i even got my Creative Sound card and i was using a Logitech USB Audio headset, so i have RMA'd my ram no change at all, Tried different RAM no change at all, so i started thinking to my self maybe a faulty chipset, But then i got on to asus spport they said try loads of different stuff which i did and none of it worked, it was stuff like CMOS reset and all that, so i was still getting them tried a different motherboard, still no different still getting BSODS. I have fully updated BIOS, Drivers the lot. Also i have come to the conclussion it is not your Processor at all my best guess is a conflict beetween VISTA and GRAPHICS DRIVER'S also if you have looked around a bit Microsoft have admitted to this problem being there fault and have a hotfix got the hotfix it didnt work for me. I am currently still having these Problems anyone who can help please HELP

ALSO I WOULD LIKE TO KNOW HAS ANYONES ISSUE'S BEEN CURED BY USING WINDOWS XP PLEASE REPLY IF SO

My RIG
Motherboard - Asus Striker Extrem nForce 680i SLI
Processor - Intel Core 2 Duo E6600
RAM - OCZ DDR2 1066 PC2 8500 Reaper Heat Pipe Conduct Edition
Graphics Card - BFG Tech Nvidia GeForce 8800 GTS 320MB
Power Supply - OCZ GameXstream 700W
Hard Drive - Western Digital Caviar SE 16 320Gb
Case - Antec 900 Gaming Case

Wednesday, September 05, 2007 9:39 PM

I think Breathless got it right. I was having the same litany of BSOD with 124 as the error code as everyone else. New video drivers, disabling stuff in the BIOS, screwing around with sound adapters and other odds and ends would occasionally do the trick for a few days but the only surefire solution I've found -- more than a month without a single BSOD -- was to reset the BIOS, then totally blow away the boot disk (I did my data disk as well). None of this reformat stuff: After you reset the BIOS, nuke the entire partition and start the Vista install from bare metal.

Knock on wood, I'm going to to claim victory on this one -- once and for all.

I'd be willing to agree that there is something screwball about the video drivers that may kick the problem off (I refuse to download the latest drivers from nVidia -- I'm running the updates that come via Windows Update instead), but once the problem starts, you're screwed until you reset the BIOS, repartition and rebuild the disks from scratch.

Thursday, September 06, 2007 4:59 PM

While I didn't go as drastic as re-partitioning my HD, I did run Breathless' technique on my system. A couple of interesting things occurred. First, was a message in the system tray that had a record of the failures. I've never seen this before or since; but I did look at the log; and it consistenly reported problems with nVidia and McAfee. The dates of the entries were consistent with the BSODs and lock-ups. So I went to nVidia's site and found yet another updated driver. I installed it. Then I uninstalled and re-installed McAfee. I believe that McAfee was responsible for the system lock-ups and nVidia for the BSOD's. Since I've done this, the system has been stable. I've had not further lock-ups or BSODs. As I stated in my earlier post, this has been random; and has gone on for days before having a problem. But for now, It's lasted longer than it every has. So here's to hoping. Thanks to Breathless. This may in fact be the cure.

Saturday, October 13, 2007 4:23 PM

Ok guys how many of you are still having this problem and you have Wireless Cards, ok right now remove you wireless card from your computer and it will 100% fix the problem did for me and my pc is know working great

Saturday, October 13, 2007 4:33 PM

Sorry, I'm not buying it. I have a wired connection on my machine and tried everything I could think of (and suggestion on this thread). The only definitive solution was to gut the machine, taking the boot disk down to bare metal, repartition, reload Vista, then all apps. I'm going on about four months without a blue screen after doing so. The latest nVidia driver seems to be well-behaved.

Saturday, October 13, 2007 10:25 PM

Ok, I dont want to be rude or anything here, but how can people say 'do this and it will fix your problem 100%' ??

Everyone has different systems and components, running different drivers etc etc ..

There is no way you can be 100% sure that whatever fixed your problem, will fix everyone elses problem.

For me I tried every single thing list in this thread, and not one single thing worked.

I pulled out all my PCI cards, removed all extra drives, formatted the HD, installed a completely new HD, swapped out the CPU and memory, took my 8800 and ran on the onboard FX chipset and so on ..

Everytime I got my PC working again it was without sound drivers and no matter which version of drivers I used, or whichever sound card I used, as soon as I installed sound drivers I would get the error. Even after uninstalling the drivers again, it still BSOD until I re-format and installed from scratch again.

Nothing fixed my problem with this error, so I contact the MB supplier and got a new one and hey presto my problem was gone.

Sorry I dont mean to rant to anything but I find it very annoying when people say they fixed thier problem and expect everyone else to be cured by the miracle they discovered that no-one else could have tried.

So maybe instead of people saying 'DO THIS, THIS WILL FIX IT', perhaps your should be saying 'Try This, it worked for me'

Sunday, October 14, 2007 7:19 PM

Me neither. My system doesn't have wireless. I can tell you that after resetting CMOS ~2 months ago, the 0x00000124 error has returned only once. I also updated my nVidia drivers at the same time. I was still getting random lock-up; but not near the frequency I was until I updated to the latest drivers last week. Now lock-up have returned with a vengence.

Sunday, December 09, 2007 6:27 AM

I did not start receiving the BAD POOL CALLER error (blue screen) until I tried to reload XP Home. Now it gets to the point of installing drivers and won't go past this point without shutting down and giving me the blue screen. The reason that I was reloading is because I couldn't access the system restore function at all, just sat and acted like it didn't know what to do. Also the computer was starting to run very slow. Can you help me with this error?

Monday, December 31, 2007 1:37 AM

Wednesday, January 02, 2008 2:26 PM

Hi there,

I am getting this BSOD quite frequently.

Using Vista Home Premium 32 bit.

I've basically been building this for a while to be a HTPC in my front room. We've just moved in so i've set it up and it's great when it works but blue sceens with STOP 0x00000124.

I've ordered a new power supply as I was certain that was what is causing it (it's an Enermax but only 350w!). I'm running....

AMD Opteron 165
2 x 1Gb DDR400
MSI NX8600GT Graphics (PCI-E x16)
Gigabyte GA-K8N51PVMNT-9 Mobo (nForce chipset I believe - onboard 6200 AGP as well)
AuzenTech x-Plosion 7.1 soundcard (PCI)
Compro VideoMate Dual DVB-T Tuner (PCI-E)
Compro VideoMate Single DVB-T Tuner (PCI)

The system is RESONABLY stable when watching live tv but will most probably crash when playing music especially when there is another load on the system - for instance, I was listening to music and the Vista "Aurora" Screensaver came on - CRASH!!!

It has crashed with this error even when not using sound - I was copying 40Gb of data via Gigabit network (onboard network).

I think, if I remember right, the system is running the drivers that come via Windows Update for the graphics.

I'm going to go home and try some of the solutions here and report back tomorrow.

- BIOS update (if it's not already the most up-to-date)
- Disable On-board sound and video (not using them)
- Disable sound inputs (mic, line-in)
- Hard CMOS update (as described above)

Still waiting on my power supply coming (650w should do it?). I'm also going to monitor temps and fan speeds (my graphics card is passively cooled - possibly that?)

Wednesday, January 02, 2008 3:50 PM

You should seriously consider using drivers from nVidia and not MS. I've been fighting this problem for 9 months; and when it re-occurs, it has always been the MS drivers that have caused the problem. The hard BIOS reset is also highly recommended. The combination of the nVidia drivers with the BIOS reset has worked the best for me. If you have an nVidia chipset on your Mobo (which it sounds as though you do), then also use the nVidia drivers you will find there as well. nVidia has an activeX control that will check your system to verify your Mobo and Video card and validate which drivers it needs.

As I stated, I've been fighting this for a long time; and I've seen it return. But this is the solution that has been the most sustained; and has worked the best. I've been on the current driver set without a 124 BSOD, system lockup, or reboot for nearly two weeks so far. I'm hoping the solution has finally been found. But so far so good.

Good luck!

Thursday, January 03, 2008 10:31 AM

OK, I'm now running the latest nVidia drivers and have disabled onboard sound and all sound input devices - I still got a 124 error - twice last night.

I haven't yet done the CMOS reset yet mainly because my case is a Silverstone HTPC one and the CMOS jumper is under the dvd drive which means I have to remove a lot of cables and remove the drive to get to it.

I've not given up the hope that my PSU is vastly underpowered for the amount of things I have in the box (Dual core processor, 3 hard drives, power hungry GPU, Blu ray drive, Soundcard, 2 TV Tuners, front VFD and 4 case fans). It should arrive today so when I get home from work, I shall install it and while I have things apart I shall also perform the CMOS reset.

I also have given a thought towards something overheating - sound card very close to the graphics card and it's massive passive cooler - and while the CPU temps at about 40 degrees, when I opened the case, it is fairly warm in there (esp around the graphics card)

Fingers crossed it gets better after the new PSU/CMOS reset.

Next on the list will be to add a couple more case fans.

Maybe SP1 and it's promise of better reliability will help the problem!

Saturday, January 05, 2008 10:02 PM

I can tell everyone that until today I never had a BSOD with 0x00000124...that's when I added a wireless DWA552 DLINK nic card to my system. I also swapped out my router to a wireless DIR-555 DLINK but I know it is not the router because when I am hard wired to the wireless router no problems. I have an AUS A8N-SLI with nforce onboard NIC. The machine kept locking up (no BSOD) until I disabled the onboard nforce NIC. After I did that, the BSOD started...but only when I went to access the internet.

I talked with DLINK and they had me try another PCI slot. Same thing. They think the card is defective but after reading all this maybe it is the combination of the nforce and wireless. I have the latest nfroce drivers and the latest dlink driver so I am stuck. Sending card back to get replacement but I am sure the same thing will happen with the new card.

Oh yeah I am running VISTA 32 bit Ultimate. When I removed the wireless NIC all the problems went away...

EDIT: Tried wireless NIC in another PC running XP and it works fine so as I suspected it is not a hardware problem with the wireless NIC. Called DLINK back and they say I have a hardware issue. I said how about fixing your driver and they cant help at all. They are worthless. They offered no help in troubleshooting why their NIC blue screens Vista.

Monday, January 07, 2008 11:47 AM

That's interesting as I am also using the nForce onboard NIC. The problem doesn't specifically rear it's head when accessing the network but it's maybe another thing to look at.

My new PSU still hasn't arrived so I still don't know if this is simply an issue with stability on my machine caused by a lack of power.

There seems to be a large amount of people getting this error with many different set ups. The common theme, though, seems to be nVidia, be it graphics cards or nForce-based motherboards.

Out of interest, are you running the latest nForce drivers from nvidia?

I'm running the internation version (UK) of the drivers and have been advised to try again with the US version - not sure what the real difference is!

Tonight I think i'm going to strip down all the drivers and reiinstall using the US versions. I have also been advised to go into the device manager and update the NIC drivers there manually.

Monday, January 07, 2008 12:47 PM

Well I'm sad to report that I got the 124 BSOD again. I've restarted the system; and it's been running without incident again for the last three days. Based on mcjimbob's input and given some other posts regarding heat and power, I'm beginning to question if I may not be actually seeing power related issues either. I looked at power supplies at newegg to get an idea of cost; and came upon power supplies that were "nVidia SLI-Ready certified." Not sure exactly what that entails; but if there are special considerations here, it would be nice to know. Here's a link to the nVidia website that provides a list of certified products http://www.slizone.com/object/slizone_ecosystem.html#certified_powersupplies. Also note that I'm not running dual graphic cards either. I also came across an application awhile back that discusses power requirements for certain configurations. Sorry, but can't recall where I found that at. I know it said that the power supply was close. As I recall, it said I would need a 485 watt PSU; and I currently have a 500 watt PSU. There are certainly factors that effect power consumption including heat; and perhaps with the right circumstances it will could cause this. One reason I have pause is because this error typically happens when the system is idle. I built this system from the ground up; and beefed up it's cooling system. My heat runs typically around 85 - 90 degrees F. That should be more than adequate in that department.

I'm looking forward to hearing from mcjimbob and the results he gets from the new power supply. Given the randomness of this problem, I suspect it will be months before we will know for certain the problem has totally gone away. So I'm probably going to go ahead and make the investment in the power supply; and not wait that long.

Let us know how things go for you mcjimbob. I will certainly do the same.

Monday, January 07, 2008 10:50 PM

I am running the .992 drivers.

Tuesday, January 08, 2008 11:06 AM

Hi again,

Still nothing of any interest to report. I got the 124 error last night again when I was watching TV (watching one channel, recording another).

Still seems quite random. I haven't yet done anything with the drivers etc but the good news is I received my new power supply today so tonight, i'll get that installed and we'll see if we get a difference!

Wednesday, January 09, 2008 10:20 AM

Just an update....

Last night I installed the new power supply and so far, so good. No crashes! It's the first time since I have been using it that it has stayed on overnight and completed all scheduled recordings!

I'm not going to say it's totally fixed just incase but it certainly has improved the stability!

Thursday, January 10, 2008 1:06 PM

I'm having a dimension 9200 from Dell. Bought august 2007

Specifications:

Quad core E6600 intel processor 2,4ghz

8800GTX 768 mb

2gb ram

2x hard disk sata2 320gb

vista home premium 32bit

psu 375w

For more than 4 months i'm busy to get my system running wel. I'm still having blue screen 0x00000124

What I did:

bios update latest (no improvement)

latest nvidia drivers (no improvement)

What dell did:

Replace mainbord

Replace Ram

Replace cpu

replace nvidia 8800 gtx

It all didn't fix the problem

You all think he the psu is to low. But it isn't. I bougth my pc at the same time as a friend of mine (together we bought to pc's). He has the same computer (delivered in the same shipment). It's the same configuration! And he has no problem!?!

Since 3 days I installed xp prof sp2. And i'm having no blue screens?! With vista i'm continuesly/ramdomly having blue screens.

Does someone has a suggestion!

thanks marcel

Saturday, January 12, 2008 9:01 AM

Same problem !
CAn I replace the PSU in my Vostro 1500 laptop ?

Monday, January 14, 2008 2:26 PM

I doubt very much you would be having PSU issues with your laptop and it's not something you'd really want to be messing around with.

OK, so i've been running a few days with my new PSU and I can inform you all that, at least in my case, it is NOT the PSU causing the problem.

I'm still getting the errors, although it was better after I upgraded the PSU. I updated to the most recent release of the US version of the nVidia drivers and, BAM, i'm getting them more frequently than ever!

I've been on a few different forums, pulling my hair out over this one.

I've come across many solutions, the underlying problem seems to be nVidia drivers. Solutions including...

- Hard CMOS reset (as above)

- Disable C1E (Only for intels)

- Disable onBoard Sound

- PSU/Overheating Issues

- Enable 32-bit Disk Access in BIOS*

*This is something that gives me a bit of hope. I haven't tried it yet and there were a good few people on forums who have fixed the error with this solution. I will try tonight and get back again.

Tuesday, January 15, 2008 1:11 PM

OK, more info.

Can anyone tell me if they have been having this problem in Vista, with nForce, the drivers they have been using.

More specifically, can you inform me if Windows confirms you have the latest version of the nForce SATA driver.

I ran Windows Update last night and there was an optional update for this driver. I installed it last night and the computer is still running now (that doesn't really mean anything though). Just a thought

Tuesday, January 22, 2008 12:48 PM

CCode: 124

BCP1: 00000000

BCP2: 85E80B38

BCP3: B2000000

BCP4: 00060151

OS Version: 6_0_6000

Service Pack: 0_0

Product: 256_1

Thursday, February 07, 2008 1:27 PM

Hi again.

Well, i found a fix for my machine.

I updated the BIOS. It obviously cleared the CMOS, DMI table etc at the same time though so i'm not entirely sure if it was implicitly the BIOS update or the refresh that did it!

Interestinly, what happened that was that upon reboot, Vista found a new hardward device - something like the PCI-to-PCI Bridge and installed the drivers for this. Since then, the machine has been running fine. I've watched whole moveis, listened to whole albums with visualisations without a glitch.

I've also been able to quieten the case/cpu fans down since I know it's not an overheating issue.

Obviously things may be different for others but I have found success!

Friday, February 08, 2008 8:06 AM

You only updated the BiOs ?

Friday, February 08, 2008 5:05 PM

>You only updated the BiOs ?

Well, that's what I did to get it working. I don't actually think it was the BIOS update that fixed it more than it was the reset of the DMI tables which somehow caused Vista to find the PCI-PCI bridge. According to the Gigabyte website, all the BIOS update was supposed to do this...

"BIOS can disable onboard graphic when Nvidia 7950 GX2 is installed and CMOS Setup item "Onboard GPU" is [Enable If No Ext PEG]."

Which I don't think is anything to do with the STOP 124.

I think the CMOS reset that was mentioned a few posts back is certainly worth doing.

My knowledge of debugging such kernal errors is limited but what I have found out is that the STOP 124 error is triggered by the error reporting part of your CPU. In my case, I think the CPU was trying to use that forementioned PCI-PCI bridge and because Vista had no driver for it, it caused a problem. I have heard that faulty CPUs can be the cause as well but it really can be a whole variety of things that cause it so i'm not going to say it's a fix for you but it certainly seems to have worked for me.

Monday, February 11, 2008 4:08 AM

My Dell Vostro 1500 have no BIOS update from dell Sad

Monday, February 11, 2008 4:09 AM

My Dell Vostro 1500 have no BIOS update from dell Sad

Can you please upload the screenshot of the "Device Manager" . I will try to install the new driver . thanks

Monday, April 28, 2008 4:47 AM

I also had lots of BSoDs (STOP 0x00000124). And since many people reported that it was something to do with sound issues...what helped for me was uninstalling Host OpenAl. Haven't had crash ever since. I have onboard sound and the driver I'm using is RealTek AC'97 Audio. Hope this helps to some BSoD issues.

Friday, February 06, 2009 3:12 PM

I thought I could put my name down on this list... Error 124 coming up completely at random whenever any sound from any program is present.

I have tried several of the suggestions people have came up with through these 8 pages without any luck.
Updated drivers, BIOS...I even installed Vista and running dualboot to try to sort it out - nothing.

-XFX 8800 Ultra GPU
-Creative X-Fi Fatal1ty soundcard
-Intel QX9650 CPU
-Asus Maximus Formula X38 chipset motherboard
-WD Raptor as XP drive, WD GP 1TB as Vista drive

-PC P&C Turbo-Cool 1200W PSU

OS: Windows XP 32-bit & Windows Vista Ultimate 64-bit

The bluescreens first started to show when I installed Vista, in XP the computer just reboots without error (automatic restart is disabled in both OSs).
Here is one:
http://img80.imageshack.us/img80/6146/img1479hj9.jpg

What's troublesome is the fact that the computer worked fine in more than a month before it started to reboot randomly - and quickly more and more frequent.
And it was the same thing after installing Vista - worked fine for a several hours, then it started to bluescreen - and again, more and more frequent.

What are the facts, if any, in this problem we all share? Is it confirmed it is "simply" a driver problem, only present when the computer consists of specific components?

One thing: will this error-problem go away guaranteed, if I throw away my 8800 Ultra, and put in an Ati card in its place? Or upgrade to, say, an GTX 285 or GTX 295 card?

Monday, February 09, 2009 12:22 AM

My brother encountered this error using a Geforce 9800 GX2, and I read through all the replies here and basically concluded that it was somehow a conflict between drivers for the motherboard and the video card. We tried just about everything suggested here (short of the bios jumping thing) and none of them worked. We discovered in some obscure forum somewhere that the conflicts arose since the November 2008 drivers for the card. After deleting all his current drivers and installing older versions of them (7.15.11.7824) I would look up the driver number - but that's the version number. October 7th, 2008 is when it was posted. And this solved our problems and everything worked great. So if everything else fails, roll back to an earlier driver

Tuesday, February 10, 2009 8:45 PM

I don't think (at least in my case) this is related to sound...in Vista I have disabled my soundcard in Device Manager, disabled ALL Windows sound, and disabled all
sounds in the games I play the most (the games I have been using only for test purposes recently, due to this problem).

And Vista still bluescreens very, very often. I was at a local LAN-party this weekend, and I had so much trouble with it...and when I got home again, and started the PC again,
I couldn't get into Vista at all: it bluescreened instantly when the login-screen was supposed to show.

XP works...sort of, until now, so I though I should try it first with the "older driver advice"...and indeed it works so far.
Opted for the 178.13 driver, and I am testing as I am writing this: all disabled sound and sound devices are now reenabled, so we'll se how this is going later on.

I do damn hope this is the solution...my Intel QX9650 costed me the equivelent of a $1000, and my GPU cost around $855 (if 1USD = 7NOK) when I bought it back in
november 2007, and frankly I don't want to either switch back to AMD or replace/upgrade my 8800 Ultra.
A small off-topic here, but does AMD have anything remotely as powerful as this:
http://www.newegg.com/Product/Product.aspx?Item=N82E16819115034
?

So Chiaco, if this works, you sure have my thanks! You have it anyway, as this is, I think, one of the few things left I haven't done or is cabable of doing on my own. :)

Edit:
40 minutes up in XP (32-bit) on old drivers so far - no problems! :D
Will install the same drivers in Vista (64-bit)...if I get there.

Edit:
I would say this works excellent! :D
Yesterday I played Crysis, watched a movie and listened to music...all the stuff I couldn't do until the older driver was installed.
I left the PC on during the night, just to see if it eventually would reboot...but it didn't! :D

So great thanks to Chiaco for delivering the solution to me (and hopefully several others too)! :D

Edit:
No, the problem is NOT solved...the older driver worked a few days, but last night it started to act up again: XP restarting at random (though not as "violently" as before), and I can't even get into Vista as it crashes instantly (stop 124) when the login screen is supposed to show, both in Normal and Safe mode.
I have tried nVidia driver 181.20, 180.48, 178.24, 178.13 and 175,19...none works, and i have also installed the microcode patch mentioned here:
http://www.microsoft.com/downloads/details.aspx?familyid=2690495F-C21E-45BC-AE0F-5452B75283D0&displaylang=en

No luck.

Friday, May 01, 2009 3:27 PM

I have spent 6 weeks every night trying to fix this problem. I even remember the bsod code by heart.

124 bsod.not audio drivers or bios or any of that bs. Sp1, Sp2, stability patch, nvidia sata drivers, NOTHING! its all bs. you guys dont know what you are on about.

all you have to do is this.

I am posting this becuase I spent 6 weeks without sleep.

vista 32 bit.

START|CONTROL PANEL|DEVICE MANAGER|SYSTEM DEVICES|

now you have to test and see if it works for your system (mine is a 680i ____)

disable at least 2 PCI standard PCI-to-PCI Bridge. test it. its a fault with our memory (RAM and VRAM) they are being dumb stealing each others IRQ.
8800GTX's have the paris hilton dumb disease. Taking resources without asking causing a mess!

nps.

Hong Tran

XPS 720 Quad 2.40ghz
6gb Ram, 8800GTX, Vista 32bit.
680i nvidia Foxconn board.

Friday, May 01, 2009 5:47 PM

I have actually got my system working...and it was, as you say k3ymaker, not a software issue - but in my case it was a rather special hardware issue...
I have 2 PSUs in my box (one of which is used only to power my Delta case-fans) connected to each other with this:
So both PSUs would shut down when turning the computer off.[/i]

[img]http://www.microplex.no/img/cache/kabel_for_tilkobling_av_stroemforsyning_2_-1855880228_0.jpg[/img]

I discovered that when I shut the fan-PSU off while the PC was running nothing happened, but when I turned it back on again after a few seconds, the PC froze instantly.
So I removed the Y-cable and let the fan-PSU run separately using one of these:

[img]http://www.microplex.no/img/cache/startkontakt_for_stroemforsyning_-1359162907_0.jpg[/img]

But the PC still froze when turning the fan-PSU off and on again...it turned out that the cause, and I have no idea why, was some of the fans separate
RPM-connector, which I had plugged into the motherboard for an RPM-readout (as I keep the Deltas under control using manual rheostats).
I had two of them connected, one in an "opt_fan" slot and one in the 4-pin CPU-fan slot (was probably this one to blame), but when I removed both these
fan-RPM-connectors, the system was and is completely stable. Checked again by turning the fan-PSU off and on while the PC was running: nothing.
Just did a "long-run" with my PC: 45 days uptime without any trouble.

So while I'm glad I found the cause for my system, I'm sorry my solution probably won't help anyone else.
Unless some of you have a fan connected to the motherboard: try to remove the connector and the let the fan run directly off the PSU. Maybe it can help...

Tuesday, July 28, 2009 9:02 AM

Hello, i get bsod all the *** time, it started a 2 months ago with 1 bsod every week. and as the time went i got it more recently. now i cant get longer than the log in screen or loading screen before it bsods.
its alwayd the same which is 0x000000124 and 0x00000009C.

I've runned memtest86 for each memroy stick and it was no error. this is making me very frustrated!!
i have also tried a lot of the thinks here, like reset cmod and stuff. but i cant disable cache, shadowering or C1E ( doesent find it in my bios, F4 has no effect)

Windows vista home premium

Tagan TG780-U33II 780W SuperRock (640 before)

RAM: Corsair TWIN2X PC8500 DDR2 4GB KIT CL7 1066Mhz (800 Mhz before)

Hdd's : 2x Seagate Barracuda 7200.11 1,5TB, 1x Seagate Barracuda 7200.10 500GB SATA2

Sound system : Creative Gigaworks Pro Gamer G500 THX

Sound card: Creative X-Fi SB Gamer, bulk

Mainboard: MSI P35 NEO-F, P35, Socket-775, DDR2,

DVD: Samsung DVD-brenner SH-S202J/BEBN

Screen: Samsung 22" LCD Syncmaster 226BW TCO99

Processor: Intel Core 2 Duo E6750 2.67GHz 1333Mhz

Videocard: PowerColor Radeon HD 4870 1GB (Nvidia 8800 GTS before)

Tuesday, October 13, 2009 4:27 PM

Welcome to the pain train -- all aboard. I have seen literally hundreds of posts around the net' with folks using 8800 class Nvidia cards and the Intel D975XBX2 mobo's struggling with BSOD's reporting STOP 0x00000124 (Bugcheck 124) errors. I strongly believe we all have similar problems in that with any audio device + configurations similar to what is listed below we end up with BSOD's either immediately after boot or within certain games and programs in a seemingly random pattern. Most of my bugchecks are occuring with AudioSG.exe which is the surrogate process for 3rd party audio drivers within Windows Vista. With audio disabled my experience within Vista is solid. Read that no BSOD's. I have found that with the Audigy it's minutes to repro a BSOD and with the onboard Sigmatel it takes longer. I want to start this thread as a list of what folks have tried -- please omit "me too" posts. We all feel your pain but let's get a good list of what folks have tried to get going. Please only folks with 8800 class cards since we have a seperate Forceware driver set.

What I have tried to no avail resulting in 0x00000124 BSOD's

- Latest drivers across the board. Feb 20 (WHQL) and March 1 (Beta) NVidia drivers

- Stock only drivers - that is what came on the Vista DVD.

- Increasing the voltage for my CPU, MCH, and Memory slightly

- Running Memory at 667Mhz. Testing memory with Vista. Running with 2GB only.

- Running w/o Intel Matrix RAID

- Similar to others I have no BSOD's within Windows XP SP2.

My Configuration:

Intel D975XBX2 "Bad Axe 2"

Bios BX97520J.86A.2663.2007.0305.1750

Core Duo E6600 (2x2.4Ghz 4MB L2) Stepping 6

2×1GB A-DATA DDR2800 1.8V

2x512MB A-DATA DDR2800 1.8V

EVGA 8800GTS 640MB ACS3 Edition

3 x 250GB WD Sata2 with Intel Matrix Raid 5 - Boot Volume

1 x 250GB WD Standalone - XP SP2 Volume

Onboard Sigmatel 92xx

Creative Soundblaster Audigy 2ZS

Windows Vista Ultimate 32 bit

I have had the same problem but with a different video card then you. I have disabled Windows Media Player Sharing Service under Services and I haven't seen no BSOD's ever since. Have tried it on Vista x64 and Windows 7 x64 as well. You should at least give it a try.

Tuesday, March 15, 2011 7:38 AM

I know this is an old thread, but it seems to me like a sure fire answer has never really been settled on. Unfortunately I'm not re-opening the thread because I have an answer. Instead, I wanted to offer something of an update:

I've been having trouble with a crashing system for some time now. I get most all the same error codes as have been talked about here. Here's my system and set up - mind you I just finished building this machine myself and it was my first time --

-- Windows Vista x64 bit (SP2)

-- AMD Phenom II x4 955 Black Edition 125w

-- GeForce 450 w/CUDA technology Video Card

-- Biostar Motherboard with AMD chipset x4 RAM slots.

-- Western Digital hard drive 500GB and 600W Power Supply

The crashes appear to be random. I've experienced them at no given time. Sometimes the crash occurs barely seconds after logging in, some times it doesn't happen for a couple days. I use my computer for high end video editing, but the system has never crashed while using my Adobe CS4 programs.

More recently, my system crashed and I recieved NO error code, just a blue screen and a message stating that Windows had to shut down in order to prevent damage to my system. I get MEMORY_MANAGEMENT errors and a couple other random errors as well.

According to some sources I've found on the internet, it is believed that the problem actually IS a memory problem. My computer even tried to tell me that it thought I had a problem with my RAM and to run the memory test. I ran the memory and it turned out negative for problems... but apparantely that doesn't matter. In most cases people I've found said it was a defective memory stick and once they replaced the stick everything was fine. However, it never really seemed like that was quick fix everyone was looking for as the thread continued with even more complaints.

I'm going to try replacing my RAM to see if that fixes the issue. I hope it's not a compatibility problem with my Video Card. I need that card for when I get my update to CS5. Please. There has to be a definitive answer out there somewhere. Please help me!!

Tuesday, March 15, 2011 7:44 AM

Just really quick, I figured I should also mention that, other than the hardware itself, everything else was already installed on the hard drive. It was one I took from my old Dell computer and transfered over to the new one. I didn't bother re-installing the programs or Vista (i also read in numerous forums that re-installing Vista doesn't help the problem anyway).

I would also like to point out that my system was crashing even in Safe Mode. All my drivers and my BIOS are up to date. Also, Windows was giving me strange messages during safe mode about my copy of Windows suddenly not being "genuine" and that I needed to activate it. Also, Windows Update couldn't download a recent update for some reason and it just happened that the update was titles in big bold letters as having something to do with NVIDIA GeForce 450. Hopefully I'll be able to download the update as it may also have something to do with the Video Card.

D975XBX2 + Nvidia 8800 Series + Any sound + Vista32 = BSOD (STOP 0x00000124)

All Replies

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support by product

Other support links

Not an IT pro?