|
Originally Posted by KrazyTaco
No I haven't. Is there a version of memtest that will work withought booting into windows?
|
Indeed there is
no version of memtest86 that will work under any operating system. Just use a Knoppix disc or a gentoo minimal install disc. The bootloader allows to select the memtest86 os.
|
Originally Posted by KrazyTaco
Apparently it was either my graphics driver or card itself according to Microsoft.
|
I don't see any connections from the drivers causing the BSOD and the graphics subsystem. tcpip.sys is part of the network system and win32k.sys is generic.
|
Originally Posted by KrazyTaco
For kicks and grins I reported the error to Microsoft and it actually gave me a seemingly useful response talking about my graphics and driver. I figured I would just reinstall with the latest drivers then, but upon resetting after uninstalling the old drivers, Windows decided to not even boot up anymore.
|
You did a bootup with protocol creation?
|
Originally Posted by KrazyTaco
I tried eventually reinstalling Windows with 3 different variations of the Proffesional version I had laying around but for whatever reason none of them had a complete and working setup proccess, even though they did a month or so ago.
While I wait for that memtest or whatever, Im downloading a new copy of XP Pro on another computer.
|
You know that you're wasting your time installing software over and over again if the problem is faulty hardware? Check the memory, check the cpu (with something like prime95), the harddrive (using the tool of you choice or the tool you hd vendor provides) and the gfx card.
You say you've another computer, then you can check the components there. memory and hd can be tested without installing an os, so do this first. I know its really frustrating, but its even more frustrating if you install everything again and again and the system fucks up your installation after some hours.
cya
liquid
This thing is sticky, and I don't like it. I don't appreciate it.