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

system boot CRAWLS after verifying DMI pool data

L

Leeoniya

Member
so i have a winxp/sp2 system (xp333r and a 2200+ thoroughbred).

everything was working great, then a few days ago it started crawling during boot, right when it got to loading the os after verifying dmi pool data

i tested w/memtest86, no errors. also all pc-check tests pass fine.

i thought HD maybe, i installed another known good one.

installed clean os...but during drive examination/detection it took maybe 5 minutes, and took another 5 when detecting existing operating system, then the whole install took much much longer than usual, and the boot after the install was just as long as before....it was CRAWLING. it took maybe 10 mins to boot into OS, and after it was in the os, it was way too slow to be usable.

thought it was a bad ide controller, swapped drive to secondary, and then to ide raid controller....same issue, reset dmi in bios, it redetected, still nothing.

could it be cmos batt? doesn't seem like it is, i dont know. i'm ready to swap mb/proc 🙁

any ideas?

thanks,
Leon
 
freshly prepared:
brand spanken new slipstreamed sp2, updated w/RyanVM v2.1.2 (all post sp2 updates through sep. 17th, 2006) + slipstreamed WMP10

also latest BTS driverpacks (as of a couple of days ago):
massstorage+textmode, lan, chipset, proc

i booted from this cd on my main system to test it, and textmode flies through just fine. i have 2xRaptor raid-0 on an a8n-SLI premium (sil3114r5 controller), and it had no problem loading the textmode drivers for it and detecting the volume.

the biggest clue might be that there is a huge slowdown in textmode portion during (ide?) hardware detection, so it has absolutely nothing to do with windows and unlikely that it is the drivers that are preloaded with BTS.

it seems like a hardware problem, i dont know if it's bad bios, or a fried something else.

i installed some extra ram a couple of weeks ago, but it has been doing just fine, and like i said, memtest86 gives me no errors. other than that, i haven't touched a thing. it just started doing this out of nowhere.

Leon
 
Is DMA enabled on your HDs? Are all your chipset drivers up-to-date? Be careful with those driver packs ... sometimes the wrong driver can be loaded and cause strange system conflicts. You might want to try downloading/reinstalling each of your hardware drivers manually.
 
my thought would be either the drive controller or a drive, since you've tested the hard drive disconnect all optical drives if you have't already
test the cmos battery, check cmos reset instructions and make sure you're resetting it properly.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top