• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Jmicron drivers causing delayed write failed???

Okasa

Member
Ok, so ive been getting a Delayed Write Failed Error on my new build from the start. I have tried just about EVERYTHING and im thinking its possible that its a problem with the Jmicron raid drivers i have installed or ive heard that the nvidia graphics driver sometimes causes this.

My rig:
asus m2n-sli dlx
mushkin ddr2800 2gb
bfg 7900gt oc
amd X2 4200+
creative sb audigy2 zs
1x 320gb WD 16mb 7200rpm JBOD array
1x 320gb WD 16mb 7200rpm JBOD array
2x 74gb WD 10k Stripe

Things ive tried:
reformatting
replacing cables
replacing harddrives
replacing mobo
trying individual ram sticks
turning off LargeSystemCache in registry
changing paging file in registry to max value (ffffffffff)
turning off [enable read caching] [enable write caching] [enable command queing] in the sata controller through the hardware manager.

ive read other forums on this topic, ive looked at microsofts solution....please help me in desperate

EDIT: I almost forgot to mention, i also turned off [allow bios to choose transfer speed] in the hardware manager as well
 
oh and i also noticed that the graphics card and the raid controller are both under the same IRQ if that matters
 
ok i just tried pio mode instead of sata for transfer on the harddrives, and the comp froze mid transfer
 
You've tried running at stock, right? I've heard bad things about JMicron chips and overclocking over at XtremeSystems.
 
i dont know how i would oc my raid, so i havent messed with it and therefore i assume its stock, if u tell me what to look for i will check to be sure tho
 
(Assuming you are OCing your CPU), overclocking anything causes unpredictable failures so that's the first thing I'd do to eliminate any further complications. Your CPU can pass Prime95 but how do you know everything else is fine? If you're not OCing, never mind, I had just gathered that for some reason.

http://searchwinit.techtarget.com/tip/0,289483,sid1_gci1041334,00.html

I would hook all the drives up to the nForce controller with no JBOD or anything. Others are having problems with the JMicron controller like being stuck in PIO mode. I don't know but I can't help but think that's the problem. I assume you have all of them hooked up to the JMicron?
 
heh yea ive been to that site as well and tried out what they said. my gfx card is slightly oced because its BFG but nothing past that, the cpu and ram are both running stock tho the ram may be running at 2.1-2.1V but is within what the manufac says is good

all drives are hooked up to 4 different raid ports all supported through the jmicron chip
 
I was getting the same error before my Hitachi harddrive died.
I'd run the diagnostic software for your drives to make sure one isn't dying. Mine gave a SMART error before it died.
 
i would think that, but to have it happen on 4 NEW drives all at once, and then happen to all 4 drives again after i RMA 2 of them? id say unlikely. tho i have heard that it is a sign on a dying harddrive
 
Back
Top