BSOD. 8 different errors. More common playing GW2.

[VicLost]

This has been happening for several months, and I've been slowly trying to work on it.

It first started when I installed an SSD as my main drive. The crashes would happen several times a day and sometimes back to back. Sadly I don't have the dumps from those. I took the SSD back out, and went back to my old setup. The blue screens still happened, but far less often sometimes not for a week or more. I believe I have minidumps from the last 17 crashes.

I'm making this thread because since the launch of GW2 (yesterday) I have received 6 crashes.

If any other information is needed just let me know.

 

[richc46]

Welcome
The report points toward memory.Take this test.
Run for 8 passes.
Then test each stick in a good slot for 6 passes.
If you have dual channel, the results may be incorrect, if shows pass.
Guide to using Memtest86+ - Geeks to Go Forums

 

[VicLost]

Welcome
The report points toward memory.Take this test.
Run for 8 passes.
Then test each stick in a good slot for 6 passes.
If you have dual channel, the results may be incorrect, if shows pass.
Guide to using Memtest86+ - Geeks to Go Forums

I'd be so happy if it was ram.
I'll run this tonight.
Thanks.

 

[VicLost]

Can't make this Shit up. This is after an hour of memtest.
http://www.imgur.com/fdRkZ.jpeg
Should I leave it running? It's still going, but I can't read anything.

 

[richc46]

Leave it running for 8 passes and then if it does not show errors. Test each stick for 6 passes.

 

[VicLost]

Which one of those numbers is the passes?
How will I know if it gets an error? I can't read anything...
Did you look at the picture?

 

[richc46]

When done you should see errors
Using Memtest to test computer memory

 

[VicLost]

Wait. Ok theres a read line across the screen that means there's an error right?
Should I move on to doing them 1 at a time?

 

[richc46]

If you do have an error, continue doing one stick at a time, but you must solve the problem of the error. You may need new ram.

 

[VicLost]

A red line means there is an error right?
I can't read anything all of the text in memtest is corrupted and displaying weird symbols

 

[richc46]

I really cant answer that one. When there is an error it tells you how many.

 

[VicLost]

I'm just going to assume that's an error, and start testing it individually.

 

[VicLost]

Ok so I tested all of the sticks individually and they passed.
Does that mean one of the slots could be bad?

I feel like it might be one of my video cards that could be the problem. Isn't dxgmms1.sys related to video drivers/cards.
The ati driver that is involved in some of the crashes is the driver for my video cards too.

 

[richc46]

To test the slots take a good stick and test each slot. If slot is bad that means bad MotherBoard (not good)
As far as Video driver, yes that is for your video card, but that was just one of many driver hinted at by the reports. This is not a science, but an art. Experience tells us when you have all different drivers, most times it may be hardware. Lets be sure about memory and then move on.

 

[VicLost]

Hmmm. I reran all of them last night to make sure that there was an error, and that it didn't just bug out the first time.
It came back as passed.
So I guess the ram isn't the problem?

 

[richc46]

Lets see if it is a driver
Driver Verifier
I'd suggest that you first backup your data 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/Windows 7 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.
Driver Verifier - Enable and Disable

 

[VicLost]

Setup verifier and went to restart. Upon the restart it chained c9 errors (I can upload them it if you want).
I tried to get into safe mode, but I'm not sure how to do that on this computer F8 only brings up a boot priority list.
I can start-up repair (which failed), and shutdown all the way. I turned it back on, and it booted fine.

Should driver verifier still be running? How do I check to see if it still is?

 

[richc46]

Keep the computer running for 36 hours. If you did not turn off the verfier it should still be working.

 

[VicLost]

I was right. It wasn't running. What should I do now?
I tried doing it again, but it still blue screens everytime.
Also, I guess I don't have the ability to get into safe mode.
I tried every key I could think of including the usual f8

 

[richc46]

Well looks like we may have to use other methods rather than verifier.
Uninstall and send me any dumps that you have.
Then try this
http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html