PC Peripherals BSODs - Error detected on device during a paging operation

Status
Not open for further replies.
H

hippy2981

Contributor
hmmmm. i have the crucial ballistix 2x1gb 200mhz 2.66v 3-3-3-8 1t [CL1115V.61]. there's a thread on dfi-street (http://www.dfi-street.com/forum/showthread.php?t=29743) that runs like 50 odd pages regarding the recent problems with this memory. yesterday, i got 3 BSODs and that worries me now. fingers towards memory mostly.

i ran SP with blend. 4h, no errors. 4h, no errors.

memtest86 (3.2) 12 passes, 7h, no errors.

i read on the memtest86 site (http://www.memtest86.com/) and it mentions that till test #8 (Modulo-X, X = 20), the caching, buffering and out of order execution may interfere with the results and some errors can go undetected in the moving inversions tests (#2, #3, #4, #6). for that reason, the Modulo-X test #8 was implemented.

so, my question: does disabling cache (only the L2) in AMD64 (opteron 170 DC) help to detect more errors? has anyone who's getting errors with cache on tried with cache off? i dont know since i've NOT been getting errors so far (fingers crossed).

has anyone run the Bit fade test? does it detect errors that are NOT detected in the 8 tests?

Test 9 [Bit fade test, 90 min, 2 patterns]

"The bit fade test initializes all of memory with a pattern and then sleeps for 90 minutes. Then memory is examined to see if any memory bits have changed. All ones and all zero patterns are used. This test takes 3 hours to complete. The Bit Fade test is not included in the normal test sequence and must be run manually via the runtime configuration menu."
 
Hippy are you sure its your hardware specifically memory that is causing BSOD, cant it be a software thing, can you tell us when does BSOD occurs, can be a case of bad drivers etc.

Best would be to check the system logs and be certain its a hardware and not a software issue.
 
from MS online crash analysis:

1st time it was the memory.

2nd time i dont remember.

3rd time it was the device drivers.

i'd check the logs more thoroughly.
 
If you've just added the ballistix RAM, then the BSOD is probably because of it - either way, add just 1 stick of RAM and see if your system is stable. If you have some other RAM lying around, try it and see if you're still getting BSOD.
 
i had that in mind but that's when memtest86 (or SP) starts giving me errors. and it doesn't so far. anyways, like dipdude said would check the logs and see if i find anything.
 
all dumps have the common preceeding log.

"An error was detected on device \Device\Harddisk0\D during a paging operation."
 
Did u get ur ballistix from newegg or crucial? Make sure u have active ram cooling. Looks like ur hard drive is gonna die or u are having nf4 data corruption issues.
 
Chaos said:
Did u get ur ballistix from newegg or crucial? Make sure u have active ram cooling. Looks like ur hard drive is gonna die or u are having nf4 data corruption issues.
Click to expand...

newegg. active ram cooling? i dont think the RAM is heating up (if that's what you mean).

another 4h of memtest86. no errors. let's leave RAM out for a moment.

nf4 data corruption issues? more info please.
 
nf4 data corruption issue :O dang chaos ur scaring me even before building my rig :bleh:
*doin some research now* :P
 
I had similar problems with my ballistix. It started giving BSOD one fine day.

no memtest errors. It was hardly a week old.

Then it started giving 3-4 erros in test 5. And then it simply stopped working.

I didnt even get a chance to test those sticks for even moderate oc.

Dont know why but it seems entire batch of these sticks were flawed. But my HDD too went bad in couple of weeks after this incidence. But it was hardware failure on that HDD. crunching noise of head and HDD stopped being Detected one fine day. It was baracuda 7200.8 which was infamous for such issues anyway.

So I doubt its NF4 data courruption issue unless you are using maxtor drives.

if possible to send the ram back to either get it RMAed or store credit so that you can go for something else.

At this time simply too many ballistix sticks having issues out there.
 
funkymonkey said:
I had similar problems with my ballistix. It started giving BSOD one fine day.

no memtest errors. It was hardly a week old.

Then it started giving 3-4 erros in test 5. And then it simply stopped working.

I didnt even get a chance to test those sticks for even moderate oc.

Dont know why but it seems entire batch of these sticks were flawed. But my HDD too went bad in couple of weeks after this incidence. But it was hardware failure on that HDD. crunching noise of head and HDD stopped being Detected one fine day. It was baracuda 7200.8 which was infamous for such issues anyway.

So I doubt its NF4 data courruption issue unless you are using maxtor drives.

if possible to send the ram back to either get it RMAed or store credit so that you can go for something else.

At this time simply too many ballistix sticks having issues out there.
Click to expand...

thanks for the info. so far, it doesn't seem the RAM. so far that is. i know these sticks have issues over here but crucial is dealing with them. i have been following that RAM thread and the more they are OCed the quicker they die ranging from 2 weeks to 2 months.

i have a seagate 160 7200.8 sata1. the rest of the rig is in the sign.
 
Chaos said:
Did u get ur ballistix from newegg or crucial? Make sure u have active ram cooling. Looks like ur hard drive is gonna die or u are having nf4 data corruption issues.
Click to expand...

g1 chaos. looks like this for the moment. hard drive problems or nf1 data corruption.

my HDD is seagate 160gb 7200rpm sata1 NCQ. forgot to mention "NCQ" in the sign. i ran chkdsk and it does find some errors and fixes it. like index errors or discovery of free space marked as allocated in MBT. but there are no bad sectors. does this point towards nf4 data corruption? i have not disabled NCQ as some of the sites suggest. (reading as i write.)

other than the nvidia display, should i be using the nvidia ide or nvidia ethernet drivers in 6.70? i dont use the nvidia FW driver.

EDIT01:

http://forums.anandtech.com/messageview.cfm?catid=29&threadid=1771160

http://forums.nvidia.com/lofiversion/index.php?t8171-0.html
 
admin, can you change the topic from "memtest86 questions" to "BSODs with error was detected on device during a paging operation"?
 
1) Try recreating your page file.(with minimum fragmentation)

2) OT: on the dfi ultra -d i was using the marvell NIC. i had disabled the nvidia NIC as it was not very stable for me atleast ....(due to the login software of my former isp in2cable)
 
