Random BSODs, STOP 0x124

[Yusoex]

Hey guys,

This is my first post on the forums Hope its all in order ...

Problem:

So anyway ... my laptop has spent the last 2 months crashing with BSODs like crazy.
It started out from as little as once a week, but now its up to 6 times daily, and its gettin on my nerves.

I get a random BSOD, saying STOP*** 0x124, dumps memory, and then reboots my laptop (Sometimes it gives me a BSOD while on the Welcome Screen after it reboots).

So Far:

I've tried basically everything, hoping it wouldn't be anything major. Tried formats, cleaning inside of laptop, memory testing and swapping card positions, and also paid €65 for a new HDD, cause my previous HDD failed its test. But unfortunately it wasnt the problem.

And Thus...:

I'm led to believe its either a very nasty driver, or a motherboard fault - i hope not
The kernel dumps mention something about WHEA_UNCORRECTABLE_ERROR and VISTA_DRIVER_FAULT.

Anyways, I've attached the dumps and reports, cause I'm still very green on interpreting them.

Thanks in advance for any help.
Yusoex


My Laptop:

15.6" HP Pavilion DV6-1131ea
AMD Turion X2 Dual Core Mobile RM-75
4GB RAM DDR2 [2 Cards - 2GB Each] (Supports up to 8GB)
ATI Mobility Radeon HD 4500 Series
320GB HDD WDC WD3200BEVT-00A0RT0 ATA Device
​

My OS:

Windows 7 Ultimate x64 OEM
(Approx. 3 yrs, but performed about 3 recent formats due to these BSODs)
​

 

[cluberti]

0x124 bugchecks usually indicate hardware problems (the CPU tells Windows your system had an uncorrectable error in hardware, and Windows bugchecks with a 0x124 and the parameters the CPU passed). In looking at the hardware error, it could be either RAM or CPU:

1: kd> !errrec fffffa8004ef7038
...
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004ef7148
Section       @ fffffa8004ef72d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
[COLOR=red]Error         : ICACHEL1_SNOOP_ERR (Proc 1 Bank 1)[/COLOR]
  Status      : 0xb600000000000181
  Address     : 0x00000000b92b68c0
  Misc.       : 0x0000000000000000

Looks like you're running a pretty typical HP dv6 at stock CPU speeds:

1: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.4, DMIVersion 36, Size=1001]
BiosMajorRelease = 15
BiosMinorRelease = 24
FirmwareMajorRelease = 25
FirmwareMinorRelease = 23
BiosVendor = Hewlett-Packard
BiosVersion = F.18
BiosReleaseDate = 11/10/2009
SystemManufacturer = Hewlett-Packard
SystemProductName = HP Pavilion dv6 Notebook PC
SystemFamily = 103C_5335KV
SystemVersion = Rev 1
SystemSKU = NZ863EA#ABU
BaseBoardManufacturer = Quanta
BaseBoardProduct = 3060
BaseBoardVersion = 19.17
 
1: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2200
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 17 Model 3 Stepping 1
ProcessorNameString = REG_SZ AMD Turion(tm) X2 Dual-Core Mobile RM-75
VendorIdentifier = REG_SZ AuthenticAMD

Unfortunately, you can find many a user who complain about heat and hardware issues in the dv6 laptops running AMD mobile CPUs, even on HP's site:
HP dv6-1160en + overheating - HP Support Forum

As much as I hate to be the bearer of bad news, ICACHEL1_SNOOP_ERR bugchecks tend to be bad CPUs or poor cooling (or the former caused by the latter), as this is indicating that the L1 cache on your CPU did not return data one of the CPU cores requested within a timeout period - almost always indicating a hardware problem, hence the CPU telling Windows to stop due to a hardware issue.

HPs are pretty prone to this, especially ones running AMD CPUs, unfortunately - I'd be contacting HP at this point for RMA / warranty repair.

 

[Yusoex]

Thanks for the quick reply, Cluberti.
I am aware the HP laptops are prone to such heating issues. I will contact HP, and hope that they will be any help.

One quick question, in how many dumps did the ICACHEL1_SNOOP_ERR bugcheck occur ?

 

[cluberti]

All of them, going back to 10/17 (that was the date of the first dump gathered from your system).

 

[Yusoex]

=/ Then, the CPU is definitely the problem, e ? I'll contact my distributor and post back what they tell me.
Thanks for the help Cluberti
Sure hope its a fixable fault, this laptop has great potential ...

 

[Yusoex]

For the time being, is there a way to determine which core is giving me this error, and (if possible) disable it and work only with one core ?

 

[cluberti]

I don't know, as you can't be certain in silicon which is core 0 and which is core 1 once you boot. Also, just because one core is complaining doesn't mean the other one is fine either, so don't just make the assumption only one core is bad.