Boot problem solved........

[jeffk55]

REPOST:
I'm trying to find and answer or alternative to my "error". Brief history... MB/CPU and or power supply died last week. Short of troubleshooting everything I just went and upgraded all 3. Knew this would be no cakewalk but what the heck I'm down anyways. Well installed the components and did a repair of XP. Couldn't do it any other way because of the failure and inability to sysprep the sytem. Anyways I had a XPSP-2 CD that I made so I wouldn't have to download it. Was too lazy to make a integrated XP (my original is quite old) and XP SP2 boot disk. Well the repair went fine. Used the xpsp2 disc to upgrade the system but here is when it all went south...... Upgrade was dodgy but after some struggles I finally managed to complete it. Problem came on the next reboot... BSOD w 0x0000007e error (0xc0000005,0x00000000,0xf7a2f0c0,oxf7a2edbc). No other explaination as to the error. Tried safe mode and no go. Tried the other modes as well. Then tried VGA mode. XP-SP2 booted just fine. Everything works as designed except for the low res ect. Once corrected things appear normal. All components functioning. VERY strange. Of course now when I have to reboot I have to f8 it to use vga mode. Short of a re-install anyone have a clue????
2nd day running w/ no apparent problems once XP starts. Tried reboot w/ selective startup (no win.ini or sys.ini,no load startup items) but same error. Web help points to too many possibilities. Leaning towords a bad entry in registry or corrupt vga.sys file.
Did a slipstream disc today but don't really want to re-do due the OS is stable after boot.
Old board MSI w/ nVidia chipset and AMD-XP... New board Chaintech w/ nVidia3 chipset and AMD-64..............
My only possible mistake I made was when re-installing the OS the new board I did not install the RAID drivers since I was not using RAID or SATA for that matter.....
Hint,tips, ect needed badly.....

 

[jeffk55]

Addendum:
In system Config utility I marked basevideo so I don't have to f8 it all the time. Tried deleting drivers and reboot. No go. Reinstalling video drivers. No go. Tried a different video card. A quadro II. No go.
Getting more anoyed as I think this would be a "simple video problem" May be wrong.
Addendum2: Can now get into safe mode normally. Changed a BIOS setting which apparently was keeping something locked. Still no "normal boot" .

 

[jeffk55]

OK.. Tried fresh repair w/ slipstreamed XP. SAME problem... Only boots in VGA mode. Arrrgggh. May have to try a new video card. Quadro cards aren't working I guess.
Lost and sinking fast.....

 

[OdiN]

http://support.microsoft.com/?kbid=330182&sd=RMVP

Sounds like uninstall nvidia drivers in VGA mode, install generic VGA driver for the card, download and install latest VGA driver should do it.

EDIT - After reading a bit more of what you did...looks like it may be one of the other issues listed there. Try replacing your RAM...

Actually..if this is the first time with SP2 you may want to update your BIOS.

 

[jeffk55]

Thanks, RAM is Corsair Value RAM and was running just fine before original MB/CPU and or PS problems . Could be bad but... it appears to be only a video issue. Once booted system is stable, fast and no errors. I leave it 24/7 mostly so I assume if it were "other hardware" it would bite me at one time or another. Will pull one stick and test. Drivers installed now are fresh from nVidia. E-mailed Chaintech to see if there are incompatability issues w/ this card. Couldn't imagine there is but you never know. Think it's just some "sticky" registry value somewhere or I'm missing something in BIOS. Think this is going to be a bad problem. Until I feel it's strictly a Windows problem and/or I end up completely dead I don't want to do a full format and reload.
Looked into this at MS
http://support.microsoft.com/default.aspx?scid=kb;en-us;330182
Problenm is except for the board and CPU nothing is not a tested piece of hardware (running at least months before this) so hardware incompatabilities seems unreasonable unless it's the MB or AMD64 CPU. Since the computer runs fine after booting in VGA mode most of the other causes seem unlikely as well. Could be wrong though.
BIOS: Field Value
System BIOS Date 09/16/05

 

[OdiN]

You could also look for a BIOS update for the video card.

 

[jeffk55]

