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.
It just blue screened again...
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.
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.
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.
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.
Dumps are still not showing any driver , as those are not caused by the drivers we can say now.Code:******************************************************************************* * * * 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 ---------
Plan to change the RAM.
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.
Quote
Yes, you need to upload the dump.