Tweet
SO about a couple of months ago I loaded up my New G210 card in my main system to replace a dieing ATI Radeon that I had previously installed.
It fixed the issues and lockups and but it is a slower card. (I knew it was gonna be slow, I just did not think it would be THIS slow).
I finally decided to load up the drivers for it hoping that it would speed it up a bit (which it did) BUT, durring the process I grabbed the NVIDIA 320.49 DISPLAY drivers (please pay attention to the word DISPLAY). This was about a week or so after installing the new card.
Durring the LOADING of the drivers I saw that it wanted to load up some HD Audio drivers. But this was for a DISPLAY card, not a SOUND card and my SOUND drivers were FINE. So I told it NO. JUST load the DISPLAY drivers...
So now all the BS starts. Upon rebooting after loading the drivers, I start getting messages of the system finding new HD Audio devices and it wants to load the drivers... (MOTHER****ER...) What the hell do you NOT understand about DISPLAY ONLY drivers? SO, I figure that I can be more stubborn then the computer if I want to be so I decided to hit CANCEL all 4 times it wanted to install the drivers. I am NOT going to let it install HD drivers for something that I did not add and I had no intention on upgrading drivers because my sound was functioning FINE.
So I guess Windows XP decided to scheme on how it would prod me in the right direction to load the drivers, and this is what it did.
Shortly after changing my DNS the other night I left the comp and came back to a BSOD. It listed NO files, but the irql_not_equal_or_greater and it was a STOP D1 error.
I hit reset.
Come back shortly and get online, EACH time refusing to install the drivers again, about another hour or so and BSOD while I am online reading stuff.
So this goes on and I ALMOST posted "how can changing my DNS cause me to start BSOD all of a sudden." But I thought, okay, let's look into what this is about, it WAS a STOP D1 yet again. In fact, ALL stops errors were the same cause, and all were STOP D1 errors.
SO, I looked it up and found a TGIS.SYS or something file that was the root cause of a lot of these stop errors upon bootup.- EVEN though none of my STOP D1 errors listed any filenames. (just wanted to protect them I guess and remain anonymous).
I looked into that and found two utilz from MS that will yank the SYS file OUT of your system and make it more stable I guess. I grabbed them both but refrained from using them. I waited, about 3 hours later I come back inside and I am looking at another BSOD so I reboot and cancel the driver installs upon booting up into windows XP again and then I try to run the 32 bit version of the util I downloaded and it tells me it is not a valid 32 bit executable... Same with the 64 bit version.
I am now pissed.
SO, I do a little more searching and find that all of these STOP D1 errors are typically hardware or driver related. I am about to run my memtest and then I decide, LET'S stop and see if these damn HD drivers are the issue because I do NOT want to know if my hardware is failing. SO I reboot in safe mode and let the comp idle for about 6 hours, NO BSOD. Then I reboot, go hunt down the EXE file for the driver setup and run it. Now for the past 12 hours NO more BSOD...
WTFE. This is SUCH a dog and pony show of BS. I mean really, Everything was FINE until you (the computer) were told that I did not want to load up any drivers, so then you have an issue and throw a fit and ***** and moan until you get your way...
Anyways, moral of the story, I dunno if there is any moral, I am just pissed that I had to give in and load drivers for something that was working FINE but windows had issues and demanded those drivers even though they were in a VIDEO card package and not for my MOBO...
I swear to GAWD that Linux based VMware is going to get on this hardware sooner then you think...
It fixed the issues and lockups and but it is a slower card. (I knew it was gonna be slow, I just did not think it would be THIS slow).
I finally decided to load up the drivers for it hoping that it would speed it up a bit (which it did) BUT, durring the process I grabbed the NVIDIA 320.49 DISPLAY drivers (please pay attention to the word DISPLAY). This was about a week or so after installing the new card.
Durring the LOADING of the drivers I saw that it wanted to load up some HD Audio drivers. But this was for a DISPLAY card, not a SOUND card and my SOUND drivers were FINE. So I told it NO. JUST load the DISPLAY drivers...
So now all the BS starts. Upon rebooting after loading the drivers, I start getting messages of the system finding new HD Audio devices and it wants to load the drivers... (MOTHER****ER...) What the hell do you NOT understand about DISPLAY ONLY drivers? SO, I figure that I can be more stubborn then the computer if I want to be so I decided to hit CANCEL all 4 times it wanted to install the drivers. I am NOT going to let it install HD drivers for something that I did not add and I had no intention on upgrading drivers because my sound was functioning FINE.
So I guess Windows XP decided to scheme on how it would prod me in the right direction to load the drivers, and this is what it did.
Shortly after changing my DNS the other night I left the comp and came back to a BSOD. It listed NO files, but the irql_not_equal_or_greater and it was a STOP D1 error.
I hit reset.
Come back shortly and get online, EACH time refusing to install the drivers again, about another hour or so and BSOD while I am online reading stuff.
So this goes on and I ALMOST posted "how can changing my DNS cause me to start BSOD all of a sudden." But I thought, okay, let's look into what this is about, it WAS a STOP D1 yet again. In fact, ALL stops errors were the same cause, and all were STOP D1 errors.
SO, I looked it up and found a TGIS.SYS or something file that was the root cause of a lot of these stop errors upon bootup.- EVEN though none of my STOP D1 errors listed any filenames. (just wanted to protect them I guess and remain anonymous).
I looked into that and found two utilz from MS that will yank the SYS file OUT of your system and make it more stable I guess. I grabbed them both but refrained from using them. I waited, about 3 hours later I come back inside and I am looking at another BSOD so I reboot and cancel the driver installs upon booting up into windows XP again and then I try to run the 32 bit version of the util I downloaded and it tells me it is not a valid 32 bit executable... Same with the 64 bit version.
I am now pissed.
SO, I do a little more searching and find that all of these STOP D1 errors are typically hardware or driver related. I am about to run my memtest and then I decide, LET'S stop and see if these damn HD drivers are the issue because I do NOT want to know if my hardware is failing. SO I reboot in safe mode and let the comp idle for about 6 hours, NO BSOD. Then I reboot, go hunt down the EXE file for the driver setup and run it. Now for the past 12 hours NO more BSOD...
WTFE. This is SUCH a dog and pony show of BS. I mean really, Everything was FINE until you (the computer) were told that I did not want to load up any drivers, so then you have an issue and throw a fit and ***** and moan until you get your way...
Anyways, moral of the story, I dunno if there is any moral, I am just pissed that I had to give in and load drivers for something that was working FINE but windows had issues and demanded those drivers even though they were in a VIDEO card package and not for my MOBO...
I swear to GAWD that Linux based VMware is going to get on this hardware sooner then you think...
Comment