BSOD when in FireFox - bugcheck 0x00000124

[paleGreen1]

Hello,

I've done a fair amount of research into this BSOD, 0x00000124, and I've found lots of possible causes of course. And I've satisfied most things on the "Windows 7: Stop 0x124 - what it means and what to try" post so I need your kind help!

I recently wiped my (very stable) Win 7 Ultimate 32-bit system and installed Win 7 Ultimate 64-bit in order to upgrade my memory to 8 GB. The system is a Dell XPS 420 with q6600, GeForce GTX 460 1GB, upgraded 750 watt power supply, all running at stock speeds -- nothing overclocked. To upgrade to 8 GB, I purchased used RAM via ebay, so right away I suspect bad RAM, but I let Windows Memory Diagnostic run in extended mode for a over a day after the first crash, then later a couple days straight with no errors.

It crashed again last night while in FireFox (23.0.1) so tonight I vacuumed out what little dust there was in the system and cleaned the Arctic 5 Silver compound off the CPU and heatsink and reapplied fresh compound. After booting up and running for less than 30 minutes I got the BSOD again.

So next I downloaded the debugger and set up the MS symbol server path and ran the dump but just received this:

BugCheck 124, {0, fffffa800975a028, b2000040, 800}

*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : GenuineIntel

So next I downloaded and ran SF_Diagnostic_Tool and I'm attaching the results.

If anyone can make any sense of this, I would be so thankful!

Also, fwiw, I have an almost identical XPS 420 at work (GTX 650 Ti instead of GTX 460) but it's had 8 GB and Win 7 Pro 64-bit from day one (going on 3 years now) and I've never seen this crash (I can't remember the last time I've seen a BSOD on it). And I've confirmed that all the drivers for things like sound card, storage controller, network adapters, etc. are all exactly the same -- all stock vanilla drivers included with Windows 7.

Thank you so much!

 

[YoYo155]

Hello, please follow the tutorial linked be below and post the results .

• http://www.sevenforums.com/windows-...ne-activation-issue-posting-instructions.html

 

[paleGreen1]

YoYo155: Thank you for your help on this!

Just curious: Do you think the BSOD is related to an activation issue or does this tool just provide you with additional information about the system?

Here's the report:

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-MCFY3-MQY22-MVVW3
Windows Product Key Hash: tWkh7zakdMZMfFhYBooRtcxKf2s=
Windows Product ID: 00426-292-0639111-85083
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {92A5DFEF-B1C9-4984-A0A4-648C1FE2C3ED}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.130708-1532
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{92A5DFEF-B1C9-4984-A0A4-648C1FE2C3ED}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-MVVW3</PKey><PID>00426-292-0639111-85083</PID><PIDType>5</PIDType><SID>S-1-5-21-3355145457-1684406135-3525802487</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Dell XPS420                  </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A07</Version><SMBIOSVersion major="2" minor="5"/><Date>20090225000000.000000+000</Date></BIOS><HWID>AC2A3007018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL  </OEMID><OEMTableID>B9K    </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, Ultimate edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: ac96e1a8-6cc4-4310-a4ff-332ce77fb5b8
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00426-00170-292-063911-00-1033-7600.0000-1952013
Installation ID: 003944588793939426357065264325208576664242858742580941
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: MVVW3
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 9/4/2013 11:12:46 PM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 7:14:2013 04:25
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: LAAAAAEAAAABAAEAAQACAAAAAQABAAEAln1SpNycWqaUxCw2rB2+pKypzDE=

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x0
OEMID and OEMTableID Consistent: yes
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			DELL  		B9K    
  FACP			DELL  		B9K    
  HPET			DELL  		B9K    
  BOOT			DELL  		B9K    
  MCFG			DELL  		B9K    
  SSDT			DELL		st_ex
  DUMY			DELL  		B9K    
  SLIC			DELL  		B9K    
  SSDT			DELL		st_ex
  SSDT			DELL		st_ex
  SSDT			DELL		st_ex
  SSDT			DELL		st_ex
  SSDT			DELL		st_ex

 

[tom982]

YoYo155: Thank you for your help on this!

Just curious: Do you think the BSOD is related to an activation issue or does this tool just provide you with additional information about the system?

Hi paleGreen1,


We tend to ask for MGADiag logs in most threads here, just to check the authenticity of people's licenses before we help. A lot of people ask for help here but have pirated copies of Windows which simply isn't acceptable - why should we bother helping them when they haven't purchased Windows like the rest of them? Rest assured we haven't singled you out for an MGADiag log inspection, most people get the same


