BSOD Cold Boot 0x000000124

[Halowar]

Hello,

Guys, you are my last hope ...
Since I have bought a second hand Acer Aspire 5741G I'm having a problem with it.

Only On cold boot, when the windows logo comes up my laptop freezes or gives me a BSOD 0x000000124.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80029EB028
BCP3: 00000000FE000000
BCP4: 000000000008014A
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\021112-26052-01.dmp
C:\Users\Popa Sorin\AppData\Local\Temp\WER-44819-0.sysdata.xml

I tried the following :
- Updated to latest drivers - graphics, network, bios
- Tested RAM with Memtest86
- Tested all 2 RAM sticks individually
- Reinstalled Windows
- Tested HDD with chkdsk
- Updated Windows
- Ran Sfc /scannow

System

Acer 5741g
CPU Type DualCore Intel Core i5 520M, 2666 MHz
Motherboard Chipset Intel Ibex Peak-M HM55
DIMM1 Samsung M471B5673FH0-CH9 2 GB DDR3-1333 DDR3
DIMM3 Corsair CMSO4GX3M1A1333C9 4 GB DDR3-1333 DDR3
Video Adapter NVIDIA GeForce GT 320M (1024 MB)

Today I've tried something new, ran Driver verifier and it gave me a BSOD.

I have attached both minidumps.

Can you please help me ?

Edit :
I tried the following :
- Ran Furmark for 15 minutes, temperature maxed at 66 deg.

 

[zigzag3143]

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... http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Halowar]

Thank you for the reply.

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

 

[zigzag3143]

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/

 

[Halowar]

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

 

[zigzag3143]

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.

 

[Halowar]

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]

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

 

[zigzag3143]

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.

 

[Halowar]

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

 

[zigzag3143]

AVG can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide

Microsoft Security Essentials - Free Antivirus for Windows


Not driver verifier but Related to mcdbus.sys MagicISO SCSI Host Controller from MagicISO, Inc. I would update to the latest driver (or remove to test)

 

[Halowar]

Hello,

Thank you for the response.

What have I done :

Uninstalled AVG and switched to MSE.
Uninstalled MagicIso.

Updated Windows.

This morning ran a clean and cold boot and got a Bsod, I have attached the minidump.

Thank you for your patience,
Alex

 

[zigzag3143]

Hello,

Thank you for the response.

What have I done :

Uninstalled AVG and switched to MSE.
Uninstalled MagicIso.

Updated Windows.

This morning ran a clean and cold boot and got a Bsod, I have attached the minidump.

Thank you for your patience,
Alex

THis one was corrupt but I was able to tell it is still the 124 BCC. Still indicating a hardware issue. I was hoping to be able to tell more about which piece of hardware but its corrupt.

Have to wait for the next one.

 

[Halowar]

Hello,

I think I've somehow solved it.

In msconfig, the boot tab, advanced, I've selected 2 cores and the amount of RAm that I have and .... no BSOD'd, 2 times in a row.

Until now I've done 2 Clean Boots with no BSOD's.
Tomorow morning I'm loading all the services.

I'll keep you posted.

Thank you,
Alex

 

[zigzag3143]

Hello,

I think I've somehow solved it.

In msconfig, the boot tab, advanced, I've selected 2 cores and the amount of RAm that I have and .... no BSOD'd, 2 times in a row.

Until now I've done 2 Clean Boots with no BSOD's.
Tomorow morning I'm loading all the services.

I'll keep you posted.

Thank you,
Alex

Glad you found it . Let us know if we can help

 

[Halowar]

Hello,

Seems like it worked.
No BSOD's with all the services and startup items loaded.

I know it sounds a bit childish ... but, what have I done ?

Isn't Windows able to do that automaticly ?

Thank you,
Alex

 

[zigzag3143]

Hello,

Seems like it worked.
No BSOD's with all the services and startup items loaded.

I know it sounds a bit childish ... but, what have I done ?

Isn't Windows able to do that automaticly ?

Thank you,
Alex

Windows does do it automatically. In order for it to be changed it usually has to be done manually.

 

[Halowar]

Hello again,

No BSOD with that seting.

But ... now my windows recognizes just one core and 4Gb of Ram memory.
My temp's are a bit odd right now, it idle's at 60 and in games it runs up to 85.

Can you help me ? Again

Thank you,
Alex

 

[writhziden]

Can you upload a photo (http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html) of your msconfig boot tab? Also, upload a photo of the Advanced Options found in that tab.

 

[Halowar]

Hello,

I've attached the files with the boot options.

These days I have tried diffrent settings with some dissapointig results:

Case 1 :
Number of procesors - checked
Cores 4

Maximum memory - checked
6144

Result : BSOD on cold start

Case 2 :
Number of procesors - unchecked

Maximum memory - checked
6144

Result : BSOD on cold start

Case 3 :
Number of procesors - checked
Cores 2

Maximum memory - checked
2048

Result : no BSOD on cold start

Thank you,
Alex