2009 is NOT my year

[vgbaron]

System was running fine at 400x9 with XP64. Decide to try the 450x9 clock that WAS working on XP32. As it booted into Windows - BSOD error7b.

Went back to 400x9 - BSOD 7b

Tried Safemode - BSOD 7b

Set overclock to auto - BSOD

Everything was working fine until I tried the higher clock that was save in the BIOS.

trying chkdsk /r from the recovery console

[NickN]

Vic

7B indicates a SATA AHCI issue.. or something in the SATA ports out of sorts with the BIOS

Its a very common error with more than just one possible problem but before you start tearing whats left of your hair out I dont think this is a clocking problem but something that goes back to the issue of you not being able to run AHCI/IDE ENHANCED

What it is I dont know but I will see if I can come up with anything

[vgbaron]

Thanx Nick - don't have any hair left - eyebrows are next.

chkdsk didn't seem to work on the sata drive - chugged for a ong time then some error re unsupported system.

I'll watch the football game and stay calm.

[NickN]

Go into your BIOS and verify something has not changed in the way of the SATA drives... check what they are set to run on ACHI, ENHANCED, ETC.. verify the controller is enabled and verify the boot sequence

If that nets nothing, unplug the tower and verify the power connections and SATA conntections to the drives.. you may even want to swap out the SATA cable for the boot drive.

Power up and try again

if it still fails, try moving the boot drive to abother SATA port.. when you do this you may need to enter the BIOS and reverify everything



This error is very specific to the hard drive controller 'missing' although a high memory or unstable memory or cpu clock can cause anything to pop up the error you are seeing is directly hard coded to a missing IDE or SATA contoller on the buss

[vgbaron]

For once, just one teeny bit - I was ahead of you.  ;D

Your comment about AHCI kickstarted the brain cells - I had loaded the saved profile(s) which were saved with the enhanced IDE setting. Switched to AHCi and all is well in beautiful downtown Burbank.

See, without even trying you solved the problem.

It must be hard to be humble when you're as good as you are.

Now to try the 450x9 again.

Sorry 'bout that............

[NickN]

Thanx Nick - don't have any hair left - eyebrows are next.

chkdsk didn't seem to work on the sata drive - chugged for a ong time then some error re unsupported system.

I'll watch the football game and stay calm.

there is something very wrong..  CHKDSK C: /r should have run if the storage system is being recognized by the BIOS

If all else fails above..   clear the CMOS on the system with it unplugged, enter the BIOS, exit menu.. LOAD SETUP DEFAULTS   F-10 save and exit    return to the BIOS and reset it back up (no clocking) ... locate the drives and verify they are set correctly

Note.. I forgot to tell you that moving the drive to another SATA port may clear the 7B error but Windows may, or may not boot. The idea is to get this 7B error clear and figure out if this is a bad cable, port, BIOS, or what

[NickN]

[quote]For once, just one teeny bit - I was ahead of you.

[vgbaron]

twoposts up - resolvd main issue.

should the 450x9 clock work w/o mods in XP64 or might some tweaking need to be done?

First reboot into corrected 450x9 profile loaded XP64 but fairly quickly went o BSOD with System_Service_Exception.

Rebooted again and so far, all seems well.

[vgbaron]

ROFLMAO! Remember, I'm old, when I laugh that hard I might hurt myself.


BTW, did I ever tell you about the time that the sky was falling...........

[NickN]

I thought we had the 450x9 clock numbers already worked out.

Are you still running all of those including GTL?

[vgbaron]

yup no changes - looked up the error on MSDN and might have been a graphics driver glitch.

the clock was very stable on XP32 but I installed the 180.42 64bit driver.

Probably a fluke, I'll just run it a while and see if anything else pops up.

[NickN]

yup no changes - looked up the error on MSDN and might have been a graphics driver glitch.

the clock was very stable on XP32 but I installed the 180.42 64bit driver.

Probably a fluke, I'll just run it a while and see if anything else pops up.

It could have been something in ACPI resources that needed to clear from switching from IDE to AHCI

the storage controller may very well share with the video adapter in ACPI IRQ assignment

[vgbaron]

tried to run 3dMark - got the exception again nv4_disp.dll - that's good old nvidia.

Could try another driver

[NickN]

BTW, did I ever tell you about the time that the sky was falling...........

No... but you would probably sound like me when I tried to explain to a judge many years ago how the brunette grinch stole my life

[NickN]

tried to run 3dMark - got the exception again nv4_disp.dll - that's good old nvidia.

Could try another driver

Were you in the middle of a driver install when all this happened?

If so try uninstall it and install it again

If not.. try 174.74 from the Nvidia site for xp x64