Fortunately, there are no issues in your MGADiag log and your Windows 7 Ultimate is a retail license with no problems whatsoever!


It's all good YoYo155, work your magic!


Tom

 

[YoYo155]

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. - H2SO4

The generic nature of the 0x124 (Arg1=0) stop code means we would have to take
the trail & error approach.


Good practice, open up the case and re-seat all types of connection.

• SATA Cables (HDD/SSD/ODD).
• SATA-Power.
• Motherboard 24-pin.
• Motherboard 4/8-pin (CPU).
• Re-seat the RAM.
• Re-seat the GPU.

Make sure that every slot / cable head is free of dust or other obstruction.
Make sure that every connection is seating properly and firmly in-place.

Also have a look at the motherboard and the GPU, search for any "bad caps", bulky, leaking bloated capacitors.

i.e






Test for overheating and stability:

• Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.

Reset the BIOS back to default in case you're unaware that your CPU is overclocked:

• CLR CMOS

   Note

Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80098c9138
Section       @ fffffa80098c92c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=Blue][U][B]BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)[/B][/U][/COLOR]
  Status      : 0xb200004000000800


===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800975a138
Section       @ fffffa800975a2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=Blue][U][B]BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 1 Bank 0)[/B][/U][/COLOR]
  Status      : 0xb200004000000800


===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800940d138
Section       @ fffffa800940d2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=Blue][U][B]BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 3 Bank 0)[/B][/U][/COLOR]
  Status      : 0xb200004000000800

In this example, the error is BUSL0_SRC_ERR_M_NOTIMEOUT_ERR, which means that the L0 cache memory on a processor suffered a generic non-timeout-related error while something was trying to access data in it. The source of the requested operation was the processor itself. This helpfully provides the exact processor number (Proc 0) and memory bank (Bank 0) for multi-core/multi-cpu systems to further diagnose.

