Bex RecordingManager.exe Error

[mojowp]

I would appreciate any help you could give me regarding this error.

I get this BEX error when downloading videos from YouTube using RealPlayer

BEX
Application Name: RecordingManager.exe
Application Version: 15.0.2.72
Application Timestamp: 4f274843
Fault Module Name: QuickTime.qts_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4e13ba08
Exception Offset: 61b9a9e9
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789



My OS is
Windows 7 Home Premium version 6.1 (build 7601: service Pack 1) 64-bit version
I have uninstalled and reinstalled RealPlayer and QuickTime, but I still have the problem.
Thanks

 

[zigzag3143]

A driver (probably RecordingManager.exe) is causing a memory exception. For specifics run these two tests.



These crashes were caused by memory corruption/exception (cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[mojowp]

Thanks for the quick reply. I just have a question before I run the tests. What is "overclocking"?

And, are these tests ones that a "non-computer-technical" person can run? I mean, I don't have the knowledge to disassemble my laptop and remove RAM sticks.

 

[mojowp]

Just to let you know that I have repaired the BEX error.
It was the result of a conflict with CODEC.

I uninstalled my most recently installed codec (which was MediaCoder) and uninstalled QuickTime.

I then installed Media Player Codec from Download.cnet.com.

Thanks for your time trying to help

 

[zigzag3143]

Just to let you know that I have repaired the BEX error.
It was the result of a conflict with CODEC.

I uninstalled my most recently installed codec (which was MediaCoder) and uninstalled QuickTime.

I then installed Media Player Codec from Download.cnet.com.

Thanks for your time trying to help

Almost any codecs will give you grief. Good players dont need them. Good job and good luck.