New Mobo/CPU - a couple of odd reboots

[dilsburger]

Hello. I just upgraded to an ABIT KX7-333 and XP 2200+ - rest of system is...
512 DDR 2100
30GB Western Digital 7200rpm
PNY GF4 Ti4200
500 watt Powermax PSU
LG 12x CD RW/DVD
52xCD ROM
1 Floppy Drive
Windows XP Pro

This is the 2nd day up (PC came up fine after upgrade) but today I've experienced 2 strange reboots. The first when I pushed the physical eject button on my burner drive. The second when I clicked on my icon to dial the internet. The modem is PCI. (Intel) These were hours apart and the only time I've seen a glitch since the upgrade.

I played games for a few hrs last night - no problems and otherwise everything has been going smoothly.

Any ideas as to what could cause the crashes?

[saphalline]

Hmm... Did you reinstall Windows after you upgraded the mobo? Windows doesn't like mobo changes, well actually it often totally rejects them!

Did you check the burner's properties under device manager? Make sure the burner's IDE cable is hooked up correctly? Are the PCI modem's drivers up-to-date? Oh yeah, did you also re-update Windows online? Well, maybe hard to do that with no internet connection...

Best trouble-shooting rantings I can come up with right now.

[dilsburger]

Thanks. Acutally all is functioning as normal after each of the crashes. The modem & burner. In fact I used the burner drive to play a game on last night with no incident. It's just that I've never experienced such crashes before the upgrade or with previous configs I've had.

All my hardware drivers are up to date.

I didn't reinstall Windows because everything came up clean following the upgrade. I'll consider doing that, but I've never been a fan of "reinstalling" Windows. I may just wait awhile and see if there is a continuing pattern and also consider a fresh install...ugh...

[ranchdog]

Glitches like this are going to happen
after upgrading to a different Mboard
which utilizes a different chipset.

Even tho a person uses the install CD
that comes with a new board. Or d/l's the
drivers,etc. selectively from various
websites.

May not happen again for awhile then may
happen 8 times in a single day. As well
as other neat confusing errors.

The Southbridge chip functions better if it
only has one set of drivers to help it function.

By not doing a clean install or using the ENUM
folder method all of your previous Mboard drivers
etc. are just confusing things.

I notice you are using DDR2100 RAM. Be careful of
the RAM timings you have set in BIOS. Random re-boots
can be caused by trying to get to aggresive here.


RD.

[dilsburger]

Thanks RD. I hadn't touched the RAM timings but noticed that the default was set to manual and by changing it, which I did, will now read the DIMM parameters and use them instead of the customizable timing settings. Which may not change a thing but should eliminate doubt in that area.

I also disabled the video BIOS shadow which is recomended by PNY...

Time will tell, thanks again.

[dilsburger]

Thought I'd post back. I did a fresh install of Windows and the problem has become a little more solid and a lot more vague in nature.

After the OS, I installed the 4 in 1 drivers (latest) and then latest certified Nvidia dets.

Dialed the internet and within 5 minutes the PC hangs. (no more reboots, system just freezes) I can restart and run for hours until I shut down with no other occurances or glitches. I have done this several times with the same results.

Recap - 1st time up cold PC will hang in minutes. I don't have to start an app or dial up, it will just freeze. Hit the reset button and everything is fine including 3D games until shutdown hours later.

I'm game for any suggestions including SWAG's ;) (simple wild ass guess)

The mobo & cpu are new, no other devices are.... Thanks again.

[ranchdog]

Does your KX7 have the option for VDIMM adjustment?
(ram voltage)

If so, bump it to 2.6 rather than 2.5 (default)
and see if that will help.

Might move the RAM to different slots. As I read
it you have 1 stick of 512MB. What brand is this?

What do you have VCore set at for your 2200+ ?

Just kicking some things around.


RD.

[dilsburger]

RAM voltage is set at 2.55 (default) - I'll bump it up as you suggest.

The VCore is set at 1.65.

RAM - Oh man I forgot something here,,, first I mis-led as it is 256x2. Most important - when I originally upgraded to the DDR2100 I could only afford a 256 stick, Micron. So a friend lent me a 256 off brand which I do not know what it is. It worked fine on the old mboard, but,,,,, now? Hmmmm...

I am waiting on a 256MB match from the local retailer I deal with. Damn, sorry that slipped my mind. I'll pull the off-brand and see what happens in the morning....

My only experiences with memory problems were much more can I say aggressive? This problem only shows up on a cold start. For example I've been scanning, installing a few games and on the web for the last 2 hours... after my initial crash..... hmmm

[ranchdog]

For the KX7 the BIOS needs to be the Kx7b6 dated 8/22/2002
or the Kx79k dated 6/05/2002 version. The release BIOS
when the board initially came out didn't support the .13
micron chips.

Just as an elimination process, disconnect the ribbon cable
from the CD-ROM and then the CD-RW/DVD and see if you have to
use the re-set method.

Abit can have quirks with IRQ problems. Might move the
modem around to different slots. Maybe #5.

Mix-n-match of RAM doesn't usually play well. We've all
done it but problems arise. More so if one stick is generic.

I have to run this 2200+ at 1.70 Vcore (minimum) or cold
boot problems arise. But each Mboard seems to be different.

Have you bumped your AGP voltage a tad?

Here is a Link to Paul's Unofficial KX7-333 FAQ:

http://www.sudhian.com/faqs.cfm/fid/11.sud

You might browse thru there for something.


RD.

[dilsburger]

Hi RD, my bios date checked out ok.

After 3 successful cold boots today and since I failed on every cold boot after the upgrade until now I think I may have this one licked.

If you would have read my mobo manual to me, you know, the part where it says "In order to create a memory array we suggest that you populate DIMM4 to DIMM1 in that order" - I would have moved my memory from DIMM1 and 2 and put them in 3 & 4.:D :D :D

I never would have thought to do something like that. You have much more experience than me, have you heard of that before?

I may not be totally out of the woods but it's looking that way. Thank you many times for your insight and suggestions. I have them as reference and learned to look in those directions for future problems! :cool: