Improve company productivity with a Business Account.Sign Up

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1055
  • Last Modified:

Blue Screen on Windows 7 Ultimate

Hi All,

After installing Windows 7 Ultimate on my HP Pavilion 9700 laptop, I noticed my system has started blue screening for no apparent reason. Below is the error I get after restarting windows.

Fault bucket 0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV, type 0
Event Name: Blue Screen
Cab Id: 0

Problem signature:

Attached files:

These files may be available here:

Analysis symbol: 0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV
Rechecking for solution: 0
Report Id: 112710-21590-01
Report Status: 0

Matt 112710-21590-01.dmp
  • 2
2 Solutions
Try updating the BIOS and other systme drivers and firmware.
You can also take a look at this website and see if it helps
For 50 points, I'm not going to put in much work on this but an anlysis of your MiniDump shows a hardware fault and an MCi_STATUS value of zero.

Here is a write up of the error by an Australian poster called H2SO4 on another forum

"A stop 0x124 is fundamentally different from other types of bluescreens because the "we must crash now" trigger is the hardware, not software. The OS passes on the hardware error report as a "stop 0x124" because it can't do anything else once the hardware has signalled an uncorrectable error condition. It's theoretically possible for drivers to indirectly cause hardware to trigger MCEs by "driving" in ways that are confusing to the hardware, but from the point of view of a home user that disctinction is so subtle as to be irrelevant.

It's important to note that there are literally squillions of different possible causes for that hardware error report (it's called a "Machine Check Exception" - MCE), and one person's stop 0x124 is likely to be entirely different to another's. Hence, posts which begin with "I had that error too, and then I reconnected the mini-molex on my FDD to fix it..." are almost always misguided because they're random stabs in the dark which are statistically highly unlikely to help anyone else experiencing MCEs.

It's relatively simple (but painful) to interpret the hardware's error report. It's in the so-called MCi_Status register, the contents of which are actually visible as bugcheck parameters 3 and 4 in that photo of your screen, as well as each of your minidumps. Interpreting the numbers is just a matter of consulting information published by Intel and AMD. (I've done it below based on your first minidump. This is such a common request that I might code a little utility to automate the process.)

The trouble is that the hardware's complaints are never "practical", in the sense that they would tell you what's wrong in layman's terms and include a recommendation for how to fix it. Instead, it's esoteric stuff which only tends to make sense to hardware folks and driver developers. Hence, a basic "0x124 home user troubleshooting strategy" might look something like this:
0) If it's under warranty, take it back to the shop. The hardware is reporting errors and you don't want to run the risk of troubleshooting it yourself with an uncertain outcome - you just want a machine that doesn't report MCE errors. Otherwise...

1) If overclocking, don't. Hardware that is driven beyond its design specs - by overclocking - can malfunction in weird ways.

2) Open up the side of the case and point a mains fan into the guts of the PC to rule out most (lack of) cooling issues.

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware. This is a desparation step, but it's legit once you're faced with having to rip out and replace bits of the machine, plus it's generally good practice to run the latest drivers anyway.

4) From time to time the OS drivers themselves may be contributing to an MCE. The scenarios are very specific and very rare, but try applying the relevant updates anyway. For example:

5) Clean and de-dust the inside of the machine. Reseat all connectors and memory modules. Use a can of compressed air to clean out the RAM DIMM connectors as much as possible.

6) If all else fails, start ripping out bits of hardware one-by-one until a culprit is found. Obviously, this is a lot easier if you've got equivalent hardware lying around to perform swaps.

The fact that your MCi_STATUS is zero is not a good sign because it means that the hardware has caused a crash but could find nothing wrong.  I hate faults like that but the principle of stripping the machine to bar minimum is a good one.  Remove anything you can do without including half the memory.
mlong219Author Commented:
They both had great feed back for me to look into to help resolve the issue.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now