just built a system for the first time and need a little help

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Uniden900

Junior Member
Feb 5, 2005
2
0
0
I am having the same problem. It generally occours when changing resolutions (alt-tab, entering-exiting games) . We all have the same similar hardware too. So there is something peculiar here.

It didnt' do this when I had the windows x64 evaluation version installed. Nor did it do this before I had SP2. I'm leaning towards software,-- windows software. I have all the latest updates, and all the latest drivers. If I had to take a shot in the dark I bet it is one of those many windows "updates" I have installed. I'm currently doing trial and error i'll keep everyone posted.
 

montag451

Diamond Member
Dec 17, 2004
4,587
0
0
When a drive that was in DMA mode reverts to PIO mode [firstly, what PIO mode is it that it comes up as????] then it may be due to Cyclic Redundancy Check errors.
If your drive comes with a few errors, XP automatically slows the drive down.

This is also backed up by the results from the drive test you conducted - problem with the drive layout, but the hw is ok.
File Structure Test Result:
Partition 1 (NTFS (200 GB) ) Result: Failed with critical Errors

How was the drive partitioned?
How was the drive formatted? [I know NTFS, but, What apps did you use to do this?]

You might have to repartition and format again. Also make sure that the MBR is overwritten and you do a long slow format.

 

Uniden900

Junior Member
Feb 5, 2005
2
0
0
Well I did some searching it isn't any of the windows updates. It is the Video Card Drivers. I found on another forum that this guy with the same problem installed the Omega Nvidia card drivers (www.omegadrivers.net) omega driver 61.77 and it worked just fine. I did the same and I have yet been able to replicate the stop error\crash. My guess is there is a flaw in the latest Nvidia drivers that doesn't like something in our similar hardware.

It appears this has fixed the problem:

Maybe if you can find an earlier version of the official Nvidia driver or go the Omega route you should be working..

Someone please do the same and verify that this is a possible fix.