J
jimbak3
Long story short.
I upgrade a 110% stable MSI Neo4 Plat w/ AMD 3000 single core to an
X2 3800.
Windows does its thing, updates the HAL to dual core and
recognizes the new chip.
Problem: Getting hard lockups ( no blue screen, just total freeze)
when browsing. Multiple load pages or certain sites only. Easy to
reproduce.
Did ALL the patches. I said ALL. Crash with AND without the dc
patches . Dont ask me about patches. They are worthless in this case.
Did not do a reinstall of windows, cause I have no intention of
reinstalling to upgrade to this.
NOW>>>>> This is the bitch of it. Whatever BUG is in the windows
dual core drivers, STAYS IN THE SYSTEM even when the single core is
returned to the motherboard. Read that twice, cause its a biggie.
Looks like XP does not update the HAL back to single core on its
own. So those drivers remain, and it recognizes that only one core is
installed.
But the crashing is exactly the same with the single core chip . I
have not seen this factor reported anywhere in hundreds or thousands
of posts. so how can we blame the X2 chip if its NOT EVEN IN THE
FREAKING MACHINE.
As soon as I revert Windoze back to the single core HAL, the system
is again 100% stable.
The dual core drivers, at least in my setup are FARKED. I doubt I
will be able install this chip. No way to trace the problem.
I upgrade a 110% stable MSI Neo4 Plat w/ AMD 3000 single core to an
X2 3800.
Windows does its thing, updates the HAL to dual core and
recognizes the new chip.
Problem: Getting hard lockups ( no blue screen, just total freeze)
when browsing. Multiple load pages or certain sites only. Easy to
reproduce.
Did ALL the patches. I said ALL. Crash with AND without the dc
patches . Dont ask me about patches. They are worthless in this case.
Did not do a reinstall of windows, cause I have no intention of
reinstalling to upgrade to this.
NOW>>>>> This is the bitch of it. Whatever BUG is in the windows
dual core drivers, STAYS IN THE SYSTEM even when the single core is
returned to the motherboard. Read that twice, cause its a biggie.
Looks like XP does not update the HAL back to single core on its
own. So those drivers remain, and it recognizes that only one core is
installed.
But the crashing is exactly the same with the single core chip . I
have not seen this factor reported anywhere in hundreds or thousands
of posts. so how can we blame the X2 chip if its NOT EVEN IN THE
FREAKING MACHINE.
As soon as I revert Windoze back to the single core HAL, the system
is again 100% stable.
The dual core drivers, at least in my setup are FARKED. I doubt I
will be able install this chip. No way to trace the problem.