Freezes and BSOD, error 0x00000124

Hello

My HP notebook freezes again and again. It started a few weeks ago. I have used all the BIOS self-diagnosis tools, but all tests are passed. I even did a completely new installation of Windows 7 with (as far as I know) all the newest BIOS and drivers. Since the problem persists, I suspect a hardware problem. Even more because I also got two bluescreens during the past few weeks and they both mention an "uncorrectable hardware error". I thought it would be easy with the code to find out by googling, what they mean. But I found so many different things it rather confused me. Does anybody know what the following bluescreens mean? Do they clearly point to a specific hardware part?
STOP: 0x00000124 (0x0000000000000000, 0xFFFFFA800516F038, 0x00000000B2000040, 0x0000000000000800)
STOP: 0x00000124 (0x0000000000000000, 0xFFFFFA80051A6038, 0x00000000B2000040, 0x0000000000000800)
If not: What can I do next?

Oh, comes to my mind: It seems that Windows does not freeze as long as I play a video with VLC player. Strange. But of course I am not sure, it is just my impression.

System:
Windows 7 Pro x64
Re-installed about 3 weeks ago; full version (download from MSDAA), not update or OEM
Hardware: HP Elitebook 8530w (2+ years old)

Thanks in advance!

Thanks JaidynM, a few of the suggested tests I've already run. I'll run now the others and hope I'll find something. I assume the BSOD messages I quoted and the attached reports didn't give a clear picture in what direction I should look or which hardware parts I should test first. Is that correct?

tripleclick said:

Thanks JaidynM, a few of the suggested tests I've already run. I'll run now the others and hope I'll find something. I assume the BSOD messages I quoted and the attached reports didn't give a clear picture in what direction I should look or which hardware parts I should test first. Is that correct?

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Thank you, zigzag3143. Please excuse my ignorance but I thought the dump files were already included in the attached Windows_NT6_BSOD_jcgriff2.zip above. But you can find the zipped minidump folder now attached to this message.

Is this enough or even too much? I noticed that your instructions suggest a setting of "small memory dump (256 KB)", I had it set to "kernel memory dump" (German "Kernelspeicherabbild"). Is that a problem? Should I change it? (But I guess it would take some time to get another bluescreen, although freezes occur several times a day, which is very annoying.)

Please allow a last question: You suggest to have Automatically restart unchecked, I have it checked. Why unchecked. And what then? I have to reboot and go to work at some point. Can you please clarify?

I am sorry about my questions. They may seem stupid to you. I am just not that computer savvy and am thankful for your support and help.

Ok, thank you, JaidynM. I keep on running the tests. I guess you haven't found anything special in the dumpfiles so far. (And I will switch to "small memory dump".)

tripleclick said:

Ok, thank you, JaidynM. I keep on running the tests. I guess you haven't found anything special in the dumpfiles so far. (And I will switch to "small memory dump".)

One needs to remember

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.

We would love to be able to perform magic...

Ok, I finally got it. Sorry, I did not mean to be disrespectful about what you're doing. Not in any shape or form. I very much appreciate your support and help. I'd be lost without you. Going now back to testing...