Win2K and Abit KA7 - IRQL BSOD
Hi. . I tried Win2K Pro a few weeks ago, but I had to get rid of it because I kept getting: ***STOP: 0x0000000A (0xC104027E, 0x00000002, 0x0000000, 0x8049F771) IRQL_NOT_LESS_OR_EQUAL ***Address 8049F771 base 80400000, DateStamp 384d9b17 - ntoskrnl.
Hi..
I tried Win2K Pro a few weeks ago, but I had to get rid of it because I kept
getting:
***STOP: 0x0000000A (0xC104027E, 0x00000002, 0x0000000, 0x8049F771)
IRQL_NOT_LESS_OR_EQUAL
***Address 8049F771 base 80400000, DateStamp 384d9b17 - ntoskrnl.exe
blue screen...
I don't know what it is, but I can usualy use my PC for like a day before it
goes and locks up like that. I have taken my hardware out of my system
leaving my modem, graphics card, hard drives and cdroms in the system and
reinstalled - still got the problem.
System:
Abit KA7 motherboard with TY BIOS
128Mb of PC100 CAS2 ram
Creative Anialator Pro (AGP 4x, fast writes on - used Detinator 6.50
drivers)
LinkSYS 10mbit PCI (used drivers installed by Windows)
Sound blaster live 1024 (used drivers installed by windows and latest
Creative drivers)
WinTV Go! (used latest WinTV drivers)
Diamond SupraExpress 56i V90 modem (used Diamond drivers)
Maxtor 20Gb (Master Primary)
Quantum 6.4Gb (Slave Primary)
LG 48x CDROM (Master Secondary)
Iomega ZipCD 4x4x24x (Slave Secondary)
I was using the Via4-1 4.28beta drivers, and I think i used the system
without the 4-1 drivers and it still locked up...
Any ideas? - I really liked Win2K, but this problem is causing me to use
WinME
------------------
Regards
Stephen Harding (AKA - SplanK)
I tried Win2K Pro a few weeks ago, but I had to get rid of it because I kept
getting:
***STOP: 0x0000000A (0xC104027E, 0x00000002, 0x0000000, 0x8049F771)
IRQL_NOT_LESS_OR_EQUAL
***Address 8049F771 base 80400000, DateStamp 384d9b17 - ntoskrnl.exe
blue screen...
I don't know what it is, but I can usualy use my PC for like a day before it
goes and locks up like that. I have taken my hardware out of my system
leaving my modem, graphics card, hard drives and cdroms in the system and
reinstalled - still got the problem.
System:
Abit KA7 motherboard with TY BIOS
128Mb of PC100 CAS2 ram
Creative Anialator Pro (AGP 4x, fast writes on - used Detinator 6.50
drivers)
LinkSYS 10mbit PCI (used drivers installed by Windows)
Sound blaster live 1024 (used drivers installed by windows and latest
Creative drivers)
WinTV Go! (used latest WinTV drivers)
Diamond SupraExpress 56i V90 modem (used Diamond drivers)
Maxtor 20Gb (Master Primary)
Quantum 6.4Gb (Slave Primary)
LG 48x CDROM (Master Secondary)
Iomega ZipCD 4x4x24x (Slave Secondary)
I was using the Via4-1 4.28beta drivers, and I think i used the system
without the 4-1 drivers and it still locked up...
Any ideas? - I really liked Win2K, but this problem is causing me to use
WinME
------------------
Regards
Stephen Harding (AKA - SplanK)
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
I have same Mobo/ same bios and no problems. Don't know what that BSOD means, but here a few suggestions for next install:
- You are talking about a clean install, aren't you ?
- Don't overclock (before the system is stable, that is)
- "untweak" the system: lower your memory clockings in bios to conservative ones - Take off the fast writes and 4x from your graphics card, lots of people report trouble with VIA chipset and 4x. The best way is to revert the whole bios back to factory settings.
-leave the creative drivers out (w2K gives you sound)
See if you get a stable system with the above, not installing any extra drivers etc for devices that already work with the native W2K drivers.
When you get a stable system, back it up (best way is Drive Image or Ghost) and add the tweaks one at a time
BTW, the new 4in1 1.29 drivers released yesterday or old ones (non beta) might work better. You must have them ready on a floppy and install them (twice) when the installation asks for them.
H.
- You are talking about a clean install, aren't you ?
- Don't overclock (before the system is stable, that is)
- "untweak" the system: lower your memory clockings in bios to conservative ones - Take off the fast writes and 4x from your graphics card, lots of people report trouble with VIA chipset and 4x. The best way is to revert the whole bios back to factory settings.
-leave the creative drivers out (w2K gives you sound)
See if you get a stable system with the above, not installing any extra drivers etc for devices that already work with the native W2K drivers.
When you get a stable system, back it up (best way is Drive Image or Ghost) and add the tweaks one at a time
BTW, the new 4in1 1.29 drivers released yesterday or old ones (non beta) might work better. You must have them ready on a floppy and install them (twice) when the installation asks for them.
H.
