BSOD playing WOW, also on initial restart after BSOD

[Fallenangel]

I had a couple BSOD last night, while playing wow.
Updated all my drivers.
Ran Win 7 memory test and hard drive test.
No issues with hard drive.
Win 7 memory test it did indicate some issue with hardware.

I have attached the minidump files and health report.

I just downloaded memtest so i plan on running it tonight over night.

Any help would be greatly appreciated.

 

[JMH]

I had a couple BSOD last night, while playing wow.
Updated all my drivers.
Ran Win 7 memory test and hard drive test.
No issues with hard drive.
Win 7 memory test it did indicate some issue with hardware.

I have attached the minidump files and health report.

I just downloaded memtest so i plan on running it tonight over night.

Any help would be greatly appreciated.

Fallenalngel Hello

These crashes seem to have several causes, most pointing to memory.
You really cannot test memory with the inbuilt memory test because it is working in the environment and doesn't stress the memory enough..
Therefore please run these 3 tests.

1-Memtest.

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.

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.


http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html


2-Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


3-System File Check

Run a system file check to verify and repair your system files.
To do this type cmd in search.
Right click to run as Administrator, then SFC /SCANNOW

Read here for more information
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.

 

[MvdB]

Just to add my two 2ct:

You might be having a devices problem. I expect your Devices screen to say something about this error:

The device driver for Coprocessor has not been installed. This device will not be available until the correct device driver is installed.

And I expect that you can solve it by fully re-installing your Nvidia drivers. That is what is mostly the problem when you get this...

 

[JMH]

Good idea Mark...

Following on from what Mark says.....

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using

Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

 

[Fallenangel]

Memtest found errors during test this morning, currently testing one stick at a time. I will keep you guys posted.

Thanks again for the the help guys/gals I really do appreciate your time.

 

[JMH]

Thanks...
It is a pleasure.
Jan.

 

[Fallenangel]

Good news...

Memtest found my 2nd ram stick to be bad, the first one is good, it ran about 14hrs without a single error. Good thing I have 4GB so i will see if my warranty is still good.

Thanks again for all your help, if any more BSOD appear i will keep you posted.

 

[JMH]

Good luck.

 

[MvdB]

That is good news! Jan was right again! Thx for posting back!

 

[Fallenangel]

Bad news, BSOD came back, just ran 7 cycles of memtest no issues here is my minidump files. I am doing sfc/scannow atm command, will check again to make sure drivers are up to date and try the driver test.

any help would be greatly appreciated.

 

[Fallenangel]

I think my board might be the issue, when i was installing the first set of ram I got, I had one bad stick and one good stick my luck, but when I was testing one at a time the stick wasnt seated correctly.

I think something might have shorted out, after this I could not use the 1st slot, i just decide to go to slots 3 and 4 when I installed the 2nd pair of ram I got.

 

[Fallenangel]

SFC/SCANOW perfomed, no issues found, currently updating mboard driver and vidcard driver

 

[zigzag3143]

SFC/SCANOW perfomed, no issues found, currently updating mboard driver and vidcard driver

FA

I have been following this thread since the beginning and might suggest that you absolutely eliminate one piece of hardware at a time before moving on.

Initially you report memtest errors.
Did you replace the bad stick, did you test each mobo slot with a known good stick, etc.

You are now updating your mobo driver and vid card driver without a definitive answer re RAM and mobo slots.


On another matter we (as you know) need the actual DMP file as it is the only record of the events leading up to the the crash. The text file you uploaded as DMPs wont cut it.

We await your DMP files.


Ken

 

[Fallenangel]

Just to add my two 2ct:

You might be having a devices problem. I expect your Devices screen to say something about this error:

The device driver for Coprocessor has not been installed. This device will not be available until the correct device driver is installed.

And I expect that you can solve it by fully re-installing your Nvidia drivers. That is what is mostly the problem when you get this...

Well just tried fresh installing the motherboard drivers nforce 15.56, when i try to install co processor driver, it causes a BSOD...

nvsmu.sys BSOD everytime...

 

[Fallenangel]

minidump files

 

[Fallenangel]

1st set of ram, checked each stick individually memtest found one to be bad (corsair)
2nd set I bought from newegg, because its taking more than 3 weeks for corsair to sent me replacement, this set found one bad stick also using memtest (kingston)
3rd set was sent to me from newegg, ran 7 full cycles of memtest no errors recorded. Got BSOD within 30min playing WOW.

 

[zigzag3143]

minidump files

The three most recent crashes were Related to nvsmu.sys NVIDIA® nForce(TM) SMU Microcontroller Driver from NVIDIA Corporation. I would re-install the newest available (and just the driver not the control panel) as yours is from march 2010.

I am discounting the drivers from June through September as your machine is no longer configured the same.

 

[zigzag3143]

1st set of ram, checked each stick individually memtest found one to be bad (corsair)
2nd set I bought from newegg, because its taking more than 3 weeks for corsair to sent me replacement, this set found one bad stick also using memtest (kingston)
3rd set was sent to me from newegg, ran 7 full cycles of memtest no errors recorded. Got BSOD within 30min playing WOW.

Did both memory stick that were fail in the same mobo slot?

 

[Fallenangel]

They might have been, thats why i moved the last set into slots 3 and 4 to make sure it wasnt just a bad slot. But one of the sticks even when i put in in slot 3 would not boot the system at all, this was on the 2nd set (kingston).

 

[zigzag3143]

They might have been, thats why i moved the last set into slots 3 and 4 to make sure it wasnt just a bad slot. But one of the sticks even when i put in in slot 3 would not boot the system at all, this was on the 2nd set (kingston).

Sometimes memory is really finicky, requiring matched sticks, bumping the voltage a tic, running it at less than rated speed.

If the first set showed a bad stick, and the second set did I would suspect the mobo but am unsure.