BSOD's

[Hendies]

I've only recently been recieving a few BSOD's since installing windows 7 64bit on my more than capable computer.
I think it's the ram that should be in question and I think i'll take it into the shop I bought it from for a quick look over but I just need to make sure what the problem exactly is.

Is Windows 7 . . .
- 64bit
- the original OS was 32bit windows vista, then clean format upgrades to 32bit windows 7 and then again to windows 7 64bit
- the operating system is full retail

- The hardware should be fairly new - the computer was built last year
- I have reinstalled the OS many times because of problems with it, corrupt files, bsods etc not really knowing why they were happening

The zip attached has the system health check and the files the bsod dump collection app has collected

I hope you can help me out

 

[ttran]

Hi and Welcome to SF!!!

There are few things that you can try:
First of all, please remove Eset Nod32 as I can see some stop codes related to that:
How to uninstall or remove ESET Nod32 antivirus totally?
Then install MSE for testing purpose:
http://www.microsoft.com/security_essentials

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

This driver is old:

PxHlpa64 PxHlpa64.sys Tue Dec 11 06:49:01 2007 (475DD06D)

Sonic CD/DVD driver (used by many different CD/DVD programs)
If you don't know what program you use, then
Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.

Then test your 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.

BUGCHECK SUMMARY:

BugCheck 50, {fffff8801896c338, 0, fffff960000c5b4d, 2}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Could not read faulting driver name
Probably caused by : win32k.sys ( win32k+c5b4d )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff80002c42340, fffff8800979e920, 0}

Probably caused by : ntkrnlmp.exe ( nt!soutput_s+f0 )

Followup: MachineOwner
---------
BugCheck FC, {fffff8a00c102e00, e67000006a255963, fffff8800a26b7c0, 2}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42497 )

Followup: MachineOwner
---------
BugCheck 1A, {31, fffffa80061ac810, fffff88000b71000, fffff8a0099038bd}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+6378 )

Followup: MachineOwner
---------

Regard,

Tuan

 

[Hendies]

Hey thanks ever so much for the quick response!
I've uninstalled Nod, installed security essentials, renamed the system file, burnt memtest to a disc and going to boot from it in a second.
I'll leave a reply after it's finished tonight

 

[Hendies]

Right, I stopped just before the 4th pass finished with 20 errors
But they all seem to be picked up in the 7th test, everytime

I took a picture of it if it helps you in any way, it's attached on this post

 

[ttran]

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

 

[Hendies]

Alright, i'll take it back to the shop who made it for me to repair it.
May get a ram upgrade too

Thanks for the help and quick replies
It's much appreciated

 

[zigzag3143]

Alright, i'll take it back to the shop who made it for me to repair it.
May get a ram upgrade too

Thanks for the help and quick replies
It's much appreciated

You can narrow it further if you test one ram stick at a time. when you find one that is good try each mobo slot. that way you can find if it is ram or mobo before you take it in


Good luck and let us know if you need assistance

ken