Never did a BIOS update on a video card. Just got done replacing the nVidia w/ a old S3 Trio PCI video card. Same problem.. Put the nVidia back in.

 

[OdiN]

It's gotta be something other than video card then. It could be the hard drive...hell it could even be the power supply. Really hard to tell at this point...you are down to troubleshooting by replacing parts with known good parts.

 

[jeffk55]

Thanks. I know this isn't going to be an easy one.
Brand new XCLIO 450W PS (retail version), Brand new Chainteck VNF3-250 MB (Retail version). Brand new AMD XP64 2800+ (retail ver) Will stress test the memory if I can find that floppy

 

[jeffk55]

Newest trys. Tried another re-install w/ only primary drive. Switched from CS to Master. Nothing there either. Same old same old. Also board seems to be having a problem w/ 1 stick of RAM. Can boot into BIOS but XP won't boot into VGA mode or any other. Put everthing back to "normal", 2 sticks Master/slave drive IDE ect and now at least I'm back to "boot to VGA". No suggestions? Wrote to Chaintech. Will see if they can help.

 

[jeffk55]

After digging through the registry it seems like the htkey_local machine..device map.. video
..device\video0 is pointing to some s3 video drivers. Haven't had that for 3 boards ago. Can't find any NVidia refrences in
ht_key_local_machine.. system..currentcontrolset.. control..video...
which is really strange.
Ignore this.... Does point to Quadro4 drivers... Must have been sleepy this AM

 

[jeffk55]

No word from MS or Chaintech re: this issue. Ordered a new graphics card today. Not hoping for too much but what the heck............

 

[evilphantomx]

had similar problem when I upgraded family...huge jump in system specs...all the $$$ went to the usual stuff...mobo,cpu,ram,HDD,ect...

after perfectly "normal" install of win xp pro....could only start in vga mode....sure it started but ran slow seemed glitchy video sucked...ect...

reinstalled and everything else I could think of...no go

