Hi:
I am having a problem with the system in my signature called "rig 1". I recently ( about a month ago) replaced it's IBM 40GB deathstar hard drive with a WD 1000JB 8MB Cache 7200PRM PATA-100 hard drive which was new/unopened ( I purchased the hard drive in Summer of 2002). Anyway, I decided to set this hard drive up as a dual boot of Win2K Pro and WinXP Home. I used Partition Magic 8.0 to create two partitions giving the faster partition to WinXP. After I installed the two operating systems, the drivers and the software things seemed to be running fine except that WinXP was not as fast and seemed just a little "shaky" and "slow" compared to Win2k but it was stable. I wondered if maybe the "sluggishness" was due to the fact that (for right now) the system has only a single Crucial 256MB DIMM and that I needed to bump to 512MB.
Well, UNDER WINXP ONLY, I updated my Gigabyte AP64-D's drivers to a newer version of the ATI Catalyst drivers posted at the Gigabyte website. What a mistake. When I'm running WinXP the system will suddenly "crash" and spontaneously reboot several times per day or it will flash to a "blue screen" that reads, in effect, that the system was "froze" to be protected from damage. Then there is a lot of gibberish on the blue screen such as "...RIVER_IRQL_NOT_LESS_OR_EQUAL..." and other nonsense. The only thing I can understand on that blue screen is the message that there is some sort of problem with tbirdhd.sys, which is one of the files used by my Phillips PSC-705 soundcard. However, I NEVER had this problem BEFORE upgrading to the newer Catalyst drivers.
Anyway, I ran a complete virusscan of the system; something I do regularly, and found no problems. Then I re-installed my soundcard drivers. The same problems continued. Then I "rolled back" to the orginal older ATI drivers I had been using for the videocard but STILL the problem persists. It is so frustrating to be working in WinXP and never knowing at what moment the system will either INSTANTANEOUSLY crash and reboot OR give me that odd blue screen. I've tried to determine if there is any particular TYPE of operation in which the system is more vulnerable to this problem but the only thing I have noticed is that it tends to happen more often when I am opening a web page, transferring mulitple files from one section of the hard drive to another but in general it can happen at any time.
The really frustrating thing is that I can run under Win2k for hours and hours and hours and NEVER have a crash or blue screen.
So I think you see the dilemma. It would be easy to point the finger at the power supply but the system runs just fine under Win2k with the SAME p/s. If my memory is at fault, wouldn't I have crashes and blue screens under Win2k???
The problems under WinXP home really seemed to start AFTER I installed those newer ATI catalyst drivers and even though I have done a rollback to the older ATI drivers my problems under WinXP persist. Right now I am typing this running Win2k and have NO WORRIES that the system is going to crash or bluescreen.
Does anyone have any ideas, suggestions or solutions to the WinXP "spontaneious reboot" and "blue screen" problems ???
Thanks in advance for your input.
I am having a problem with the system in my signature called "rig 1". I recently ( about a month ago) replaced it's IBM 40GB deathstar hard drive with a WD 1000JB 8MB Cache 7200PRM PATA-100 hard drive which was new/unopened ( I purchased the hard drive in Summer of 2002). Anyway, I decided to set this hard drive up as a dual boot of Win2K Pro and WinXP Home. I used Partition Magic 8.0 to create two partitions giving the faster partition to WinXP. After I installed the two operating systems, the drivers and the software things seemed to be running fine except that WinXP was not as fast and seemed just a little "shaky" and "slow" compared to Win2k but it was stable. I wondered if maybe the "sluggishness" was due to the fact that (for right now) the system has only a single Crucial 256MB DIMM and that I needed to bump to 512MB.
Well, UNDER WINXP ONLY, I updated my Gigabyte AP64-D's drivers to a newer version of the ATI Catalyst drivers posted at the Gigabyte website. What a mistake. When I'm running WinXP the system will suddenly "crash" and spontaneously reboot several times per day or it will flash to a "blue screen" that reads, in effect, that the system was "froze" to be protected from damage. Then there is a lot of gibberish on the blue screen such as "...RIVER_IRQL_NOT_LESS_OR_EQUAL..." and other nonsense. The only thing I can understand on that blue screen is the message that there is some sort of problem with tbirdhd.sys, which is one of the files used by my Phillips PSC-705 soundcard. However, I NEVER had this problem BEFORE upgrading to the newer Catalyst drivers.
Anyway, I ran a complete virusscan of the system; something I do regularly, and found no problems. Then I re-installed my soundcard drivers. The same problems continued. Then I "rolled back" to the orginal older ATI drivers I had been using for the videocard but STILL the problem persists. It is so frustrating to be working in WinXP and never knowing at what moment the system will either INSTANTANEOUSLY crash and reboot OR give me that odd blue screen. I've tried to determine if there is any particular TYPE of operation in which the system is more vulnerable to this problem but the only thing I have noticed is that it tends to happen more often when I am opening a web page, transferring mulitple files from one section of the hard drive to another but in general it can happen at any time.
The really frustrating thing is that I can run under Win2k for hours and hours and hours and NEVER have a crash or blue screen.
So I think you see the dilemma. It would be easy to point the finger at the power supply but the system runs just fine under Win2k with the SAME p/s. If my memory is at fault, wouldn't I have crashes and blue screens under Win2k???
The problems under WinXP home really seemed to start AFTER I installed those newer ATI catalyst drivers and even though I have done a rollback to the older ATI drivers my problems under WinXP persist. Right now I am typing this running Win2k and have NO WORRIES that the system is going to crash or bluescreen.
Does anyone have any ideas, suggestions or solutions to the WinXP "spontaneious reboot" and "blue screen" problems ???
Thanks in advance for your input.
Facebook
Twitter