amenoss
asked on
A parity error was detected on \Device\Scsi\nvgts2
I have an older XP system that we use in the office for some specific tasks, recently we have had some issue with it restarting on its own, if you happen to be at it when it happens, there is a flash of a BOD before it reboots. The only thing I can find in the event log is: A parity error was detected on \Device\Scsi\nvgts2. This error alert happens hourly. The only thing I was doing the last time I when it occurred was using IE. The system has 4 drives in it a 96GB SSD, 400GB storage drive, and a pair of 75gb drives in Raid 1. Doing a smart test the 96gb and 400gb both pass, the raid array doesn't show up individually there. The software (SIL Raid Manager) shows the raid array with no issues. The motherboard is a ASUS A8N-SLI Premium 939 NVIDIA nForce4 SLI ATX AMD Motherboard. Anyone have any ideas on how to resolve the issue?
John
It seems to have a hardware error, perhaps memory. In any event, go to My Computer -> Properties -> Advanced and look for the restart settings. Set the restart setting NOT to restart on a BSOD. Then you can trap the error and see what the issue is. .... Thinkpads_User
I've seen this before, here to be exact, it is chipset related. Apparantly the issue was fixed by enabling S.M.A.R.T. monitoring in BIOS. Do you have that setting enabled?
ASKER
Thinkpad and Gerw.... I have did both suggestions at this point I will report back with if the issue is resolved or further details based on thinkpad's comment.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The system continues to crash I was able to trap the BSOD error, which is Driver IRQL Not Less or Equal. Any thoughts that the errors might be do to a failing drive? The error doesn't happen instantly it takes normally some time to pass before it happens ( I can't make it happen at will, so to speak).
Driver IRQ not less or equal is usually indicates a driver corrupted (video, network, etc.). Does the error message (stop number) shed any light.
You can get memtest.exe and run that to see if memory is failing.
I am not sure about disk testing in a Raid environment. .... Thinkpads_User
You can get memtest.exe and run that to see if memory is failing.
I am not sure about disk testing in a Raid environment. .... Thinkpads_User
ASKER
I had reloaded the network and raid drivers prior to the intial posting, but I did update the Video after your post. The stop code started out like 0 x000000D1 081503859, which in my google searches didn't turn up much. When the machine restarted after the BSOD, the raid array was degraded and was rebuilding. It failed and one of the drives now appears as orphaned, I plugged the drive into the standard SATA controller and ran HD diag on it. It passed the SMART test and the other non destructive tests. I have now plugged it in on a different port on the raid controll (its 4 port), and will see what comes of it. I also ran memtest prior to the posting, I let it run for I think 10 passes it found no errors. I posted a screen shot from the array manager and event log of it..
Raid-Array.JPG
Raid-Array.JPG
The correct answer of what the parity error means is #37337976. There is also data corruption, which explains #37350880
Root cause is most likely interoperability issue. The NVIDIA fakeraid chip was never designed for SSDs to work in the first place, which is probably root cause. It just can't keep up. That is why there is no hardware fault. Points should go to #37337976.
Root cause is most likely interoperability issue. The NVIDIA fakeraid chip was never designed for SSDs to work in the first place, which is probably root cause. It just can't keep up. That is why there is no hardware fault. Points should go to #37337976.
ASKER
Once I plugged the drive into a different raid port as described on 37350880 the issue has cleared up no further BSOD since that day and the parity error is no longer in error log.