System crash

[kronos666]

Hi,

Ive been getting a lot of system crashes on my laptop (asus f3sg) now that i have installed cod4. When i have been playing for about 20 min, there is a noise that is repeated rapidly for about 7 seconds (soundloop), and then my computer reboots - no blue screen, just normal reboot,...but i am given the option to boot up in safe mode or normal mode....

I have been playing it for 2 days now,...and i reformed my computer and installed win7 x64 ult a couple of months ago... Installed call of duty 4 yesterday, and was playing fine untill my comp started re-booting...it has re-booted about 10 times since yesterday.


My troubleshooting:

Installed new drivers for my nVidia 9300m g, nothing changed
Installed the games again, but this time to my primary drive, nothing
Installed Directx again, even though when i ran, the directx diag, it said i had directx 11, - i think that just a w7 factory setting(pre-loaded)

I thought i had to do with skype, because i was talking to my friend at the same time as playing, so i started using xfire instead, that, i thought worked, but only for about 30min..... I believe this has nothing to do with over heating, as when laptops overheat, you get a blue screen...and my computer isnt even that hot...

I played cod4 just fine before i installed a new copy of the OS...

attached dmp files from yesterday and today.

Thanks very much!

 

[richc46]

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. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

 

[kronos666]

great, thanks for the link. Just an update...i did update my bios from asus 305, to 306...it did not change anything.

Also, when i am playing the game, i can now tell when the computer is about to crash. I suddenly starts to run louder.

I have a asus f3sg laptop, dual core, 2.1ghtz. 4gb ram, nVidia 9300m g...
I have cleaned my computer from the inside, and updated the bios, and im going to try some of the other methods in that link that you posted. It says that these types of blue screen crashes are usually due to overclocked systems..

Ill post some updates here once i try some other stuff out. thanks

 

[richc46]

Louder maybe fan
maybe overheating
Look into that

 

[kronos666]

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

Not Overclocked

2) Ensure that the machine is adequately cooled. If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

My laptop is flat on my desk, nothing under it, nothing blocking the fan at the back, i dont have my laptop cooling pad anymore - maybe no enough air being fed through the vents at the bottom of my laptop. So - My laptop maybe overheating

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware. It is good practice to run the latest drivers anyway.

DONE

4) Update the motherboard BIOS according to the manufacturer's instructions. Their website should provide detailed instructions as to the brand and model-specific procedure.

DONE

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug). At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

Done

6) Attempt to (stress) test those hardware components which can be put through their paces artificially. The most obvious examples are the RAM and HDD(s). For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing. For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors". Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

Done - no errors

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc. Should that fail to mitigate the 0x124 problem, jump to the next steps. Otherwise, if you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes. Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.

I might do this later, but, i did do a re-installation 2 months ago, so that shouldn't be a problem.
​

If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events. Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:8) Clean and carefully remove any dust from the inside of the machine. Reseat all connectors and memory modules. Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

Done

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Cant do this (laptop)

 

[wish]

Hi,
Have you tried memtest for at least 7 passes?
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

And update this driver:

AsDsm.sys    Fri Aug 10 05:16:30 2007 --> [URL="http://support.asus.com/download/download.aspx"]Asus Data Security Manager Driver[/URL]

 

[kronos666]

thanks for that, ill give it a go tomorrow,...i also installed those drivers, and yet another crash...

I attached another jpeg file, screen shot, of what pops up when my computer reboots, error report.

 

[kronos666]

Looks like the problem is solved, i re-installed the OS. Thanks for your help anyway! I post updates if anything goes wrong.