BSOD Cold Boot 0x000000124

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

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

Some generic advice.

If you are overclocking STOP. Return to the default settings at least for now.
If you are running a RAID update its driver.


You can read more on this error and what to try here... Stop 0x124 - what it means and what to try

Thank you for the reply.

I'm not overclocking and I don't use a RAID drive.

Halowar said:

Thank you for the reply.

I'm not overclocking and I don't use a RAID drive.

124's are general hardware complaints. Read the link for what to try/

I've tested all the points :

1 - No overclocking;
2 - My temps are 50 at the max point;
3 -Updated all the drivers;
4 - Last Acer bios 1.23
5 - Updated windows
6 - Ran memtest, chkdsk, furmark
7 - Reinstalled Windows
8 - Cleaned laptop;
9 - Removed only the RAM memory.

I've attached the minidump from this morning.

Can I do something else ?

Thank you in advance,
Alex

Halowar said:

I've tested all the points :

1 - No overclocking;
2 - My temps are 50 at the max point;
3 -Updated all the drivers;
4 - Last Acer bios 1.23
5 - Updated windows
6 - Ran memtest, chkdsk, furmark
7 - Reinstalled Windows
8 - Cleaned laptop;
9 - Removed only the RAM memory.

I've attached the minidump from this morning.

Can I do something else ?

Thank you in advance,
Alex

Was there any lead up to the problem like freezing, or intermittant shut offs?

If it is not under warranty and you feel comfortable you may want to pull all the ram but one stick.

RAM is usually the first thing I check in a 124.

Hello,

The laptop was freezing on cold boot with the wireless led on, still does it when no BSOD.

Tried to disable wireless card and network card, still does it.

As far as the Ram, I even bought a new stick, and no change.

Alex

Halowar said:

Hello again,

I have done 2 tests with intresting results:

1. Clean boot (cold boot) - BSOD 124 with the minidump in post Nr. 5

2. Safe Mode (cold boot) - No BSOD, for the firt time :)

I really don't know what to do now. Can this test help me localize the problem ?

Thanks in advance,
Alex

When you boot into safe mode most drivers arent loaded, ergo no BSOD.


Since it appears to be driver related, please run driver verifier to find which ones are misbehaving.




These crashes were caused by memory corruption/exception (probably a driver).
Please run this test to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.





Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Hello,

Thank you for the response.

I've already ran driver verifier and it gave me a Bsod.
I'm attaching the minidump again.

Is this of help or should I run it again ?

Thank you,
Alex