Blue Screen Errors with Kyro II when accressing Floppy
Hi all, I'm posting this on behalf of a friend, so I've not seen this happen. Here is the issue. Whenever he attempts to access the floppy drive under Win2k he gets the following BSOD error: *** STOP 0x0.
Hi all,
I'm posting this on behalf of a friend, so I've not seen this happen.
Here is the issue.
Whenever he attempts to access the floppy drive under Win2k he gets the following BSOD error:
*** STOP 0x0....
KMODE_EXCEPTION_NET_HANDLED
*** Address 80004001 based at 80001000
DateStamp 3a248773r - hal.dll
This only happens when using drivers for the Prophet 4500 (Kyro II) graphics card.
If no Kyro II drivers are install and it's ran in standard VGA then these errors do not appear.
The specifications of the PC in question are:
AMD TBird 1.3Ghz
ABit K7TA-RAID
528MB RAM
Now this all happened when he attempted to update the motherboard BIOS.
He upgraded to the latest BIOS, reset the BIOS as the instructions recommend and then this problem started appearing.
He then downgraded the BIOS back to the original version and he's still getting exactly the same problem.
After each BIOS flash he reset the BIOS to default settings as per instructions.
So to me it looks like a possible BIOS setting issue, IE something has changed when the BIOS was set to 'default'.
Anybody have any ideas?
Thanks.
I'm posting this on behalf of a friend, so I've not seen this happen.
Here is the issue.
Whenever he attempts to access the floppy drive under Win2k he gets the following BSOD error:
*** STOP 0x0....
KMODE_EXCEPTION_NET_HANDLED
*** Address 80004001 based at 80001000
DateStamp 3a248773r - hal.dll
This only happens when using drivers for the Prophet 4500 (Kyro II) graphics card.
If no Kyro II drivers are install and it's ran in standard VGA then these errors do not appear.
The specifications of the PC in question are:
AMD TBird 1.3Ghz
ABit K7TA-RAID
528MB RAM
Now this all happened when he attempted to update the motherboard BIOS.
He upgraded to the latest BIOS, reset the BIOS as the instructions recommend and then this problem started appearing.
He then downgraded the BIOS back to the original version and he's still getting exactly the same problem.
After each BIOS flash he reset the BIOS to default settings as per instructions.
So to me it looks like a possible BIOS setting issue, IE something has changed when the BIOS was set to 'default'.
Anybody have any ideas?
Thanks.
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
Forgot to mention.
He's using Win2k SP2 as the only installed OS.
As said before, this didn't happen when he first installed the system, only when he upgraded the BIOS, however it's now still happening with the old BIOS re-installed.
He's using Win2k SP2 as the only installed OS.
As said before, this didn't happen when he first installed the system, only when he upgraded the BIOS, however it's now still happening with the old BIOS re-installed.
In device manager, what type of PC is his listed as? If the ACPI got changed with it somehow, that could be affecting it.
Are the using the same IRQ? Or any other resources? Or near each other? That is the only thing I could think of. Maybe trying to get new drivers for the Kyro II. Or talking to the motherboard manufacture and BIOS manufacture.
Hope this helps.
Hope this helps.
