nvatabus.sys corruption

R

Ramedge

New member
nvatabus.sys has corrupted in \system32\Drivers\ meaning windows wont start. I cant do the windows recovery to because it Blue screens when i press R - i tried putting windows on a spare HDD and then putting the HDD with the problem in to see if i could get at any files, but the system just restarts itself.

the hard drive with the problem has two partitions i really need to get to the one with my documents, the other has windows on and can be formatted but the thing is i cant format it and low level format would wipe both partitions and i would lose all my A-Level work which was going to be backed up onto my spare HDD but with revision for exams it slipped my mind.

if i dont recover the work on the other partition ive totally fucked up my chance of getting decent alevels. Ive got backups of alot of the stuff but its all to old to and with 3 moths to get 6peices of work done iam panicing some what.

Is there any other way atall i can replace the nvatabus.sys ??

any ideas would be so helpful

Cheers
 
hey man bluescreening in recovermode is a sign of u havin pushed summit too far run a memtest 86 see if there is a probem if so throttle some fsb back put voltage up the usualy wats ur overclock (if memtest show an error this may be hoy it got corrupted in the 1st place .. faulty ram read/writes)
 
name='Joe' said:
hey man bluescreening in recovermode is a sign of u havin pushed summit too far run a memtest 86 see if there is a probem if so throttle some fsb back put voltage up the usualy wats ur overclock (if memtest show an error this may be hoy it got corrupted in the 1st place .. faulty ram read/writes)
Click to expand...

I agree with that, it does sound like memory,
 
ive taken my overclock off and will try the linux boot cd - i can boot to my unbuntu partition on another drive but its never booted with the other drive plugged in so i always have to unplug it to boot to unbuntu any way.

been looking at limiting some FSB but cant were to drop the fsb in the bios, do asus label it sommething different in their bios's?

i made a recovery disk but all it did was boot to a command line where it was stuck on A:\ you couldnt change it to C:\ I always wacked a non currupt version of the nvatabus.sys file on their and tried to copy it over but it wouldnt let me copy it.

I did boot to windows via another drive but it wont boot with the other drive in and if you plug it in when in windows it just recoginises it then restarts.

EDIT:

Joe said:
or chipset or memcontroller damage/stress

....
Click to expand...

So trying the Hard drive in another PC is a good idea? because i expected i would have the same problem but if not i will try that!

Will also do a memtest ASAP!

Thanks for the help, i have had a better responce here than i have had from the Nvidia forums, i guessed because the file starts NV it was prolly something to do with my nforce4 drivers so i went straight to their forums

Cheers guys :D
 
Ramedge said:
ive taken my overclock off and will try the linux boot cd - i can boot to my unbuntu partition on another drive but its never booted with the other drive plugged in so i always have to unplug it to boot to unbuntu any way.

been looking at limiting some FSB but cant were to drop the fsb in the bios, do asus label it sommething different in their bios's?

i made a recovery disk but all it did was boot to a command line where it was stuck on A:\ you couldnt change it to C:\ I always wacked a non currupt version of the nvatabus.sys file on their and tried to copy it over but it wouldnt let me copy it.

I did boot to windows via another drive but it wont boot with the other drive in and if you plug it in when in windows it just recoginises it then restarts.

EDIT:

So trying the Hard drive in another PC is a good idea? because i expected i would have the same problem but if not i will try that!

Will also do a memtest ASAP!

Thanks for the help, i have had a better responce here than i have had from the Nvidia forums, i guessed because the file starts NV it was prolly something to do with my nforce4 drivers so i went straight to their forums

Cheers guys :D
Click to expand...

yea but if it is mem corruption any files u accessed while it was faulty could be corrupted (nvatabus is accessed @ each boot)

try the recovery console the floppy u made cant see ur SATA HDD

for future ref u shd alsways memtest afta each oc
 
Joe said:
or chipset or memcontroller damage/stress

....
Click to expand...

Chipset damage would cause other errors as well, and possibly wouldn't allow the system to get past boot, but it could also be the mem controller.
 
iam going to do this memtest in abit.

if it turns out okay then where do i go from here to try and fix my problem?
 
possible power loss/inadequeacy damaged data cable corrupt bios hell man there is a LOT of possibilities even summit as simple as not shutting down can cause these errors
 
name='Phnom_Penh' said:
I doubt it would cause a cause a bsod in recovery mode though :\.
Click to expand...

actually..... i have had a laptop that was always turned off and not shutdown and it bsod on boot AND in recovery mode as ecovery mode DOES rely on a few files on the HDD <basically for authentication of the system being what its meant to be> and it BSOD[ed] in recover with a kernel memory error (its fixed now)
 
I have done memtest and found 2 errors, not sure what i will do about that. I guess try and RMA the RAM I am going to stick some other RAM in and see if i can repair windows, Which fingures crossed i can !

if not then iam really stuck for ideas :(

EDIT: Left the memtest going for a while longer i checked on it at 95% and saw 2 errors just had another look and its still going but its back at 40% with a nice big list of errors, odear.
 
Ramedge said:
I have done memtest and found 2 errors, not sure what i will do about that. I guess try and RMA the RAM I am going to stick some other RAM in and see if i can repair windows, Which fingures crossed i can !

if not then iam really stuck for ideas :(

EDIT: Left the memtest going for a while longer i checked on it at 95% and saw 2 errors just had another look and its still going but its back at 40% with a nice big list of errors, odear.
Click to expand...

Is this at stock speed?
 
name='FragTek' said:
Is this at stock speed?
Click to expand...

Yeep my whole system is at stock speeds.

just an update, the spare RAM i tried didnt work again i got a blue screen at the recovery console. going to have ago with some of the tools from www.NTFS.com and see if i can recover any thing, I just need to access this one partition to recover my work then i will format the whole drive.

Any more suggestions on what i could do would be great!!
 
what timings are you using ?? loosen em up a bit (numerically higher value) also put more voltage thru the chipset and RAM
 
Using the tools on the NTFS.com site i can actually access my partition and see all my work ( YAY !! ) Theres a copy option but it wont let me copy to the other HDD thats plugged in.

So looks likes Linux Live CD it is !! I cant access my NTFS Drive from my Unbuntu partition, not sure why its different for a live CD Distro.

Thanks for the advise hopfully after the works coppied over i can low level format my hard drive and get windows back on and my work.
 
You must log in or register to reply here.

Similar threads

Dawelio
Corsair iCUE Issue
Replies
1
Views
558
Warchild
W
g0ggles1994
Kitchen Flooring
Replies
8
Views
171
g0ggles1994
g0ggles1994
P
Memory error
Replies
4
Views
4K
Warchild
W
J
Is LTT forum is choke full of spooks ?
Replies
5
Views
213
hmmblah
hmmblah
P
Do some people never learn from the past?
Replies
2
Views
604
Pugsport
P
Back
Top