Getting a BSOD every 2-3 weeks

FireHazard772

Poster Extraordinaire
=(e)=
Joined
Apr 15, 2010
Messages
3,047
The title just about sums it up:

For the past..month, give or take, every 2-3 weeks I've been getting this BSOD. I tried to look up what it was about but haven't really had much help..not to mention I'm only slightly tech-savvy.

Bug-check details from Win7 Action Center 'Reliability History':

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa800671d038, 0x00000000f2000040, 0x0000000000000800). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101113-20358-01.

Any help/ideas on a fix would be appreciated.
 
Take a look in the Win 7 Event Viewer under Critical and see if there are any recent errors.
(control panel/System and Security/admin tools/Event viewer)

some things you can do as well.

Run ChkDisk (my Computer/right click HD/prop/tools/ Run error Chk)

Open up command prompt and run sfc/scannow
(ctrl R/type cmd)

Run a memory test.
(control panel/System and Security/admin tools/WinmemDiag or you could download Memtest86+)


Hope this helps.
 
Last edited:
Event Viewer I'll have to look into if the BSOD ever happens again as the last time I had one was a little while ago.

I ran a memory test around the first or 2nd time I had the BSOD and nothing came up.

Question - what is sfc/scannow? Or what does it do?
 
If I remember correctly it checks all the standard issue drivers to see if they're installed correctly or not corrupted.

More or less. It checks the integrity of some core windows files and if corrupt or missing, replaces them.

but yeah definitely post again if you Bsod in the future.
You might have fixed it without realizing it. ;)
 
More or less. It checks the integrity of some core windows files and if corrupt or missing, replaces them.

but yeah definitely post again if you Bsod in the future.
You might have fixed it without realizing it. ;)

Thank you for the correction. :thumbup:
 
I had a similar problem with my laptop, best advice i can give would be to reinstall the OS as soon as humanly possible. If you don't you may eventually brick your computer. That's what happened to me.

Don't make the same mistake i did by not reinstalling your computer completely
 
Last edited:
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.

What steps have you taken to resolve this issue?
 
First off - a update: When all this first happened, I installed a NVIDIA (my card manu.) program called NVIDIA GeForce, thinking it would be a easier way to apply driver updates..which it somewhat was.

Recently, such as within the past week or so, after installing a very old game via disc - Command and Conquer Generals/Zero Hour, to be specific (Or to be even more specific - Command and Conquer The First Decade, which includes every C&C game except C&C3 Tiberium Wars, Red Alert 3, and so on) - set it to compatibility mode for WinXP SP2 and to Run as Administrator.

EDIT: The Main game - Command and Conquer Generals, ran fine. But with Zero Hour, the expansion to Generals, after playing a couple campaign maps the BSOD would occur again. After the reboot, I try it again, same thing.

Afterwards, I uninstalled GeForce and instead of just letting the campaign continue on to the next map after hitting Continue, tested a different method to continue the campaign maps (via after one map completes, hit Exit at the score screen, go to the Saved game section of Main Menu since it auto-saves after every campaign map completion and load from there) and have yet to experience a BSOD ever since.
--

@Ric - In addition to the above of uninstalling GeForce, since it was ever since I installed it that problems arose:

Awhile prior to uninstalling GeForce:

- Ran a memory test (as mentioned in one of my earlier posts)

- If I recall correctly, I also ran a sfc/scannow or something similar in command prompt (I had researched the 0x124 code prior to Kitetsu suggesting 'sfc/scannow' and found a answer from a MS-tech suggesting a command-prompt command)

Both of which didn't show anything wrong.
---

@xitreon: May I ask what exactly you mean by 'brick your computer'? o_O
 
Last edited:
Doing a OS re install every 6 month-1yr is a good idea for preventive maintenance.

But if your not having Bsods anymore than I wouldn't worry about it.
 
I had a GForce issue not long ago.... it decided to dl and install a Game Ready Driver instead of the Video Driver.... forced me to do a complete fresh install of Win 7 64bit. Always make sure Video Driver updates are just that and not the Game Ready add-ons.
 
Well, might as well post this in case someone else may be having similar issues.

After having uninstalled NVIDIA GeForce as I mentioned in a previous post, I have yet to see a BSOD a month after having deleted it.

Thanks for the support!
 

Latest posts

Back
Top