Really need help from you guys!!

[Hellwardk]

Hi

I've had some seriuos problems with my cd drive for some while now, without actually knowing what the problem is. Each time I insert a cd, the bluescreen of death pops up, showing this message:

(0xc0000005, 0x8A3A2C45, 0x8E83B67c, 0x00000000)

fltmgr.sys - Address 8A3A2C45 base at 8A382000, Datestamp 47918a6a


Windoes said it was the antivirusprogram that caused the problem, and they said that I should update it to fix the problem. And so I updated Norton. When finished updating, a new bluescreen pops up, now with this message:

IRQL_NOT_LESS_OR_EQUAL

Windows now said it was a camera that caused the problem; the driver wasn't working. I installed a driver some time ago; just before this problem came.

I don't know how to uninstall this driver, because it's not listed anywhere. I downloaded it, and is worried that it was a virus(?). Anyway, I need help of you guys to solve this problem, and i'm not very good at computers as you guys guessed

This is the driver I installed:
http://www.nodevice.com/driver/DCR-TRV9E/get39740.html

It's a driver that is for XP, but i ran it on vista, could that have caused the problem?

 

[PC eye]

Apparently the driver isn't compatible with the newer version of Windows. Usually when an XP driver won't work in Vista the installer for it won't even run however. Vista drivers downloaded and installed on XP being the older version would cause problems while Vista mainly ignore XP drivers since they are unusable and unloadable.

A driver for a usb plugin for a camcorder doesn't explain the other errors being seen when the autoplay prompts fails to appear when inserting a disk into the optical drive. That's a Windows related problem there not from simply downloading the wrong driver for a usb device. Those are less intrusive unlike video or sound drivers which would see immediate problems when the wrong set goes on.

The "fltmgr.sys" file is an MS file or virus posing as one. It sounds more like a needed background service was stopped for some reason if that file was damaged or now missing explaining the BSODs you have been seeing.

 

[Hellwardk]

Apparently the driver isn't compatible with the newer version of Windows. Usually when an XP driver won't work in Vista the installer for it won't even run however. Vista drivers downloaded and installed on XP being the older version would cause problems while Vista mainly ignore XP drivers since they are unusable and unloadable.

A driver for a usb plugin for a camcorder doesn't explain the other errors being seen when the autoplay prompts fails to appear when inserting a disk into the optical drive. That's a Windows related problem there not from simply downloading the wrong driver for a usb device. Those are less intrusive unlike video or sound drivers which would see immediate problems when the wrong set goes on.

The "fltmgr.sys" file is an MS file or virus posing as one. It sounds more like a needed background service was stopped for some reason if that file was damaged or now missing explaining the BSODs you have been seeing.

Ok, makes sense..

But do you have any solutions? Is there any way that I can find out what the problem is and fix it?

Thanks for respons anyway!

 

[PC eye]

I've had Vista since beta and haven't run across that error seen with the fltmgr.sys file in XP either since it's a common file there too. The "IRQL_NOT_LESS_OR_EQUAL" error on the other hand can be caused by a hardware fault as well as a software glitch of some type. That's an old one going back to the Windows NT days.

There is one free online scanner to see if you somehow got hit with a more XP orientated virus or trojan using that file name or simply a system file seen at http://www.file.net/process/fltmgr.sys.html

The MS file itself is the file filter manager by purpose likely the thing that tells you when a driver is digitally signed. The event viewer as well as taking notes on any driver error seen on a BSOD are the most helpful steps since you can go from there in finding the actual cause as well as a solution. For using the event viewer follow the steps here.

To view error event logs

You must be logged on as an administrator to perform these steps.
1. Open Event Viewer by clicking the Start button

, clicking Control Panel, clicking System and Maintenance, clicking Administrative Tools, and then double-clicking Event Viewer.

If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
2. In the left pane, double-click Applications and Services Logs, navigate to the specific program that had an error, and then review any error events for that program.
3. Double-click an event to view a description and to find links to more information.

http://windowshelp.microsoft.com/Windows/en-US/Help/10cb4f91-7883-4e61-aebc-03e303c7064c1033.mspx