Solved BSOD randomly

[lynx876]

Windows 7 Ultimate x64. Original OS, OEM.
Hardware was bought at different times.
- DualCore Intel Core 2 Duo E6600, 2400 MHz (9 x 267) - Roughly 2007.
- Primary HDD, again, roughly 2007
- Secondary HDD 2-3 months ago.
( At the bottom of this post, "My system specs",
Western Digital WD20EARS 2TB Hard Drive SATAII 64MB Cache Is the secondary drive )

Formatted my OS around 5 days ago and reinstalled the basic drivers to see if there were any problems,
but I still managed to get the BSOD.


The BSOD's seem to have started after around a month of having bought my newest HDD.
At first (that I noticed, as I don't play games much anymore) the BSOD's happened when
my system was left unattended and just sat there idle. I was led to belive that it could
have been the HDD trying to sleep, or something similar, if that's possible?
( I never let my HDD's sleep ( Power options ) )

I set my system to show a blank screensaver after 5 minutes and then display the logon screen
upon system wake up. Almost every time I woke the computer up, after a prolonged screensaver,
it would take a while for my screen to turn back on as my system would wait for my newest HDD to start spinning back up.

Even with the above problem, when I try to play a game, which is installed on the drive I also
get a BSOD while the drive is loading/reading/idle.

A friend installed Everest last night so I could run a stress test, I just wanted to see if I could
stress any hardware enough for it to fail and present me with a BSOD, but nothing happened at all.

If anyone could help me with this, I'd be more than greatful!!

 

[lynx876]

Ok, so I just had yet another BSOD. This time I was starting a game to see if I could cause it to crash while playing and never even had to go the extra mile... ahaha.

I took a photo with my phone and have re-zipped the jcgriff2 files.

 

[MvdB]

Hello Lynx876, welcome to SF!

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.

Also, you seem to be using old 2008 VMware drivers. Depending on what you use exactly, there are newer for W7 here: VMware Workstation 7.0

You also have some problems with Windows Update

Please go to your Maintenance Center and check the Windows Update status. Make sure you are up to date, do them one by one manually if needed.
For help or reset see: http://www.sevenforums.com/tutorials/91738-windows-update-reset.html

 

[lynx876]

Thanks for the reply. I've never had any BSOD's (That I know of) as a result of using Daemon Tools.

I had a currupt driver install of my graphics card. Since I fixed that I've had no file related(win32k.sys, other .sys files etc) BSOD's.

Since then, the only BSOD's I've actually gotten have been:
MEMORY_MANAGEMENT
PFN_LIST_CORRUPT

Of which, to my understanding are related to physical RAM issuses/errors?
All the information I found was on internet sites from searching the errors, most of the replys were physical memory related.

 

[MvdB]

It is up to you of course... but sptd.sys is a well known BSOD cause in W7. Plenty of free good alternatives for daemon... And yes, a sptd crash can look like a memory error.

Search the threads here if you wish... all experts will tell you to get rid of daemon first thing. It is bound to give you issues.

 

[lynx876]

Thanks for replying so quick. I'm not disagreeing with you about the SPTD.sys file causing BSOD's. I myself have never had a BSOD since (that I can remember of) Windows 7 came out. And I have always used Daemon Tools, no alternative.

So in all fairness, from my point of view this looks like a memory error to me from what I've read around and read on these forums. But don't think for a second I know more than you, cause I don't! lol!!

I've ordered more RAM anyway, and submitted an RMA request with the company I bought my current RAM from. I'll write back and let you (and others, if they have similar problems) know the results of the new RAM and whether or not I have the BSOD's anymore.

Thanks again for your reply.

 

[MvdB]

You're welcome and I understand your hesitation. The thing is that this is a difficult area of analysis. It is unclear what the combination of factors is that can cause a system that seemed to run ok with Daemon to fail all of a sudden. But the one thing that is clear is the Daemon part/role in this....It is the common factor that needs to be eliminated...

 

[lynx876]

Well, I will be recieving my new RAM on Friday this week, so if I continue to recieve the BSOD's that will be the first port of call, to remove Daemon Tools.

But as I said in the previous post, I rarely(if not at all) have BSOD's. Only since my latest purchase of my newest HDD/RAM have I had these problems. If it turns out, that the RAM wasn't the problem, I'll have to find the source of these BSOD's, hopefully with the help of this site. Also, I'll have 4GB DDR3 (2x2GB sticks) of Corsaid RAM to sell, ahaha.

 

[MvdB]

No problem and good luck! Hope you are right, could well be...

 

[lynx876]

Quite funny what's happened... lol. Since I ordered my new RAM, I haven't had one BSOD!!

So no idea what it could be, cause I was having BSOD's on a very regular basis.Got my new RAM this morning and installed that, still no BSOD.

If I get any more BSOD's, I'll come back and reply to this thread. Thanks a lot for the help either way!

 

[MvdB]

You're welcome and let us know sometime!

 

[lynx876]

Well, I haven't had a single BSOD since I ordered my new RAM. I've had my new RAM in for a week now.

So it must have been the RAM that was the problem. Again, thanks for the help!

 

[MvdB]

Great news! If your happy the thread is solved, please mark it solved?

 

[lynx876]

Yeah, sorry. Forgot about that!