Ad:

Windows NT / 2000 / XP Discussion Thread
Unsolved
Views: 16068

You are currently viewing page 2 of this multi-page discussion thread; Jump to the first page

Apr 3rd, 2004

Re: Windows rubicks cube - BSOD

Quote originally posted by topcat unknown ...

Doh!No Luck - it must be cursed.

Tried the battery thing and the "cmos error" came up - continued with hdd that has XP on it and same stop screen. Rebooted with CD and gets to "Starting windows setup" screen and BSOD.

Also downloaded the bios update from the MB website and updated it and BSOD. Can't f' n beleive it.

Thanks for that chanto - but that is where i got most of my original info from - load of crap wasted a whole week going through those solutions. Still haven't been able to try the mass storage driver thing that you were talking about as there is no HDD driver on the giga website. There is Intel chipset drivers - INF and IIA ( i think ) but i dont know what they are.

I got a option menu at one stage which gave me safe mode options etc. I selected safe mode and it shows the drivers as they are loading - it gets to mup.sys and that is when the bsod comes up - dont know if it is mup.sys or the next driver making it crash.

Any new ideas will save me from throwing this computer into a wall

Well, you won't need the mass storage driver since XP has native support for the ATA-100 controller on the ICH4 chipset.

Have you checked the condition of the IDE cable? Any signs of damage? Try another IDE cable...

If all fails, let's try try the installation one more time, except deleting the partition table first...

1. hook up the IDE hard drive to your friend's P4 board
2. power up and get into the CMOS setup, set the boot priority to floppy first, cdrom drive next, and then hard drive; save and exit
3. find a DOS boot disk and boot up with this boot disk, run fdisk to delete all partitions on the hard drive; save and exit
4. place the XP installation CD into the CDROM drive, boot up the system with this CD
5. proceed with the installation, you'll be asked to choose the drive to install XP to...hit enter to select the only hard drive and select NTFS filesystem. Don't select quick format option, let it do a slow format
6. hopefully the installation will complete successfully

chanto!

Reputation Points: 45

Solved Threads: 1

Light Poster

Offline

39 posts
since Mar 2004

Permalink

Apr 3rd, 2004

Re: Windows rubicks cube - BSOD

Quote originally posted by topcat unknown ...

If what tallcool1 was saying works then i can I am happy to try that as the mother board provides Q Flash which allows me to upgrade the bios without going into the os.

Hi Tallcool1 - thanks for the info - I would like to trey what you suggested but the only jumper i was able to find was a password clear jumper. Do you think a bios update would have the same effect ( remove corrupt bios).
The motherboard is a Gigabyte GA-8GEM667K - can anyone confirm whether it has a cmos reset jumper

Do not re-flash the BIOS until we have cleared any other problems! I am about to write a brief article on the safest ways to do this, but it is not yet necessary in this case. BIOS contents and CMOS contents, while related, are separate issues; consider the BIOS as house wiring and the CMOS contents as light switches and you will have it about right. You wouldn't start yanking house wires if you had just a bad switch, would you?

In this case, what Gigabyte calls the Clear Password jumper actually clears (resets) the CMOS. Modern motherboards can hold settings with the battery removed for up to 12 hours, which is why the jumper is provided. Try that first.

TallCool1

Team Colleague

Reputation Points: 149

Solved Threads: 45

Practically a Posting Shark

Offline

865 posts
since May 2003

Permalink

Apr 6th, 2004

Re: Windows rubicks cube - BSOD

Hi, to everyone who has trierd to help me - thankyou, but i am no better off.

I bought a brand new motherboard and am still having the same problem.

I am only using the bare minimum
M/board (Gigabyte - GA-8VD667K)
CPU (P4 2.4 533 FSB)
HDD (Have tried 10G Quantum, 40G Maxtor, 2x80G Seagate)
n.b. all these hdd work on 2 other computer ( amd 1400, celeron 700)
RAM (Kingston 512 DDR 333 x 2 - 1 old and 1 new)

I am able to get win 98 working so I cant understand why XP keeps blue screening. I used a brand new M/B and a cleanly formatted HDD and tried to install XP ( I had the cd-rom connected at the time) and it BSOD before the install options came up. I used HDD with XP already installed and I get the start up options screen ( safe mode, start normal etc) - I went through and selected each option - same thing every time.

Is there anyone who can think of a solution

N.b - I got brand new cables with the m/b

topcat unknown

Reputation Points: 10

Solved Threads: 0

Newbie Poster

Offline

11 posts
since Apr 2004

Permalink

Apr 6th, 2004

Re: Windows rubicks cube - BSOD

Is that Windows XP a legitimate CD?

Did you use Fdisk to create a small partition for Windows 98?

Did you then use the Windows XP CD to create a partition, format it and install Windows XP?

It really sounds like you're using old Windows 98 techniques for Windows XP. That hardware should be fine. If it's not working, boot from the Windows XP CD, remove all partitions and create a new one(s). Install Windows XP formatting to NTFS.

If that works, then you know the harware compatibility issues are fine.