hippy2981 said:
g1 chaos. looks like this for the moment. hard drive problems or nf1 data corruption.

my HDD is seagate 160gb 7200rpm sata1 NCQ. forgot to mention "NCQ" in the sign. i ran chkdsk and it does find some errors and fixes it. like index errors or discovery of free space marked as allocated in MBT. but there are no bad sectors. does this point towards nf4 data corruption? i have not disabled NCQ as some of the sites suggest. (reading as i write.)

other than the nvidia display, should i be using the nvidia ide or nvidia ethernet drivers in 6.70? i dont use the nvidia FW driver.
EDIT01:
http://forums.anandtech.com/messageview.cfm?catid=29&threadid=1771160
http://forums.nvidia.com/lofiversion/index.php?t8171-0.html
Click to expand...

Possible data corruption issues. Try disabling NCQ in the bios and see if those paging errors persist. If I were you, I'd wanna do a surface scan of the hard drive as well! Also DO NOT use NV IDE drivers. They suck. Use the standard ones that come with XP.
 
x86 said:
nf4 data corruption issue :O dang chaos ur scaring me even before building my rig :bleh:
*doin some research now* :P
Click to expand...
there are some serious issues abt that..u can read up abt it on many tech websites..
 
sorry for the late response. DCfinal fraggin yesterday :D.

deejay said:
1) Try recreating your page file.(with minimum fragmentation)
Click to expand...
done. 2048MB.

deejay said:
2) OT: on the dfi ultra -d i was using the marvell NIC. i had disabled the nvidia NIC as it was not very stable for me atleast ....(due to the login software of my former isp in2cable)
Click to expand...

i'm on LAN1 (Vitesse VSC8201). but this may not be related to my issue. i tried using LAN2 but couldn't for some reason (forgot).
 
Status
Not open for further replies.
Top Bottom