Brand new computer having some BSOD's

EkoWraith said:

Alright, i'll try that. :)

*Edit* Neither taking ownership or trying to rename in safe mode would let me rename the files. However, i found out that these files are included with the latest drivers available for this mouse, so i suppose they cause no harm. --

EkoWraith said:

Also another question; Can a defect RAM unit interfere with/corrupt files during program installations?

Could any of you answer this for me aswell? That is if you know of course.

Once again, I really appreciate all the help!

It might, but I don't know if I have ever seen it.

Jonathan_King said:

It might, but I don't know if I have ever seen it.

Alright, so what is the most usual cause of file corruption during installations? It might be the HDD aswell, but my RAM was the only one that had any errors at all. Is there anything else you suggest i should check?

Wait, you had errors in Memtest86?

If so, test the sticks individually, to see if you can find whether it is a compatibility issue, bad stick, or bad motherboard.

If you find a stick that lasts 6 passes with no errors, test it in each of the other slots.

Jonathan_King said:

Wait, you had errors in Memtest86?

If so, test the sticks individually, to see if you can find whether it is a compatibility issue, bad stick, or bad motherboard.

If you find a stick that lasts 6 passes with no errors, test it in each of the other slots.

Yeah, i did have errors. But strangely the BSOD's have stopped, even when trying to install.. But, i continue getting getting errors about corrupted files when im trying to patch/update the game. It might be a problem with the games patching program though.

I'll wait till i get the new memory stick i ordered to do another MemTest, i get it tomorrow anyway so.

Bad memory modules could definitely cause file corruption errors...

Tews said:

Bad memory modules could definitely cause file corruption errors...

Thanks, Tews; I learned, too. :)

So i had another BSOD while playing a game this time?

Could anyone take analyze it for me so i get it fixed(If possible)

Thanks again!

Have you replaced the bad ram yet??

Tews said:

Have you replaced the bad ram yet??

No, i havent. I dont get the replacement untill tomorrow.

Just wanted someone to analyze it to make sure it is the ram causing the BSOD's. And if there's any other issues aswell that may cause it.

The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause.

Lets wait until you get your new ram before going any further with this, as it may well take care of your problem..