BSOD windows 7 professional x64

[NNKHAN]

Just got my new asus g72gx laptop 4 days ago and decided to run a clean install of windows 7 on it. Clean install was successful and I proceeded to update my video card drivers and download some everyday programs (skype, google chrome, utorrent) when I noticed the windows update button telling me to update with 24 new updates. I clicked install and the updates went through.
Upon restarting my laptop I got an endless cycle of BSODs, at which point I decided to simply reinstall win 7. However, I can't even get to complete an install without a BSOD 0x124 or 0x09c error showing up. I'm pretty sure it's not the hardware since everything was working fine when i restarted the laptop 10 mins before that restart.
I'm at my wits end since I can't even reinstall to clear everything. Safe mode, last known config and recovery disc all result in BSODs.

Help plz

 

[zigzag3143]

Just got my new asus g72gx laptop 4 days ago and decided to run a clean install of windows 7 on it. Clean install was successful and I proceeded to update my video card drivers and download some everyday programs (skype, google chrome, utorrent) when I noticed the windows update button telling me to update with 24 new updates. I clicked install and the updates went through.
Upon restarting my laptop I got an endless cycle of BSODs, at which point I decided to simply reinstall win 7. However, I can't even get to complete an install without a BSOD 0x124 or 0x09c error showing up. I'm pretty sure it's not the hardware since everything was working fine when i restarted the laptop 10 mins before that restart.
I'm at my wits end since I can't even reinstall to clear everything. Safe mode, last known config and recovery disc all result in BSODs.

Help plz

These crashes were caused by several things but they all point to hardware. Please use these instructions to find out what that means and to figure out what to try.



Bugcheck 124 is a hardware error. use these to find out what it means and what to try. These crashes were caused by several things but they all point to hardware. Please use these instructions to find out what that means and to figure out what to try.

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


If you wish to have others 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.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.


Thanks


Ken

 

[NNKHAN]

Thanks for the reply Ken, however I can't get to login to my account to zip the file anyway. Is there any other method by which I can supply a log?

 

[Jonathan_King]

That sounds like hardware, because you cannot get into the repair or installation disc. Ken is right, 124 is a hardware error.

Actually, the dumps will do little more than tell us that it is a hardware error. Let's start some hardware tests now.

For RAM: Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

For CPU: Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

For hard drive: HD Diagnostic

If you are overclocking, stop.

Open the side of the case and aim a fan inside.