Comp randomly restarts after Mobo change

This afternoon I swapped mobos (from a KOB P4M266a to a brand new Gigabyte 8s661fxmp-rz). Installation went fine, as did a fresh new Windows install - but then when i tried to install the drivers for the board, the comp restarted shortly after loading the driver/selection screen off the CD - i managed to install a few by choosing then from the folders in explore view - but it won't run through the on-disk setup. I got this error message:
c:\WINDOWS\Mini110805-01.dmp
c:\DOCUME1\ROB\locals1\temp\wer1.tmp.dir00.\sysdata.xml
i deleted the Mini110805-01.dmp (whatever the fook it is) along with its friends, Minidump (an empty folder) savedump.exe, dumprep and anotherone, but they just come back, cept the .dmp number changes to 04 or different for that one file.
I've also reinstalled windows - a different version from a different CD, same problem

Other disks run fine, managed to install AVG/Zone Alarm/ Modem etc - but it still cuts out at random, no pattern showing at all.

Any ideas? :unsure:

(it's taken 5 goes at typing/posting this due to the restarts, and im a piss poor dislexik smeller, so plz excuses it all)

Try going to the mobo website and get the lastest drivers there. BTW, which drivers in particular is giving you grief?

Mr. Mulder is unable to reply from his computer so is using me as the go between :)

Reply: It shouldn't matter drivers are being used because it still does it at random anyway and the CD is TUCD VER.2.46

Ah good old Gigabyte. Right after I switched from an Abit to a Gigabyte, (mainly for PCI Express and 8 channel audio) it all went downhill from there. I've been having rebooting problems ever since. I even got 2 new sticks of ram (2x 512 MB) to replace and existing two 512's. What a waste of money. I still have problems. I tried a new, psu also (higher wattage/quality Antec PSU), and still the problems remain. As soon as I get a good flow of money from work, I'm getting rid of this POS motherboard and I never plan on getting or trusting Gigabyte again. Just sharing some of my experience with Gigabyte. .. :frusty:

Those files you quoted are generated by Windows when there's a system failure.
What we need is BSOD information.

When the puter resets, do you get a blue screen or does it just reset without warning?
If it resets without warning, right-click My Computer, select Properties, click the Advanced tab, click the Settings button in the Startup and Recovery section and disable Automatically restart in the System failure section, then OK your way out...
This should now present you with a bluescreen the next time the system fails, and you can make a note of the error codes and references that appear on it. Enter them into Google or ask more advice here.

I did as Chewie asked and got rid of Automatically restart, the BSOD said

"Driver_IRQL_Not_Less_Or_Equal" - then towards the bottom it quoted the file "usbohci.sys" along with it's address etc.

...so thinking it was the USB driver that's needed i tried installing it straight off the CD in explore view but got a screen up saying no - something to do with service packs, update to SP1 which i already have (might even have 2, not sure right now cos im at the g/f's computer) - then I went in to Device manager and tried to install it there using the wizard - but was told "The driver installation for this file is missing a necessary entry. Might be because the INF was written for Win95 or later" :blink:

...i managed to burn a screenshot to disk of device manager, took some doing though' :ermm:

http://img405.imageshack.us/img405/6...bfgvghv0ch.jpg

http://www.giga-byte.com/Motherboard...661FXMP-RZ.htm

the USB 2.0 driver is for Win2000 only - it says to update to SP1 OR 2 -Once again im fairly certain i have at least SP1 :ermm:

Right click on 'My Computer' and select Properties.

It will show you the version of Windows and what Service Pack is installed.

http://img235.imageshack.us/img235/4257/sp1kk.gif

Quote:

---

Originally Posted by Mr. Mulder

http://www.giga-byte.com/Motherboard...661FXMP-RZ.htm

the USB 2.0 driver is for Win2000 only - it says to update to SP1 OR 2 -Once again im fairly certain i have at least SP1 :ermm:

---

