Solved BSOD STOP: 0x00000124 Randomly on 2mins tops if even that

[thugishangel]

Hello

"BSOD STOP: 0x00000124 Randomly on 2mins tops if even that"
With that said

Here is how it all started, i was watching TV last night and had the computer on idle next to me. It suddenly rebooted and i was like wth? then at windows start up it BSOD:ed me the 0x0..124
and now it won't stop, can't find the reason it doesn't matter if i press repair, start from last known ... neither can i hold it on for longer then 1-2mins "if im lucky" before it goes BSOD.

I can enter bios without any problems i've even kept bios running for 5-10mins without and changes as soon as i enter windows in any form "even safe modes" it BS:s on me.
I've tried to drop down the auto clock even setting it all to power saving still BS on me.
I have checked all the tempetures and nothing seem to be overheating ?

When i got the chance i copy all the dump files in the folder minidump and they can be found here http://sdrv.ms/Mfp2aL

I'll sshot the BSOD and upload it too in few mins
Any help would be helpful

I'm sorry for my bad english i hope it is understandable.

Thanks in advance

 

[writhziden]

BSOD Posting Instructions

We really could use the full crash reports if you can get them through http://www.sevenforums.com/tutorials/69585-safe-mode.html :

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html​

Analysis:

Some of your older crashes point to the Marvell controller drivers. Try removing the software through Start Menu -> Control Panel -> Uninstall a program if possible. http://www.sevenforums.com/tutorials/117840-uninstall-remove-software-safe-mode.html may also help.​

 

[thugishangel]

Here is a picture and i'm atm loading up video to youtube so you will see the whole process.

 

[thugishangel]

BSOD Posting Instructions

We really could use the full crash reports if you can get them through http://www.sevenforums.com/tutorials/69585-safe-mode.html :

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html
​

Analysis:

Some of your older crashes point to the Marvell controller drivers. Try removing the software through Start Menu -> Control Panel -> Uninstall a program if possible. http://www.sevenforums.com/tutorials/117840-uninstall-remove-software-safe-mode.html may also help.
​

There was 2 marvell drivers.. got the chance to remove one .. but dídnt get the chance to remove the second.. and now it BS on as soon as log in "even safe mode"
Gonna try wait few mins and try again.
And full report seem not possible for me since it BS pretty quick as you see here on the first part of the video and that goes for all safe mode with and without network

 

[writhziden]

BugCheck 0x124:

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html
​

System Restore:

Since this just started happening, I would suggest trying a system restore to before it started. Do the following steps:

• Read carefully through http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html...
• Use the System Repair Disc to access the System Recovery Options...
• Use the http://www.sevenforums.com/tutorials/668-system-recovery-options.html to choose System Restore...
• Follow OPTION TWO of http://www.sevenforums.com/tutorials/700-system-restore.html and pay close attention to the NOTE: in OPTION ONE step 8.

 

[thugishangel]

BugCheck 0x124:

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html
​

System Restore:

Since this just started happening, I would suggest trying a system restore to before it started. Do the following steps:

• Read carefully through http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html...
• Use the System Repair Disc to access the System Recovery Options...
• Use the http://www.sevenforums.com/tutorials/668-system-recovery-options.html to choose System Restore...
• Follow OPTION TWO of http://www.sevenforums.com/tutorials/700-system-restore.html and pay close attention to the NOTE: in OPTION ONE step 8.

I'm going to try this...though i need to get hang of a system repair disc

 

[writhziden]

Read carefully through Create a Windows 7 System Repair Disc — MAXIMUMpcguides – Windows 7 tips, tricks, help, and how-to guides, especially the very end of the article.

 

[thugishangel]

Here is two more videos that shows abit more when error occur





about 5sec after i turn off on the part 3 it bsod again.






How do i know if it is a hardware issue or not... because this seem to happen when i only do something with or in windows 7?
When i check the temps both in bios and in win 7 "when i get in and get the luck to see" the temps are more or less 30C on cpu and i've tryed to have my graph card on full throttle 100% and even without full power on the fans it still is cool. I know on the part 2 video looks like when i turn it of and it bsod but that was just bad timing.

 

[thugishangel]

Without System Repair Disc



Part is without the repair disc, i hope it looks different when i try the same with the repair disc?

** BTW When i look on the minidump files copied to my other computer, it tells me:

 

[writhziden]

Failure to Boot:

Even though you are not having a failure to boot, the steps for http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html may be helpful.​

Hardware Stripdown:

I have a feeling your problems are the result of a damaged Windows install, but you could still see if there is a failed hardware component.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

Strip down your system to run only the bare essentials: one RAM module, the CPU, motherboard, one hard disk, one graphics card (or use onboard graphics if you have it), keyboard, mouse, and one monitor. See how the system behaves by running Windows for twice as long as it typically takes for you to get a crash. If it is stable, add one piece of hardware back at a time until you get crashes again. Take notes of what hardware you add and how the system responds to the hardware changes.

As you add and remove hardware, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.

Once these steps have been followed, it is safe to remove and replace components within your computer.​

 

[thugishangel]

Hi, sorry for the late reply... I've tryed a clean install it didn't work still got bsod so I turned the computer in for troubleshoot the hardware, didn't want to jeopardise the warranties... but I will keep this thread updated until problem is solved, though now I have to wait 10-15 work days for the troubleshoot.

 

[thugishangel]

Failure to Boot:

Even though you are not having a failure to boot, the steps for http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html may be helpful.
​

Hardware Stripdown:

I have a feeling your problems are the result of a damaged Windows install, but you could still see if there is a failed hardware component.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

Strip down your system to run only the bare essentials: one RAM module, the CPU, motherboard, one hard disk, one graphics card (or use onboard graphics if you have it), keyboard, mouse, and one monitor. See how the system behaves by running Windows for twice as long as it typically takes for you to get a crash. If it is stable, add one piece of hardware back at a time until you get crashes again. Take notes of what hardware you add and how the system responds to the hardware changes.


As you add and remove hardware, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.

Once these steps have been followed, it is safe to remove and replace components within your computer.
​

I sent the computer to the technician to check what hardware failure it was...
first he thought it was the motherboard and after few days called me again and said its the SSD too. Few days later called me again said it wasnt the motherboard it was the graphic card and the ssd, then again after few days called me and said it is SSD, Graphic card and processor. And that was the final result, theyve also runned stress test for about 3 hours and no failure.
Gonna check all this my self as soon as ive done a clean installation.
Reason why they had failed is still unknown.