BSOD - For 1 week now

dirknaruto · 25 Jan 2011

Hello,

Please help me with BSOD. Been occuring since i bought this pc. Minidump included.

Windows 7 is 32bit OEM. Everything is 2 weeks old.

Thanks.

zigzag3143 · 25 Jan 2011

dirknaruto said:

Hello,

Please help me with BSOD. Been occuring since i bought this pc. Minidump included.

Windows 7 is 32bit OEM. Everything is 2 weeks old.

Thanks.

A couple of problems

1-sptd.sys
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

2-Hardware

Most of these were caused by hardware. Please read here and follow the instructions.

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

Thanks

Ken

CarlTR6 · 25 Jan 2011

In addition to Ken's spot on advice, you have some very out of date drivers. Outdated drivers can contribute to a 124 crash. I suggest you completley uninstall LogMeIn.

lmimirr.sys Tue Apr 10 18:32:11 2007 - RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver. https://secure.logmein.com/US/home.aspx.

LMIRfsDriver.sys Mon Jul 14 12:26:22 2008 - RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver. https://secure.logmein.com/US/home.aspx.

RaInfo.sys Fri Jan 04 13:57:12 2008 - LogMeIn/RemotelyAnywhere Kernel Information Provider. RemotelyAnywhere - Remote Access Solutions.

dirknaruto · 25 Jan 2011

Thanks guys... ill try to do it one by one and post back if i encounter it again...

dirknaruto · 26 Jan 2011

Hi again guys.... i did the things relating to daemon tools and logmein but i encountered the problem again...

I read through the stop 124 troubleshoot and did what i can do for my pc....

Could you confirm this, does windows really have a limit on memory that can be plugged on?? I have read earlier somewhere that there is a 4gb limit to windows. But since i have a 4gb(2 x 2gb mem) mem stick and a 1gb video card, i have been qualified to have exceeded this limit. That's why i have this bsod... i have removed 1 of my 2gb stick, and ever since i haven't encountered the blue screen.

I really hope you could confirm this because i wanna return that stick... :)

CarlTR6 · 26 Jan 2011

32 bit Win 7 is limited to 4 GB. Read the first post in this thread for an explanation of 32 bit and 64 bit versions of Windows.

https://www.sevenforums.com/general-d...omparison.html

Your removing one stick of RAM and your BSOD's going away points to a RAM problem: a bad RAM stick, a bad motherboard slot, RAM sticks incompatible, RAM incompatible with the motherboard, RAM timings and /or voltages are not set properly, or a bad memory controller.

I suggest that you test your RAM with Memtest86 following the instructions in this tutorial: RAM - Test with Memtest86+. Run Memtest from a cold boot after your computer has been off for an hour or two. Let it run for a minimum of 7 passes. This will take 4 - 8 hours depending on whether you are testing one or both sticks. I suggest that you start the testing with both sticks in place. If you see errors on your screen you can stop the test. Post back with your results.