Gamingforce Interactive Forums
85242 35212

Go Back   Exploding Garrmondo Weiner Interactive Swiss Army Penis > Garrmondo Network > Help Desk
Register FAQ GFWiki Community Donate Arcade ChocoJournal Calendar

Notices

Welcome to the Exploding Garrmondo Weiner Interactive Swiss Army Penis.
GFF is a community of gaming and music enthusiasts. We have a team of dedicated moderators, constant member-organized activities, and plenty of custom features, including our unique journal system. If this is your first visit, be sure to check out the FAQ or our GFWiki. You will have to register before you can post. Membership is completely free (and gets rid of the pesky advertisement unit underneath this message).


Computer Freezes/BSOD woes
Reply
 
Thread Tools
LiquidAcid
Chocorific


Member 6745

Level 38.97

May 2006


Reply With Quote
Old Jul 20, 2006, 01:12 PM Local time: Jul 20, 2006, 07:12 PM #1 of 17
Turn off the automatic reboot on BSOD and write down the BSOD message. Then post it here.

How ya doing, buddy?
LiquidAcid
Chocorific


Member 6745

Level 38.97

May 2006


Reply With Quote
Old Jul 21, 2006, 05:38 AM Local time: Jul 21, 2006, 11:38 AM #2 of 17
Seems to me like a driver problem or maybe also memory corruption. Tried scanning the memory with memtest86 yet?

There's nowhere I can't reach.
LiquidAcid
Chocorific


Member 6745

Level 38.97

May 2006


Reply With Quote
Old Jul 21, 2006, 10:54 AM Local time: Jul 21, 2006, 04:54 PM #3 of 17
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.
LiquidAcid
Chocorific


Member 6745

Level 38.97

May 2006


Reply With Quote
Old Jul 22, 2006, 12:01 PM Local time: Jul 22, 2006, 06:01 PM #4 of 17
I just wanted you to know that memory support on AMD processors has always be a slight problem after they integrated the memory controller directly into the CPU. The RAM I bought at first was high quality TwinMOS, two modules for dual channel support. I wasn't able to get them to run in dual channel, they even didn't work when dual channel was of. Only after reducing the pseudo-FSB (which didn't really exist at this time anymore) to half of the specified value and only using one of the modules the system worked. The integrated memory controller has always been quite picky when it comes to RAM. I know the situation has improved, but maybe you problem is general incompatibility between the RAM modules and the cpu's mem-controller.
If the Corsair modules are still in your reach you could try testing them on another board.

I am a dolphin, do you want me on your body?
Reply


Exploding Garrmondo Weiner Interactive Swiss Army Penis > Garrmondo Network > Help Desk > Computer Freezes/BSOD woes

Forum Jump


All times are GMT -5. The time now is 06:55 PM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2026, vBulletin Solutions, Inc.