Possibly bad RAM, I had the same errors and it was a faulty stick of RAM
matty88 LPG Installer :p Joined Aug 5, 2005 Messages 423 Reaction score 3 Points 18 Age 35 Location Doveton Members Ride TEXXXY: Resprayed TX3 Non Turbo Sep 24, 2006 #11 Possibly bad RAM, I had the same errors and it was a faulty stick of RAM
Reaper Tells it like it is. Joined Aug 15, 2004 Messages 6,493 Reaction score 11,536 Points 113 Location SE Suburbs, Melbourne Members Ride RG Z71 Colorado, 120 Prado , VDJ200, Vantage Sep 24, 2006 #12 tr3nt said: Not to insult your intelligence or anything yobbo.. but im pretty sure the master/slave configuration is setup right. It all boots/works fine.. until it pops up bluescreen. Click to expand... You may have tried already, but put in a different IDE cable. Your one might be buggered. Reaper
tr3nt said: Not to insult your intelligence or anything yobbo.. but im pretty sure the master/slave configuration is setup right. It all boots/works fine.. until it pops up bluescreen. Click to expand... You may have tried already, but put in a different IDE cable. Your one might be buggered. Reaper
M mischf New Member Joined Jul 30, 2006 Messages 67 Reaction score 0 Points 0 Members Ride VN Executive S2 Sep 24, 2006 #13 It's a hard disk problem. ntfs.sys is the filesystem driver. The filesystem is on your hard drive... lol Try a brand new cable and make sure it's the right way round. Even the old parallel ide cables have a right and wrong way.
It's a hard disk problem. ntfs.sys is the filesystem driver. The filesystem is on your hard drive... lol Try a brand new cable and make sure it's the right way round. Even the old parallel ide cables have a right and wrong way.