Remember - you don't need fdisk for Windows XP, only for Windows 98. XP has it all contained in the setup routine.

Catweazle

Team Colleague

Reputation Points: 229

Solved Threads: 149

Grandad

Offline

3,826 posts
since Mar 2004

Permalink

Apr 6th, 2004

Re: Windows rubicks cube - BSOD

I used 2 versions of XP thinking that might be the prob (one was legit and new version)

2 of the HDD are ntfs format with XP installed

I cant boot from the xp cd ( it doesn't get to the install options) unless I use another machine - and I tried doing that aswell ( removing partitions - create new ones and install in ntfs format ( not using quick format) )

I am trying to eliminate hardware compatibility by replacing items one at a time - the only thing i haven't changed is the cpu - but i cant understand how that could store info which would make it blue screen a XP HDD or setup cd.

Any other ideas - I exhausted my own

topcat unknown

Reputation Points: 10

Solved Threads: 0

Newbie Poster

Offline

11 posts
since Apr 2004

Permalink

Apr 6th, 2004

Re: Windows rubicks cube - BSOD

What Optical drive have you got. I'm betting it's the problem.

Catweazle

Team Colleague

Reputation Points: 229

Solved Threads: 149

Grandad

Offline

3,826 posts
since Mar 2004

Permalink

Apr 6th, 2004

Re: Windows rubicks cube - BSOD

Hi Cat weazle,

I thought of that - it is a liteon LD411s ( DVD burner)

but i disconnected it and tried to load xp from a hdd that it was already installed on,

could that be the problem - i have a spare cdrw which i can put in but i didn;t think of it when the hdd did nt work on its own

topcat unknown

Reputation Points: 10

Solved Threads: 0

Newbie Poster

Offline

11 posts
since Apr 2004

Permalink

Apr 6th, 2004

Re: Windows rubicks cube - BSOD

I'd be trying that. In fact, I'd be trying a 'vanilla' CD-ROM if one is available.

Some optical drives simply cause problems. Mitsubishi drives seem troublesome at times, and I've heard of DVD drives having installation problems as well.

But the problems you're having seem to point to a conflict between optical drive and the drive controller, or an incompatibility between motherboard and RAM.

Catweazle

Team Colleague

Reputation Points: 229

Solved Threads: 149

Grandad

Offline

3,826 posts
since Mar 2004

Permalink

Apr 6th, 2004

Re: Windows rubicks cube - BSOD

Quote originally posted by topcat unknown ...

I used 2 versions of XP thinking that might be the prob (one was legit and new version)

2 of the HDD are ntfs format with XP installed

I cant boot from the xp cd ( it doesn't get to the install options) unless I use another machine - and I tried doing that aswell ( removing partitions - create new ones and install in ntfs format ( not using quick format) )

I am trying to eliminate hardware compatibility by replacing items one at a time - the only thing i haven't changed is the cpu - but i cant understand how that could store info which would make it blue screen a XP HDD or setup cd.

Any other ideas - I exhausted my own

legit cd or not, it's not up to us to judge...we're here to help...

anyway, don't do what you're currently doing...that is, install xp on another system and take that hd to your system... it will blue screen.

have you checked out your memory? if not, get memtest86 either on cd or floppy and test them out...

if your xp cd does not boot, what you can do is...

1) boot up with a floppy with cdrom support (the 98 floppy/cd will do)
2) fdisk, format your hard drive
3) make a temp folder on the hard drive and copy all the files in the i386 folder from your xp into this temp folder
4) run smartdrv.exe if you can find it on your 98 cd/floppy
5) start the xp installation from your hard drive by running winnt.exe

remember not to install xp on another machine and swap hd...

chanto!

Reputation Points: 45

Solved Threads: 1

Light Poster

Offline

39 posts
since Mar 2004

Permalink

Apr 11th, 2004

Re: Windows rubicks cube - BSOD

Hi Chanto,

I tried what you said above - I created a folder called temp and copied all the files from i386 to that folder ( i did not copy the folder aswell just the files) and when i run winnt.exe it starts the install and asks where it can find the files. It defaults to the temp folder that it is in and when i hit enter it says it cant find the first file, choose ignore then cant find the second etc etc for all the files. At this point it doesn't give you an option to locate the file manually.

Am i doing this correctly or should i call the temp folder i386 or something.

It seems to be hardware incompatibility - the only thing i haven't been able to change is the cpu - is that capable of storing information in its cache which could be causing the problem.

Another idea i had was to use the mother board cd to install the drivers using win 98 then try upgrading to XP - does anyone know if this is a step forward or back.

topcat unknown

Reputation Points: 10

Solved Threads: 0

Newbie Poster

Offline

11 posts
since Apr 2004

Previous
1
Page 2
3
Next

This thread is more than three months old

No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.

Previous Thread in Windows NT / 2000 / XP Forum Timeline: pc freeze on games load when previously worked fine

Next Thread in Windows NT / 2000 / XP Forum Timeline: svchost.exe error

DaniWeb Message

Cancel Changes

User Name
Password