My windows debug

[FeFiDoh]

I had a BSOD and after just getting my ram back in which I had a fault stick previously its annoying.

I took it upon myself to load windows debug but its to make sense out of it personally.

It points to

"Probably caused by : ntkrnlmp.exe"

Which google says hardware/cpu etc..

but the default bucket ID says VISTA_DRIVER_FAULT

http://pastebin.com/aJ0Rmes5

full dump

 

[Dup]

How long has the computer been built. This is probably way off but at work we received a base unit but it would randomly crash and reboot it self after the POST occasionally until it got into windows.

It looks like a RAM issue, one stick wasn't being seen and Memtest went mental at it, but after RMA we had the same issue.

It turned out the "pins" on the motherboard socket (i7) were bent the wrong way and therefore not making contact with the CPU. I managed to use a paper clip and fashion them into some normal looking arrangement and it's worked flawlessly since. Might be worth a look if its a new build.

 

[FeFiDoh]

Built the PC in Oct and it was fine for months.

2 weeks ago I got a virus and a bunch of bsod as well, ran memtest and it showed one faulty stick which had errors almost straight away.

Sent it back and got my new ram 2 days ago.

I have a usb dongle installed on the front usb port, I took it out and it seemed to crash right after.

Praying its a one off as I don't want it to be a hardware fault its just hassle.

Will take a look at the pins tomorrow when I get a chance.

Pc was overclocked at one point but it was at a comfortable speed and the temps/volts were within limits. Got it back on stock now as I sent the ram away.