Problem with my Floppy disk


When ever in insert  a floppy my system in going into blue blank screen and it show some
error like this



it take 100 seconds and after that it shutdown

could u tell me what i need to do for solving the problem

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

By the sounds of it your floppy is accessing memory is not support to, or the memory it needs is beeing used by a different program, this is what happens when to programs try to access the same memory address. If you reboot your system and try to access the floppy does it work? Is this a recent problem? verify what programs you have running in the back ground and maybe close one at the time, do you have another floppy drive you can swap with?

10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

nader alkahtaniConsultantCommented:
The file that is in error message : NVCOARC5.SYS either it is illegal file (may be  random-created file by a virus ) or you   misnamed the file .thus, scan online from viruses here 

or give me the correct name of the file that appeares with the error message ....however after scan from viruses read this to troubleshoot the problem :

How to Troubleshoot a STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED Error Message

This article was previously published under Q275678
This article describes how to troubleshoot a "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message.
A "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message is a common type of STOP error message you may receive on a Windows NT-based computer. A "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message indicates that an error condition was detected by the kernel and Windows NT was unable to continue running because of this error condition. The types of problems that can cause a "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message are very similar to the problems that cause a "STOP 0x0000000A" error message, such as bad pointers, invalid addresses and other types of access violations. The STOP 0x0000001E bug check identifies an error that occurred in a section of code where no error handling routines exist. Note that most exceptions are generated directly in the section of code that is running.

The top four lines of a STOP 0x0000001E generally appear as:

The four hexadecimal parameters after the STOP code (0xAAAAAAAA, 0xBBBBBBBB, 0xCCCCCCCC, 0xDDDDDDDD) have the following meanings:
0xAAAAAAAA is a code that identifies the exception that was not handled.
0xBBBBBBBB is the address at which the exception occurred.
0xCCCCCCCC is the first parameter of the exception, and sometimes this is another address in code.
0xDDDDDDDD is the second parameter of the exception, which can vary in meaning.
Interpreting the Parameters
Usually the exception address identifies the driver or function that caused the problem. Always note this address and the date of the driver or image that contains this address.

The first parameter is a Windows NT error code, and all error codes are defined in the Ntstatus.h file (which can also be found in the Windows NT 4.0 SDK). The first parameter tells you the type of error.

The second parameter is also important because it tells you in what code module the error occurred. This can frequently point to an individual driver or piece of hardware that is at fault, which will generally be listed on the third line of the STOP screen.

The last two parameters vary depending upon the exception that has occurred. Typically, you can find a description of the parameters included with the name of the error code in the Ntstatus.h file.

If there where no parameters to the error code, these will be 0x00000000.

For example, in the following STOP error message, an access violation (0xC0000005) occurred in module Srv.sys, which is the kernel mode server service:

STOP: 0x0000001E (0xC0000005, 0xFCA733B9, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED 0xC0000005 from 0xFCA733B9 (0x0, 0x0)Address FCA733B9 has base at FCA70000 - SRV.SYS
Note that no parameters went with this error code.
How to Troubleshoot a "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" Error Message
Try to replace the driver that is identified in the STOP error message, either with a known good copy from your installation media, or with an updated version from the manufacturer.
Disable the driver that is identified in the STOP error message or any newly installed drivers.
Verify that any new hardware or software is properly installed. Disconnect the new hardware or replace it to see if this resolves the issue.
If you have a video driver that was not supplied with the operating system, try switching to the standard VGA driver or a driver that is compatible with the operating system.
View the following Microsoft Hardware Compatibility List Web site to verify that all your hardware and drivers are compatible with the operating system:

Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM check. If this is a new installation of the hardware or software, contact the manufacturer for any requires updates for drivers or firmware.
Disable all filter drivers, such as remote control software, antivirus programs, backup programs, and so on.
The information in this article applies to:
Microsoft Windows NT Server 4.0 Terminal Server Edition
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Professional
Microsoft Windows NT Workstation 4.0
Microsoft Windows NT Server 4.0
Microsoft Windows NT Server, Enterprise Edition 4.0;en-us;275678
Try to boot from a bootable floppy in your floppy disk drive. Does it work successfully? If yes, restart your system and remove your Floppy Disk Drive and also remove your Floppy Disk Controller via Hardware Manager to end in a fresh driver installation after restart. I also had a similar problem with an Elitegroup Mainboard. The failure was finally fixed after a BIOS upgrade.
PAQed - no points refunded (of 500)

Community Support Moderator

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.