That's version 1.02, Version 1.03 (the one above it) appears to be universal.

Edit: sorry, I misread that, that's the SATA raid driver. But from the look of things you need that too.

I've never known a driver which was for Win2k which didn't work under XP, although as indicated you need at least SP1 for it to give you the proper benefits.

random restarts when you're using ur comp? sounds like your power supply's too shetty

Lynx: AFAIK USB2 drivers are required for Win2k but not for XP 'cos SP1 has them.

Mulder: I'd right-click and uninstall the controller with the alert, then restart and see if Windows installs drivers properly second time around.
Do the same for the RAID drivers.

I didn't have any service packs :blushing:

...I put back the old motherboard, downloaded a new version of Windows Pro with SP2, put back the new Mobo and then installed the newer version of windows - been using it for a couple of hourse now and it all seems to be working fine, all drivers are installed etc - thanks for teh help :01:

(still no Word hence the bad spelling)

I thought so. That's why I posted about how to check the version.

It still does it :frusty: :cry:

this time it says:

c:\DOCUME-1\rob\LOCALS-1\Temp\Werae79.dir00\mini111005-01.dmp
c:\DOCUME-1\rob\LOCALS-1\Temp\Werae79.dir00\sysdata.xml


No BSOD yet, just switched off Automatically restart, will post what it says after it happens again :dry:

BSOD info - nearly went the whole day without it happening :dry:

IRQL_Not_Less_Or_Equal

***Stop: 0x0000000A etc...

also stuff keeps shutting down with error reports - Opera - BSPlayer etc

http://aumha.org/win5/kbestop.htm

thanks lynx, nice link - tried most of the stufff they've said but it still happens though, with different Stop codes :no:

...the next thing on the list to upgrade is the RAM, could upgrading from crappy old ram to a fresh gig of GeiL make these problems go away? :ermm: Eventually, every piece of hardware will be replaced (cept the new mobo of course), and if it's a hardware problem then surely it would go away eventually, right? :unsure:

Make sure you used all screws for the motherboard and make sure its not warped, also check to see if you dropped a screw behind the mb could be that somthing shorting out, it sounds like the MB is not grounded properly, also check your cables to make sure the wires going into your power connectors are seated properly

Lastly check your fans to make sure they are running properly many sensers will shut the computer down if a fan in either the ps is not running or a cpu fan, also check to see that your heatsink for the cpu is mounted properly

If all that looks good you know ram is ok then RMA the MB

Good luck

Run Memtest86 overnight and see what happens.
That'll tell you if you needto change it.

When I had all my probems with y pc restarting of its own accord it turned out to be a fuck up on the cpu chip from manufacturing :(

I bought a new chip, put it in, and touch wood i haven't had a BSOD in nearly 10 months

o rly? it worked fine before the mobo change, it's been looked after well, tis a celeron D - not had any problems with it before so? :unsure:

the latest BSOD said something new, something about a page error and quoted the file sisgrv.dll - did some googling, downloaded a little app called error nuker which found the following two .dll errors/problems

http://img60.imageshack.us/img60/60/...ghgf1xt.th.jpg

can't choose the option to fix them (whatever that really does? :ermm: ) though cos i don't have a crack/keygen :frusty:


chances are the sisgrv.dll and missing cmmgr32.exe could be behind it all, right? :ermm:

It won't be cmmgr32.exe, that's the old connection manager which doesn't exist in the latest OS, but they forgot to remove the link to it in the registry. I'm not sure if it ever existed in XP, but if it did it was replaced in one of the service packs.

Sisgrv.dll is part of the sis graphics driver set. I've seen other mentions of that problem, with this solution:

Quote:

---

I found out that there was an updated driver from the video chipset maker that was not paassed along to the maker of the mobo.

---

Just google for sisgrv.dll, and you will find lots of mentions of similar problems. I suggest you try to find the latest drivers at sis.com

thanks lynx, i'll take a look :01: