• 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.

INACESSIBLE_BOOT_DEVICE

R

Roza

Junior Member
I've got an A7N8X mobo i decided to upgrade the CPU on from an 1800 to a 3200+. I was up and running just fine after the upgrade and then I lost video signal. I tried to reboot and then got the "INACESSIBLE_BOOT_DEVICE" bluescreen message going into windows. any of you run into this before? I could understand why this would come up if i was changing the motherboard or something but the CPU?
😕
 
Which rev is your board (1.x or 2.x) and BIOS? Have you checked Asus' site to see if you need a newer BIOS rev to support your CPU?
 
temps were fine. rev1.04 cpu is supported with the bios update i installed.

i went back to the old cpu and it's giving the same message.
 
I've had that happen a couple of times, before. Possiblities:

1. When you changed the CPU, or when you flashed the BIOS, something changed in your CMOS.

2. Your IDE cable has gone bad and needs to be replaced.

3. This one's more of a guess based on experience. Either the hard/floppy controller or something in the drive's electronics got set in a non-working state.

Solution 1. Clear the CMOS, and reset it.

Solution 2. Try replacing the IDE cable.

Solution 3. This one may sound weird, but I've been able to get my system back by powering down, disconnecting the IDE cable and running my finger across the connector pins on the drive. I'm not sure why it works, but it has on several occasions.

We all need a few mysteries in our lives to keep them interesting. Good luck. 🙂
 
Harvey, solution 3 is something I've experienced many times.

Running your fingers across the pins may not be the cure but the fact you removed and replaced the cable certainly could be.

Nice to see you [ahem] old timer.
 
Originally posted by: jadinolf
Harvey, solution 3 is something I've experienced many times.

Running your fingers across the pins may not be the cure but the fact you removed and replaced the cable certainly could be.

Nice to see you [ahem] old timer.
Click to expand...
I don't think so. I've tried just unplugging the cable, waiting a few minutes and replugging it, and it didn't reset it. I'm just guessing it may take just a small static charge to reset whatever is hung in the electronics. I'm an electronic engineer, and I still don't have more than an unsupported theory about it.

And I'm not old. I'm just a kid of 64. It's my McCartney year. His, too. 😎
 
before you go and reinstall windows, try running a hard drive tester and see if it comes up with any drive errors. i use the drive tester on ubcd (http://www.ultimatebootcd.com/) and it's never let me down. although unlikely after just changing a cpu, the hard drive could possibly be dead. couldn't hurt to check before you go reinstalling operating systems and everything.
 
Verify you didn't have a shift in boot order in bios.
run a chkdsk /p from recovery console.

Where does the stop 7b happen? Is it before the splash screen or after the bar has moved a bit? There are a couple branches to the 7b troubleshooting tree and this is an important fork 🙂

Do NOT reload windows man! I'm the Jedi Master of fixing 7bs!
 
i've checked the boot order. haven't run chkdsk yet because none of the recovery options work and i need to get together a boot disk.
it happens during the splash after the bar has moved a bit.
 
Any XP/2003 CD is a boot disk... so use that, boot to recovery console (F10 at the first prompt, when it's fully loaded and asking you to press enter to continue), and log in, and then chkdsk /r...
 
Originally posted by: Harvey
Originally posted by: jadinolf
Harvey, solution 3 is something I've experienced many times.

Running your fingers across the pins may not be the cure but the fact you removed and replaced the cable certainly could be.

Nice to see you [ahem] old timer.
Click to expand...
I don't think so. I've tried just unplugging the cable, waiting a few minutes and replugging it, and it didn't reset it. I'm just guessing it may take just a small static charge to reset whatever is hung in the electronics. I'm an electronic engineer, and I still don't have more than an unsupported theory about it.

And I'm not old. I'm just a kid of 64. It's my McCartney year. His, too. 😎
Click to expand...

My McCartney year was 8 years ago.😎
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top