Tweet
Win2k drivers not SMP safe
This is just a hunch but I'm betting it is the problem I am running into with the new beta drivers. It runs GREAT on my dual CPU box and then it acts like a partial write from one CPU clobbers the data going to/from the videocard from the second CPU. A race condition somewhere within the driver or a missing spinlock somewhere.
It is fairly random when it will die on you but it usually leaves your box locked hard with a 'tornado leftovers' on your screen.
The system is rock solid with the drivers that came with RC3.. just less featureful
System:
Abit BP6 (100% rock solid under Be, Linux, W98 and Win2k with old drivers)
Does it whether or not the 2 CPUs are running at the default rate of 366mhx @ 2.0V or my normal running speed of 561mhz @ 2.0V
AGP : Matrox Mil. G200
PCI1: Hauppauge WinTV
PCI2: SB Live! (the only slot that doesn't share IRQs unfortunately)
PCI3: Intel PRO/100+ Management NIC 10/100
PCI4: Canopus V2
PCI5: Canopus V2
ISA1: Empty
NJ Bios on the BP6, w/ the 1.21 Win2k drivers for HPT366 chipset.
It is fairly random when it will die on you but it usually leaves your box locked hard with a 'tornado leftovers' on your screen.
The system is rock solid with the drivers that came with RC3.. just less featureful
System:
Abit BP6 (100% rock solid under Be, Linux, W98 and Win2k with old drivers)
Does it whether or not the 2 CPUs are running at the default rate of 366mhx @ 2.0V or my normal running speed of 561mhz @ 2.0V
AGP : Matrox Mil. G200
PCI1: Hauppauge WinTV
PCI2: SB Live! (the only slot that doesn't share IRQs unfortunately)
PCI3: Intel PRO/100+ Management NIC 10/100
PCI4: Canopus V2
PCI5: Canopus V2
ISA1: Empty
NJ Bios on the BP6, w/ the 1.21 Win2k drivers for HPT366 chipset.