Solved Random BSOD, SF Diagnostic tool zip file attached.

[brook4]

It would be great if some one could continue to help me here.

 

[Arc]

Brook you let me know the latest situation. Upload the latest dumps etc.

I will have a try again.

 

[brook4]

Here is the latest SF Diagnostic dump.

 

[Arc]

You need to check you storage.

1. Reseat the sata and power.
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
4. Update your SSD's firmware.

 

[brook4]

What do you mean by "reseat the sata and power."?
I did the Chkdsk step above. Is there any fallow up to be done with that?
I don't have any cds to burn to. Is there another option for the seatools setp?

 

[Arc]

Unplug those connections from the HDD, and plug those properly again.
You dont have any CDs? OK, buy one. Or make a bootable usb.

 

[brook4]

I think i may have fixed the problem. I downloaded the latest Nvidea drivers for my graphics card and the computer has not blue screened since. Hopefully this is the end of my issues. Thank you to every one for you help.

 

[Arc]

 

[brook4]

Bad news...my computer blues screened just a few minutes ago. *sigh*
Here is the latest SF Diagnostic dump files.
I thank you in advance for your help solving this problem.

Edit: Downloading the driver for my video card obviously helped some how because it's been several days since a blue screen even with a lot of use on the computer. I don't know if that's a place to start or not. Just thought i would offer that much thought.

 

[Arc]

The cause of the crash is, as I am seeing, the display driver.

 lmvm nvlddmkm
start             end                 module name
fffff880`0f408000 fffff880`100f0000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Aug 30 21:20:16 2012 (503F8BB8)
    CheckSum:         00CCA304
    ImageSize:        00CE8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

• Download and install Driver Fusion.
• Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

 

[brook4]

I have done the above steps and the process went without incident. Is there another step to fallow or do i wait and see if this fixed the problem? In the event of another blue screen should i post another SF zip file?
Thank you very much for your help.

 

[brook4]

It just blue screened again...

 

[Arc]

Yes, you need to upload the dump.

 

[brook4]

Here you go.

 

[Arc]

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

Do one thing more ... Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

 

[brook4]

I turned on driver verifier and got a blue screen very soon after. Here is the dump.
When i was turning on verifier and it came to the step where i was to select all drivers not made my Microsoft Corporation that list only had two drivers in it and they were both Microsoft Corporation. There was an option to add drivers and the program wouldn't let me continue without checking at least 1 driver. So i clicked the add button and added the only two drivers that were in the directory it came up with. I checked both those drivers and closed the program.

I will do the ram check tonight.

 

[Arc]

Seeing the dumps, it seems to me that havent enabled it properly. It happens.

Disable it, and enable it again.
Just make it sure that you are following the guide properly: Driver Verifier - Enable and Disable

If still the crsh dumps dont provide any information, memtest will be helpful I thin.

 

[brook4]

I turned driver verifier back on and it set up properly this time. Here is the latest dump.

I did the RAM test. It did 8 passes and ended up with 4842496 errors. I will do the fallowing steps when i have some time. For now we will just have to work with the dump info.

 

[Arc]

I did the RAM test. It did 8 passes and ended up with 4842496 errors.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8002c90df0, 0, fffff8000310b235, 2}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3a2 )

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

Dumps are still not showing any driver , as those are not caused by the drivers we can say now.

Plan to change the RAM.

 

[brook4]

By "change the ram" do you mean buy new ram? Is there any other option?
If i have to buy new ram is there a way to make sure i get something that is compatible? the motherboard i'm using is a Sabertooth Z77.
If i change out the ram will this cause windows to want me to re-install windows? When i changed the motherboard before it made me re-install windows.