well being family they said no prob just figure it out and come back then to fix it cause we can use it like this....well about two weeks later I ran accross a great deal on a 19"monitor for my wife...so took the 17" over to complete there"upgrade"(we never even thought about spending anything toward the monitor...the OLD 15"svga worked fine)

hooked it up and fired it up to see how it looked....and bingo....EVERYTHING WAS PERFECT
normal boot ...vid drivers finally working...even did a little O.C. on the vid card...runs like a top still today(put the old 15" back on as a test and problem came right back with it)

so just for S&G's ya might play around with the monitor settings or borrow another and give it a shot.....it was never in my head that it could even be the problem but hey what ya got to lose?

 

[jeffk55]

Doubt if my Mitsu 22" Diamond Pro 2070SB is part of the problem but at this point who knows. When in VGA mode the computer runs fine though I don't "game" it. Watched a DVD on it the other day and certainly not "jerky". Actually looked real good. Thanks anyways.

 

[jeffk55]

NEWEST TWIST IN THIS TALE.
With nothing to lose I tried a few of the other boot.ini switches. Guess what? By using only the SOS switch (no /basevideo) I get a "normal boot". albeit a bit slow sice XP has to go through whatever it does w/ that switch. Maybe a video timing issue at boot ? At least now I get full vid driver loading. At least I don't have to readjust my refresh rate/ resolution.
Did I mention I was confused

 

[jeffk55]

Just put in a newq 8x AGP nVidia card. Same problem. /sos mode works just fine as before. This mode only differs from normal mode by the absence of the startup moving white bars screen, Maybe that little "countdown" program is bad????.

 

[dclive]

Originally posted by: jeffk55
Just put in a newq 8x AGP nVidia card. Same problem. /sos mode works just fine as before. This mode only differs from normal mode by the absence of the startup moving white bars screen, Maybe that little "countdown" program is bad????.

Stick a non-nVidia card in there and tell us what happens.

 

[jeffk55]

Did earlier. An old s3 PCI card. Had the same thing. After all that I ran a drivecleaner for s3 and nVidia. Then reinstalled the nVidia card. Since the box works fine (except for the boot) I'm not too anxious to throw any more cash at it. I doubt if it's the video right now but I'm guessing. Using just the /sos switch loads the nvidia drivers which function fine.

 

[rasczak]

have you checked the bios and made sure your video setting was agp or pci?

 

[jeffk55]

Yes. that's set correctly. Pretty sure a refomat/reinstall is called for though this still bothers me. The fact it works fine w/ the /sos switch pretty well eliminates driver problems amd post bootloader problems. Looking into the bootloader steps in XP. Tried to run SFC /scannow but I get 23 files where XP wants to access the CD to find and replace files. Doesn't seem to work though. A search for "workarounds" led to editing the path in the register and copying the full i386 folder to root..
Still didn't work. Maybe a .net problem somewhere. My ntoskrnl file has a windows splash Network splash screen in it. Anyways I'm getting to the point of ignoring it till something else breaks. Sorry to say but I'm lost. Maybe Chaintech has an answer. The BIOS I have is new 9/05 and one right after a BETA BIOS by only a few days. Any odds they muffed the BIOS though I would expect more "problems" to pop up by now.

 

[dclive]

I wouldn't bother. The only thing SOS does is echo progress info (http://support.microsoft.com/default.as...s;833721#XSLTH3223121121120121120120); I'd just ignore it and let be.

If you want, though, I'll see if I can tell you what's going on and why it crashed - send me the minidump file(s) found in c:\windows\minidump, and run MPSReports (see my .sig) and send the resulting .cab file and I suspect we'll get a quick answer.

 

[jeffk55]

Oddly that's the answer I was hoping to receive. Seems like a non-problem problem if you get my drift. As to the minidumps.. none are generated. Last minidump I had was 04/05.
Tried every which way to get one per MS(change pagefile size ect) but no go. Think the problem occurs even before Windows will write one. Sounds odd but seems to be the only explaination I can come up with.
did you mean the cleanerlog??
log file
Minidump screen capture. As you can see there are none past 04. The zip file includes some even older ones that have been deleted. There are about 5 in total.
mini screen
The host thing I suspect is part of an IBM program like gotomypc. Darn thing wreaked havoc on my box years ago, but could be wrong. Not well identified by MS. Deleted it.

 

[jeffk55]

Originally posted by: dclive
I wouldn't bother. The only thing SOS does is echo progress info (http://support.microsoft.com/default.as...s;833721#XSLTH3223121121120121120120); I'd just ignore it and let be.

If you want, though, I'll see if I can tell you what's going on and why it crashed - send me the minidump file(s) found in c:\windows\minidump, and run MPSReports (see my .sig) and send the resulting .cab file and I suspect we'll get a quick answer.

Does this program (MS Antispyware) knock out programs once in a while? I had an "issue" the other day accessing my nVidia tab in Controlpanel: display: settings: advanced.. then no tab for nvidia w/ an error message "unable to initiate tab" blahh blahh blahh". NVidia was also missing from the taskbar. I just reinstalled drivers and all is well. Was wondering if that was 1 of the 2 programs/files I deleted w/ the first scan.

 

[jeffk55]

:BUMP:
Still looking for some advice on the so called "error" with a normal boot. Can still happily boot using \sos switch in boot.ini. Everything seems fine otherwise. Such a small and annoying problem but no easy solution so far. MS India or wherever is quite uselessly helpful but no direct fixes short of reinstalling everything. I foolishly insist there is an easier way (could be wrong though). Did run into someone w/ the same error ( except lat 2 addresses but similar enough all around)
but the thread died and no help given if they found a solution.
Thing still runs 24/7 except for the few times I test reboot to see if by some miracle (Christmas you know) it just goes away. No luck.
Similar thread
http://www.techspot.com/vb/showthread.php?p=220833#post220833

 

[dclive]

Well, you could always boot in recovery console, go back to the previous registry you had on the box (by moving the sam\software\system\security files from c:\windows\repair to c:\windows\system32\config, whilst backing up files previously there) and see if anything changes. Do you have a backup from prior to this problem that you could put the backed up registry in place?

Have you tried simply doing a System Restore to a date prior to the problem? Ah, I suspect a reinstall would wipe SR. Nevermind.