The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
When I try to run it at normal speed (1400mhz, 10.5x133), the bios posts fine, windows starts to load, and then I get a BSOD shouting KMODE_EXCEPTION_NOT_HANDLED, and not specifying any driver file. Running Win2k pro, which the MS online help site doesn't seem to cover for this message..
It did boot windows this morning after I told it manually to use 133mhz fsb for the cpu and ram, but then it randomly rebooted and I had to set it down. It's not stable at anything above 100mhz fsb, 3dm 2k1 crashes within seconds of starting or it reboots itself.
Running it on an Asus A7V266 with 1002C bios - tried to update to 1003, but I can't boot to dos - tried 5 boot disks, they all either lock up, or I can't type anything. This bios revision supposedly supports the XP, and the bios recognises it fine, only when it starts booting windows it finds a problem. The palmino/t-bird jumper on the board is set correctly, and I can't see any other jumpers that it would help to change.
Any ideas as to what's causing this and any steps to take, short of a reformat (nowhere to back up 30gb of data to just now) would be greatly appreciated.
Spec: win2k pro, athlonxp 1600, 2x 256mb crucial pc2100, asus a7v266, gf2mx200, no pci/isa cards in.
Cheers,
Phil
All the problems seem to be with the NT kernel...error is always in ntoskrnl.exe, which is used (at least in part) by 2k/nt/xp, still haven't seen any reports of conflicts like this with 9x...dare I go back to using WinME/98?
As you have had the CPU exchanged it's pointing at either memory, motherboard or PSU. I know that the PSU setting sounds funny, but if the new setup is draining more power than the PSU can handle it may be reducing power output rather than overheating, as your machine has restarted itself once already, it may have been this that caused it.
Memory sounds the most obvious problem though, however it could also be a simple compatibility issue with you motherboard. I have an Athlon Thunmderbird 1.4ghz 266fsb, 256Mb PC2100 and a QDI Kudoz 7 motherboard, when I try to install Windows XP, it just doesn't support the board(possibly the Via266 chipset) and therefore gives me all the same types of errors you are recieving.
Although it does sound more like a memory/motherboard issue in you circumstance.
When I try to run it at normal speed (1400mhz, 10.5x133), the bios posts fine, windows starts to load, and then I get a BSOD shouting KMODE_EXCEPTION_NOT_HANDLED, and not specifying any driver file. Running Win2k pro, which the MS online help site doesn't seem to cover for this message..
It did boot windows this morning after I told it manually to use 133mhz fsb for the cpu and ram, but then it randomly rebooted and I had to set it down. It's not stable at anything above 100mhz fsb, 3dm 2k1 crashes within seconds of starting or it reboots itself.
Running it on an Asus A7V266 with 1002C bios - tried to update to 1003, but I can't boot to dos - tried 5 boot disks, they all either lock up, or I can't type anything. This bios revision supposedly supports the XP, and the bios recognises it fine, only when it starts booting windows it finds a problem. The palmino/t-bird jumper on the board is set correctly, and I can't see any other jumpers that it would help to change.
Any ideas as to what's causing this and any steps to take, short of a reformat (nowhere to back up 30gb of data to just now) would be greatly appreciated.
Spec: win2k pro, athlonxp 1600, 2x 256mb crucial pc2100, asus a7v266, gf2mx200, no pci/isa cards in.
Cheers,
Phil