Why does my system "crash" when I try to open a CD?

[Guest]

Anytime I open a CD that I have saved data on, my system essentially
"crashes." I get two messages. First message is "The instruction
'ox7c918fea' referenced memory at '0x65636f82.' The memory could not be
written." I can either click ok to terminate the program or click cancel to
debug the program. THEN, I have another window that appears that says
"Windows Explorer has encountered a problem and needs to shut down. We are
sorry..." I can either tell Microsoft about the problem or End. During this
annoying process, my screen goes blank for a couple of seconds, regardless of
which box I click, and then goes back to normal.

What's going on here?

 

[Richard Urban]

I have seen corrupted information on a data CD or a music CD cause this. Try
a different CD. Does it work? Use your judgment as to what to do next! I
have had to throw out a few CD's over the years that did what you are
experiencing!

--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[Maurice N ~ MVP]

Provide a bit more details:

Select Start button/ select Run , then type in

eventvwr.msc<enter>
-- or Go to Control Panel / Performance and Maintenance/Administrative Tools >Event Viewer.

Review the sections and look for Errors or Warnings that match the time the event occurred. Double click---the information "may" give a clue.

One possibility is some RAM chips have gone bad.
Run a RAM memory test. MEMTEST86 is one such utility.
See http://www.memtest86.com/

 

[fmesiano1]

ox7c918fea fix

memory @ 0x00000010. The memery could not be written ) The solution is as follows:

1- Go to Control Panel
2- Administrative Tools
3- Services
4- go to the following Service : ( Windows Driver Foundation - User-mode Driver Framework ) Right Click then choose Properties ----> in the start up type choose Disabled.

Then reboot the system.

This should do the trick and stop the error from appearing at the login screen. I guess that Windows MediaPlayer 11 is the one responsible for this error