Originally Posted by nekrosoft13
like i said before, it can be trigered by:
1) bad memory, but supposelly you tested that already
2) bad driver
3) corrupt OS files, and in post 32 you said sfc scan failed, thats not a good thing
4) faulty hardware
Alright, re did it, and it scanned fine now. Here is a screen shot.
The CBS log is HUUUUGE. I don't really know how to read it.