To decipher the mnemonics presented in the error message, consult the CPU developer manual associated with the CPU installed in the offending system. For Intel CPUs, it's in Intel 64 and IA-32 Architectures Software Developer's Manual Volume 3: System Programming Guide (for 64-bit of course), and the tables for the mnemonics are located in section 15.9.2 (that's chapter 15, section 9, subsection 2). While Intel and AMD CPUs present their errors differently, typically the mnemonics are the same.

Considering you already replaced the PSU (with a new one?), Tested the RAM, although not using
the recommended method (I don't suspect the RAM at this time), I suspect the CPU whether
it being overheating or the lack of a BIOS update, but most probably a faulty CPU it seems as of now.

No update available for your BIOS.

!sysinfo machineid
Machine ID Information [From Smbios 2.5, DMIVersion 37, Size=2326]
BiosMajorRelease = 0
BiosMinorRelease = 0
BiosVendor = Dell Inc.
BiosVersion = A07
BiosReleaseDate = [COLOR=Red][U][B]02/25/2009[/B][/U][/COLOR]
SystemManufacturer = Dell Inc.
SystemProductName = Dell XPS420                  
BaseBoardManufacturer = Dell Inc.
BaseBoardProduct = 0TP406
BaseBoardVersion =

• Do you have access to a different CPU for testing?

Good places to read more:

• Stop 0x124 - what it means and what to try
• Stop 0x124 Troubleshooting - 'New Method'

 

[paleGreen1]

Thank you YoYo155! I will go through your post in detail this weekend and supply everything you requested. I do have access to several other Q6600 cpus, thanks to having 4 more XPS 420 systems at my office. So I could swap those out, although I don't look forward to having to clean and reapply thermal paste on the cpus. I might have to order more paste. Do you recommend one? I used AS5 years ago.

Also, is there a program that will monitor the temp of my CPU? (CPU-Z says the mainboard is X38-based, with a Q6600 cpu.)

In the meantime, here's more info regarding everything I did to the system while upgrading:

As I said before, I needed to add more memory to the system (I originally had 3 GB) so found some matching memory on ebay from a reputable seller and ordered a set of 4 2GB sticks (the most this XPS 420 system will support). So I swapped out the memory and swapped out the OS (reformatted partitions of 32-bit Win 7 Ultimate and installed 64-bit).

Now after the 64-bit Win 7 install was completed I did one more thing -- but I don't remember if it was before or after the BSODs started. I changed out the system hard drive (swapped a 500 GB Seagate for a 500 GB WD Black). I had a full system backup of the new system on my Windows Home Server, so I swapped the hard drives and restored the partitions on the drive from the WHS backup. After fixing a minor boot issue with the Windows Repair Disc, it seemed to be restored successfully. So theoretically that new drive could also be an issue, but I'm guessing that would be lower on the list of suspects.

Thanks again for your time on this. I'll reseat and inspect all the cables, connections and caps this weekend and run speccy and those benchmarks. I'll also reset the BIOS, although I haven't touched it in years. It's been at A07 for a long time. And the SATA mode is AHCI, although none of the drives are in Intel RAID mode. (I do have two striped in Windows however. That's been that way for a long time too.)

 

[YoYo155]

Thank you YoYo155! I will go through your post in detail this weekend and supply everything you requested. I do have access to several other Q6600 cpus, thanks to having 4 more XPS 420 systems at my office. So I could swap those out, although I don't look forward to having to clean and reapply thermal paste on the cpus. I might have to order more paste. Do you recommend one? I used AS5 years ago.

There is almost no difference between thermal pastes, arctic silver is considered very good.

Also, is there a program that will monitor the temp of my CPU? (CPU-Z says the mainboard is X38-based, with a Q6600 cpu.)

Yes as posted above you can use Speccy.

In the meantime, here's more info regarding everything I did to the system while upgrading:

As I said before, I needed to add more memory to the system (I originally had 3 GB) so found some matching memory on ebay from a reputable seller and ordered a set of 4 2GB sticks (the most this XPS 420 system will support). So I swapped out the memory and swapped out the OS (reformatted partitions of 32-bit Win 7 Ultimate and installed 64-bit).

Now after the 64-bit Win 7 install was completed I did one more thing -- but I don't remember if it was before or after the BSODs started. I changed out the system hard drive (swapped a 500 GB Seagate for a 500 GB WD Black). I had a full system backup of the new system on my Windows Home Server, so I swapped the hard drives and restored the partitions on the drive from the WHS backup. After fixing a minor boot issue with the Windows Repair Disc, it seemed to be restored successfully. So theoretically that new drive could also be an issue, but I'm guessing that would be lower on the list of suspects.

Every hardware component is a suspect in this kind of bugcheck.
If I understand correctly, you are currently using the ebay bought RAM?
Also you didn't perform a clean install of Windows, correct?

 

[paleGreen1]

Yes, I am running with the new (used) RAM. It's Kingston ValueRAM, fwiw.

I *did* do a clean install of Win 7 64-bit. I totally removed all partitions and re-created everything from scratch. However, I did swap the system drive after the clean install, using a backup, as I described before.

I inspected all the caps I could see -- they all look brand new. No bulges, leaks, corrosion, etc.

I re-seated everything except the cpu, which I did the other day, with new thermal paste.

Here is speccy at idle:
View attachment 285196

And here it is after running both prime95 and furmark at the same time for about 30 minutes:
View attachment 285197

I'm going to reset the BIOS next. I'll post back when that's done.

Thank you!

 

[YoYo155]

Hi thanks for the update .
The temperatures look well within the expected range, so that's good.

Keep us up to date as things progress.

 

[paleGreen1]

I reset the BIOS and restored a few of my custom settings. So far so good. I've tried to re-create the BSOD and haven't been able to so far. I guess time will tell if we really fixed it.

Anything I should try to see if it's really resolved?

Thanks!

 

[YoYo155]

I like to say if it in not broken you need not fix it .
Time will tell, as you mentioned.

 

[paleGreen1]

I like to say if it in not broken you need not fix it .
Time will tell, as you mentioned.

I totally agree.

So far so good. As I was reconnecting USB devices, I noticed that my Microsoft Xbox 360 Wireless Receiver for Windows is apparently dead. It doesn't power-up when I plug it in and Windows doesn't do anything (no success or failed device notification). You don't think that could have been the hardware problem, do you? A USB device?

 

[YoYo155]

Hey Thanks for the update .
As for the controller I doubt it was the cause as USB related problem *usually generate a different bugcheck code.

*You have to keep in mind that 0x124 is as generic as it gets.

 

[YoYo155]

Any update?

 

[paleGreen1]

Sorry for the silence. I did have one more BSOD last week (I think) but I didn't have time to troubleshoot because my Windows Home Server is have major issues now too! (When it rains it pours.) So I've shifted my focus to that problem right now. But I've been using my desktop to work on the server and its hard drives, and I've just had the one BSOD last week, so it's definitely behaving better. But I don't think I've seen the last BSOD, unfortunately.

 

[YoYo155]

Thanks for the update .
Those are good news, you can run another instance of the SFDT and it will pick up the bugcheck
so we could take a look at it.