Numerous BSODs

[renren]

Fresh OS
Fresh Parts
Windows 7 Ult 32 bit SP1

Numerous BSODS. Report attatched with an additional report from CPU-z (report2.html) and dxdiag (dxdiag.txt).

Ive gotten a few more BSOD since the last compilation. If you wish for me to recompile just post back =].

And thanks in advance for any help given <3.

EDIT: Ive done a sfc /scannow and here is the CBS log that it outputted.

 

[zigzag3143]

Fresh OS
Fresh Parts
Windows 7 Ult 32 bit SP1

Numerous BSODS. Report attatched with an additional report from CPU-z (report2.html) and dxdiag (dxdiag.txt).

Ive gotten a few more BSOD since the last compilation. If you wish for me to recompile just post back =].

And thanks in advance for any help given <3.

EDIT: Ive done a sfc /scannow and here is the CBS log that it outputted.

Memory corruption caused by a driver please run these two tests.


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.



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.

 

[renren]

Hi after doing a memtest i am currently at Pass#0 Test#9. Currently have 250,000+ errors. Does this indicate a faulty ram? should i call for a warranty?

Also does my dumps indicate any other potential problems?

Thanks zigzag for finding one of my (possible) problems <3.

EDIT: This test was done in all slots of the motherboard so im assuming its the ram that is faulty.
EDIT2:I uploaded a picture that protains to the second stick being tested. Is this some kind of faulty error?

 

[MvdB]

It could be a faulty ram stick OR faulty mobo mem receptor. Test one stick at a time in all slots. See if that makes a diff. I see that you have tested a ram stick in all slots with ram errors in all. But did you have a good stick tested in all slots so you are sure it is the stick and not the slot(s)/memmanagement module?

 

[renren]

After finding a good stick and slot combination with two passes, i proceeded to test the other just to be sure. thats when it gets weird. Further testing of two or so passes shows that both sticks work fine in the slots i recieved errors from before. what on earth is going on ?

EDIT: im going to leave the stick thats in at the momment for more passes.
EDIT2:I uploaded a picture that protains to the second stick being tested. Is this some kind of faulty error?

 

[MvdB]

If I'm not mistaken, that looks like a bigger problem. Normally, memtest should be able to "hold its own" and tell you nicely if there is a problem. If it can't do that, it could be a broader mobo / memmanagement problem.

Let's be sure by fully testing 1 stick at a time in 1 slot for min of 5 passes.
If that works, no errors, move THAT stick to the next slot and start again.... etc.
We need to know if it varies per slot or not.

 

[renren]

Dear Mr Mv,

Well i tested in that slot with the other working stick (or so i hope it works) with 7 passes just fine. on the same slot as well, i tested on a different slot. This error only occurs with that one stick on the apparently fine slot after 40 odd mins or so. Any other advice you can give me.

On another note i just ordered a new kit of DDR3 memory and hopefully i can get this PC shipped to my cousin by sunday ><.

 

[MvdB]

Dear Mr Mv,

Well i tested in that slot with the other working stick (or so i hope it works) with 7 passes just fine. on the same slot as well, i tested on a different slot. This error only occurs with that one stick on the apparently fine slot after 40 odd mins or so. Any other advice you can give me.

On another note i just ordered a new kit of DDR3 memory and hopefully i can get this PC shipped to my cousin by sunday ><.

I'm not entirely sure what you mean here. So you have 1 stick that tests fine on multiple slots and another stick that tests badly, with errors in those slots? In that case... it luckily is only a stick and not the mobo and your new sticks should work fine.

 

[renren]

Yeh sorry im not feeling to well today. YOu read my mind. Basically that module is faulty (or so i hope) i just hope it happens when they test it at the shop so i can get my money back *Sigh*. Just to mention when i pair them together they give normal erros but seperatly the faulty module will make the screen go all crazy :S. Thanks guys for your help. If anything else happens ill post up or make a new thread.

 

[MvdB]

Yeh sorry im not feeling to well today. YOu read my mind. Basically that module is faulty (or so i hope) i just hope it happens when they test it at the shop so i can get my money back *Sigh*. Just to mention when i pair them together they give normal erros but seperatly the faulty module will make the screen go all crazy :S. Thanks guys for your help. If anything else happens ill post up or make a new thread.

Hope you get it replaced!
If you're sure this is solved, please mark the thread solved at the top? Thx,
Mark