Blue Screen of Death after installing Replay Media Catcher 4.3.0

[dalevine]

On 8/12/2011 I upgraded to v 4.3.0. Since then I've experienced numerous BSODs.

I am running on Windows 7, SP1, 64bit. The machine is a Dell XPS 8300, on an i5-2400 with 8G RAM.

The problem may be related to the power state when the system goes to sleep; the bug check string = DRIVER_POWER_STATE_FAILURE.

I uninstalled RMP last night. It's too soon to determine if this makes the problem go away.

I cannot say for certain if the problem was caused by RMP but it did install a device driver, appliand.sys, and I believe there is another one (I don't know its name.), and badly behaving drivers can cause BSODs.

I can upload a miniDump if that will help determine if the driver is the problem.

[kwondra34]

I have the same issue -- just got it for my birthday and only having it on my Asus N53JF-XE1. My server (thats just running win 7 ultimate) doesnt have this issue. i think its related to the NDIS driver but i cant remmeber why I think that.

can we get some help?

[RoadKing007]

On 9/18/2011, I upgraded to Replay Capture Suite. After installation, I discovered that every time I put my system to sleep, the computer would power down. I discovered I had the "Blue Screen of Death". I restored my system to a couple of days earlier which deinstalled all of the modules in the Replay Capture Suite. After this action was taken, the problem went away.

I am running Windows 7 Home premium, SP 1, on a 64 bit Hewlet Packard computer (HPE-590t). I have a 3.33ghz intel i7 cpu, 12 gb memory, two internal 1tb hard drives running raid 0 and an external 2tb hard drive.

Today, I reinstalled Replay Capture Suite and will be monitoring my computer to see if it shuts down after being put to sleep.

Prior to installing Replay Capture Suite, I installed FreeCorder..........I deleted it from my browser when my system experienced numerous hangs requiring rebooting the computer. So far, anything I've touched from Applian has caused me problems. In the event I get another BSOD, I'm pulling the plug on Applian and getting my money back.

[RoadKing007]

Update on today's prior post...........After reinstalling Replay Capture Suite, I attempted to put my computer to sleep without problems. I clicked on the sleep button and the screen went blank giving the appearance that the computer was asleep. However, the computer never went to sleep and remained on. After some period of time, the computer shut down. After powering the computer up, I received another message indicating that I had the Blue Screen of Death (BSOD) once again. I did another recovery to an earlier date, Replay Capture Suite was removed and my computer now goes to sleep properly. I haven't heard back from tech support as yet so I plan to place my credit card payment on hold and request that I receive a refund.

[Jeff Lenney]

Hi Guys

We're looking into this now with the software driver programmer. Thanks for hanging in there :)

[Archlord]

Same thing here as well. Not only for v4.3.0 but even for the older versions as well. I am currently Running Windows 7 SP1 x64 and I tried to install the older version but they all ended up with the same "Blue Screen of Death" (BSOD). The BSOD doesn't happen right away, it occurs on the Next Reboot and as soon as Windows 7 starts detecting for Network Connection, the BSOD occurs(so, its some problem with Network Driver).

After some checking I removed Applian Technologies from the Trusted Center(Just open any MS Office Program --> File --> Options --> Trust Center --> Trusted Publisher --> Remove Applian

Next, I reinstalled Replay Media Catcher 4.3.0 again and this time when it asked me for NDIS5 Driver installation, I didn't accept it. The setup didn't complete successfully, but Replay Media Catcher was installed. I rebooted the system and this time the BSOD didn't occur and when I ran Replay Media Catcher(RMC), it worked fine, but the Recording Process was unable to start as the appliand driver was missing.

So, the problem for this BSOD is the NDIS5 Driver Installation...

My Question is...is NDIS5 Necessary?? I think NDIS6.2 is the latest version available, isn't it? :s anyway, I hope this info helps the Dev Team in rectifying the problem.


P.S. Please rectify it asap..we are missing this awesome application because of this bug :( and I hope the Applian Staff respond to this reply and keep us posted on any development and any other backdoors to avoid this problem.


~ Archlord

[RoadKing007]

Update on prior post...........I finally was finally contacted by tech support requesting further information regarding this problem. I was sorry to inform them that I canceled my purchase of Replay Capture Suite and had already received confirmation from customer service that I would receive a credit for the original purchase price. Bottom line was that I didn't have the time to be a beta test site for a product that should have worked in the first place. It's unfortunate that the BSOD problem exists in certain environments because I really liked the product for the short time I used it.

[Jeff Lenney]

If you're having BSOD issues with RMC, please READ BELOW and then Contact Applian Technical Support (http://www.applian.com/support-products.php) with the below information for assistance.

A BSOD is rarely related to our applications but in order to determine if there is an incompatibility with some other software or driver on your machine, we will need the following information collected from your system:

1. Download the BSOD Dump & System File Collection utility from this link: http://jcgriff2.com/0x2/Windows_NT6_BSOD_v3.03_jcgriff2_.exe

2. Right mouse click the exe that you just downloaded and select "Run As Administrator"
It may take up to 10 minutes to finish and will create a new folder in "My Documents" called: Windows_NT6_BSOD_jcgriff2

3. Once the utility has finished, click the Start button and type Command Prompt in the search field. This will open a Command Prompt window. At the Command Prompt, type perfmon /report . Type exactly as seen or paste it in. Making sure to include the space before the /. A report viewer will appear and begin to create a report. When it is finished, save the report with File > Save As as a html document.

4. Place the folder created in step 2 (Windows_NT6_BSOD_jcgriff2 located in My Documents) along with the html file created in step 3 into one zip file and attach it to this support ticket. If you don't know how to zip a folder - here's how: locate the folder that you want to zip, right click on the folder and select send to>compressed (zipped) folder. This will create a zip file of the same name. Don't forget to add your report (html file) from step 3 to the zip as well.

5. Please answer the following questions:

- Are you running 32 or 64 bit Windows?
- Is this an original installation of Windows or has it been re-installed?
- Is this an OEM or full retail version of Windows? OEM means that Windows came pre-installed when you bought your computer. Full Retail means that you purchased Windows and installed it.
- What is the age of system (hardware)?
- What is the age of OS installation (have you re-installed the OS?)

Once we have received this report we'll examine the contents and get back to you as soon as possible. We appreciate the effort to collect the information required.

[kwondra34]

I confirm that:


The BSOD doesn't happen right away, it occurs on the Next Reboot and as soon as Windows 7 starts detecting for Network Connection, the BSOD occurs(so, its some problem with Network Driver).

It's definitely network related and he's right -- it occurs on the next reboot. I have replay media catcher 4.3.0 on two systems and one is fine -- its a driver incompatability issue I'd guess with the (forced) version of NDIS.

I updated drivers for wireless/wired via Atheros website (For both cards) and the problem still exist. I can confirm this happened on earlier versions as well. I should probably create a support ticket but I'm very busy. I'll wait and see if this gets solved my someone else and if I'm still not seeing any progress, I'll submit my dump, etc.


Initial answers to your questions since we're already deep in this:

- Are you running 32 or 64 bit Windows? -- 64 bit
- Is this an original installation of Windows or has it been re-installed? -- original
- Is this an OEM or full retail version of Windows? OEM means that Windows came pre-installed when you bought your computer. Full Retail means that you purchased Windows and installed it. -- retail
- What is the age of system (hardware)? -- March 2011 build
- What is the age of OS installation (have you re-installed the OS?) -- less than 2 months. reinstalled OS originally thinking maybe it was something related but its not.

Thank you.

[Jeff Lenney]

Hey Guys

Please submit a ticket with this information. It won't help us without the dump file we're requesting. Thanks! :)

[Jeff Lenney]

Hey Everybody

We spoke with the developer of the driver and here is what he said about the few dump files we DID send him - not saying that everybodys is the same, but the issue so far was NOT with Replay Media Catcher.

Just to clarify, the two we have been provided by users so far show that it is virtual box crashing their machine. If you would like to submit dump files for analysis then you are most welcome to and should contact support with the information requested in my longer post above.

I analyzed these crash dumps. They are not directly related to WinpkFilter (the filter/drive in Replay Media Catcher). The crash is rather caused by VBoxNetFlt . If you search the Internet for VBoxNetFlt and DRIVER_CORRUPTED_EXPOOL you will be able to find a plenty amount of the similar BSODs. The quick analyses below:


1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000000000003105, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800027fbdd3, address which referenced memory

Debugging Details:
------------------

Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VBoxNetFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExFreePoolWithTag+43
fffff800`027fbdd3 418b45f0 mov eax,dword ptr [r13-10h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: fffff880009fc720 -- (.trap 0xfffff880009fc720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000003115
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800027fbdd3 rsp=fffff880009fc8b0 rbp=fffffa800d7ded10
r8=0000000000000000 r9=0000000000000000 r10=fffffa800dec8020
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!ExFreePoolWithTag+0x43:
fffff800`027fbdd3 418b45f0 mov eax,dword ptr [r13-10h] ds:ffffffff`fffffff0=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800026cc1e9 to fffff800026ccc40

STACK_TEXT:
fffff880`009fc5d8 fffff800`026cc1e9 : 00000000`0000000a 00000000`00003105 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009fc5e0 fffff800`026cae60 : 00000000`00000002 00000000`00000000 00000000`00000002 fffffa80`0d7dc020 : nt!KiBugCheckDispatch+0x69
fffff880`009fc720 fffff800`027fbdd3 : 00000000`00000000 fffff880`033583bc fffffa80`0c391b60 00000000`00000002 : nt!KiPageFault+0x260
fffff880`009fc8b0 fffff880`01677195 : fffffa80`0dec8810 fffff880`009fc9e0 00000000`00000000 00000000`00003115 : nt!ExFreePoolWithTag+0x43
fffff880`009fc960 fffff880`03392aca : fffffa80`0d7ded10 fffffa80`0d7ded10 fffffa80`0dec8810 fffffa80`0d2a41a0 : ndis!NdisFreeMemory+0x15
fffff880`009fc990 fffffa80`0d7ded10 : fffffa80`0d7ded10 fffffa80`0dec8810 fffffa80`0d2a41a0 fffffa80`0d8a6190 : VBoxNetFlt+0x3aca
fffff880`009fc998 fffffa80`0d7ded10 : fffffa80`0dec8810 fffffa80`0d2a41a0 fffffa80`0d8a6190 fffffa80`0d2a41a0 : 0xfffffa80`0d7ded10
fffff880`009fc9a0 fffffa80`0dec8810 : fffffa80`0d2a41a0 fffffa80`0d8a6190 fffffa80`0d2a41a0 00000000`00000000 : 0xfffffa80`0d7ded10
fffff880`009fc9a8 fffffa80`0d2a41a0 : fffffa80`0d8a6190 fffffa80`0d2a41a0 00000000`00000000 fffff880`0173264e : 0xfffffa80`0dec8810
fffff880`009fc9b0 fffffa80`0d8a6190 : fffffa80`0d2a41a0 00000000`00000000 fffff880`0173264e fffffa80`0d8a6100 : 0xfffffa80`0d2a41a0
fffff880`009fc9b8 fffffa80`0d2a41a0 : 00000000`00000000 fffff880`0173264e fffffa80`0d8a6100 fffffa80`0d7ded10 : 0xfffffa80`0d8a6190
fffff880`009fc9c0 00000000`00000000 : fffff880`0173264e fffffa80`0d8a6100 fffffa80`0d7ded10 fffffa80`0d7dc8d0 : 0xfffffa80`0d2a41a0


STACK_COMMAND: kb

FOLLOWUP_IP:
VBoxNetFlt+3aca
fffff880`03392aca ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: VBoxNetFlt+3aca

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: VBoxNetFlt

IMAGE_NAME: VBoxNetFlt.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e4911c5

FAILURE_BUCKET_ID: X64_0xC5_2_VBoxNetFlt+3aca

BUCKET_ID: X64_0xC5_2_VBoxNetFlt+3aca

Followup: MachineOwner
---------

[Radiograbber]

My PC is running Win 7 Pro 64 bit and Replay Media Catcher 4.3.2 works fine for me, apart from the occasional hiccup with incomplete iPlayer radio downloads, which I think is a problem at the BBC's end not mine. I'm not exactly an expert on such matters, but I thought I'd chip in to suggest the people suffering BSODs might try changing their antivirus and firewall.

Earlier this year I gave up trying to get Comodo Internet Security to actually allow certain programs to access the internet and installed AVG and Zone Alarm instead. I then had a lot of random BSODs over the next few months and some research eventually led me to the conclusion that I would be better off using Microsoft Security Essentials and Windows Firewall, which I had previously spurned as they surely couldn't be as good as "proper" internet security software made by specialists. Well, it turns out they actually work very nicely after all and my PC has been much better behaved since I made the switch about a month ago.

As they say though, your mileage may vary. To be honest, knowing there are so many ways that computers can go wrong, I'm continually astonished that they work at all.

[monkeyboy96]

It appears it might be an issue of conflicting drivers by Applian and Oracle (VirtualBox). You can either choose to uninstall one of the two or follow the instructions below for a work around.

In the bottom right corner of your desktop click the network icon, then click 'Open Network and Sharing Center' and click 'Change adapter settings'. Then right-click the connection you use for the internet (for example LAN or wireless) and select properties.

If you want to use RMC then deselect the VirtualBox Bridged Networking Driver and click OK. If you then want to use VirtualBox then reselect that option, deselect the Applian Network Driver and click OK. You can have only one of these two selected at any time and thus can only use one program at a time (actually you can still use VirtualBox, just not to connect to the internet).

[monkeyboy96]

I've also notified people on the VirtualBox forums, see here (https://forums.virtualbox.org/viewtopic.php?f=6&t=45521). Is there any chance of some official communication between the two software development teams? Thanks =]

[Bk5223]

I was getting the blue screen of death after reboot from installing replay media catcher but I also had oracle vm so I uninstalled it since I do not use it anymore. But im still getting this issue after I press record. Could Not Load Driver appliand. This can happen if the product has previously been uninstalled and then reinstalled again before rebooting the machine. Every-time I do reboot I get the blue screen of death. I'm only having problems with this brand new computer but my old sony vaio on vista worked fine.

*****FIXED******
Worked when I ran the program as administrator.

[Jeff Lenney]

Hi All,

IMPORTANT:

Its not conflicting drivers at all. It is the Virtual box driver crashing - Virtual box need to fix their driver. A quick search of the internet (http://www.google.com/#sclient=psy-ab&hl=en&safe=off&source=hp&q=virtualbox+crashing+2011&pbx=1&oq=virtualbox+crashing+2011&aq=f&aqi=&aql=1&gs_sm=e&gs_upl=12816l13534l1l13723l5l4l0l0l0l0l0l0ll0l0&bav=on.2,or.r_gc.r_pw.r_cp.,cf.osb&fp=dc20b2672385f007&biw=1440&bih=668) will tell you that it crashes all the time.

The driver we use is 3rd party and is used by many other applications - not just ours.

Thanks! :-)

Edit: Just to clarify - This issue has nothing to do with Replay Media Catcher, and is purely with VirtualBox.

Just trying to keep the information flow accurate - Thanks! :)

[monkeyboy96]

I've never had VirtualBox BSOD on me before and it doesn't BSOD when I just use it with the Applian Network Driver disabled or uninstalled, likewise I've never had an Applian product BSOD on me before and when the VB driver is disabled the internet works fine, no BSOD. I've had both products installed for a while and they ran fine but both have updated recently and that is when the problems arose. Hence my conclusion that this is as a result of conflicting drivers.

Can you please point out the flaw in my logic there? They run separately and used to work together but after recent updates they cause problems together.

[Jeff Lenney]

Hi MonkeyBoy,

1. The virtualbox driver is crashing and bsod'ing the machine, not the one Jaksta/RMC uses.
2. A driver should coexist happily with all other drivers on the machine and not crash and bring down the machine.
3. The virtual box driver does not coexist happily with other drivers, it crashes and BSOD's machines and is is not working as a driver should.
4. A google search of "virtual box bsod" lists articles as old as 2008 => There have been problems with virtual box for quite a while.
5. Please contact Virtual box support.

I agree that Virtual Box does not work well with RMC, but that is an issue that Virtual Boxes driver is causing - not the one used by Replay Media Catcher (which by the way is used with MANY other applications and not just RMC).

I hope this helps clear things up.

[Tricki]

Hi,

I get the dreaded BSOD running armcp.exe directly, however when I run it through Director it runs fine. I know this doesn't help either of us directly but it may shed some light for the support team.

Cheers

[rplummer]

I purchased a brand new Gateway (All-In-One) computer (x64 - Windows 7) for my wife a couple of months ago. We finally got tired last month of dealing with the occasional, but non-periodic BSOD events (prior to installing either VB or RM) that ended up being a conflict between anti-virus and identity management programs we installed as recommended by Comcast. Symantec support finally resolved that. A couple of weeks ago, I installed VB on the machine, but hadn't yet configured any VMs. I had been using the RM suite on my Toughbook (Professional XP) for a few years, very happy until about a year ago. I've also been using with much success VB on that machine. The toughbook having > 30k hours, began having issues I attributed to old age (inverter on main screen dying, frequent BSOD). The BSOD's appeared to be correlated with whenever I used the RM apps, so I figured I would move all of my RM work over to my wife's machine, since it's a x64, multi-processor and relatively fast.

I installed the RM suite onto my wife's machine this past weekend. She's been using her email, FB, etc. apps w/o problem the weekend. I noticed today sluggishness and rebooted. That's when holy he.. broke out. Everytime I would reboot the machine either in Normal or Safe-Mode-networking, a few seconds after logging in - BSOD. After going back in plain safe-mode, I uninstalled the RM Suite and an open source genealogy program (just installed a week or so ago) and the BSOD problem disappeared.

I searched and found this thread. So it appears from my experience that there is an incompatibility, although it may be with a VB driver, that is exaggerated when using RM. First, since I'm haven't begun using VB on her machine yet, will uninstall VB, reinstall RM and let you know what I experience. I'll also research, if I find the time what exactly the VB driver problem is and if there's a workaround.

[episickness]

does the Oracle VB also apply to winxp? because i get bsod if i use RMC for more than 10 min using an winxp machine. And i can't seem to find the virtual box in my network properties windows. if it's the same driver messing up my machine, where do i find it to shut it down?

thanks.

[Jeff Lenney]

Hi Epic

Please submit a ticket to tech support - we will need the following information collected from your system:

1. Download the BSOD Dump & System File Collection utility from this link: <http://jcgriff2.com/0x2/Windows_NT6_BSOD_v3.03_jcgriff2_.exe>

2. Right mouse click the exe that you just downloaded and select "Run As Administrator"
It may take up to 10 minutes to finish and will create a new folder in "My Documents" called: Windows_NT6_BSOD_jcgriff2

3. Once the utility has finished, click the Start button and type Command Prompt in the search field. This will open a Command Prompt window. At the Command Prompt, type perfmon /report . Type exactly as seen or paste it in. Making sure to include the space before the /. A report viewer will appear and begin to create a report. When it is finished, save the report with File > Save As as a html document.

4. Place the folder created in step 2 (Windows_NT6_BSOD_jcgriff2 located in My Documents) along with the html file created in step 3 into one zip file and attach it to this support ticket. If you don't know how to zip a folder - here's how: locate the folder that you want to zip, right click on the folder and select send to>compressed (zipped) folder. This will create a zip file of the same name. Don't forget to add your report (html file) from step 3 to the zip as well.

5. Please answer the following questions:

- Are you running 32 or 64 bit Windows?
- Is this an original installation of Windows or has it been re-installed?
- Is this an OEM or full retail version of Windows? OEM means that Windows came pre-installed when you bought your computer. Full Retail means that you purchased Windows and installed it.
- What is the age of system (hardware)?
- What is the age of OS installation (have you re-installed the OS?)

Once we have received this report we'll examine the contents and get back to you as soon as possible. We appreciate the effort to collect the information required.

[PNutts]

I am having a blue screen issue on a new Windows 7 x64 build and have not installed Virtualbox on it. It ran for two days until I installed RMC 4.3.2. I'll use the information above to open a ticket and start a new forum thread if any forum interaction is needed/wanted, :) unless support wants me to continue here.

[Jeff Lenney]

I am having a blue screen issue on a new Windows 7 x64 build and have not installed Virtualbox on it. It ran for two days until I installed RMC 4.3.2. I'll use the information above to open a ticket and start a new forum thread if any forum interaction is needed/wanted, :) unless support wants me to continue here.

Please submit the ticket with the log file - there is no way to attach those files to this forum and we'd like to keep them private to protect your safety :) Thanks

[barbidurable]

Really usefull thread. I'm also a virtual box user as a replay media catcher user (in fact jaksta user but these 2 applications seem to belong strongly). I had this problem of constant crashes when using virtualbox since I installed replay media catcher. Disabling applian network driver in my connection tab solved my problem.

[nogero]

Add me to the list. I had VirtualBox installed on my new Dell XPS, Win7/i7/12GB/2TB/64bit. Immediately after installing the latest Replay Suite my system BLUE SCREEN OF DEATH (BSOD) every time I rebooted, after about 5 minutes, even without running any apps.

I would like a short term workaround if possible. If I disable the Applian network driver will Applian products still work? If so, how do I disable it?

On the short term I am going to remove VirtualBox, but that is a major app and I really need both apps.

[Jeff Lenney]

Add me to the list. I had VirtualBox installed on my new Dell XPS, Win7/i7/12GB/2TB/64bit. Immediately after installing the latest Replay Suite my system BLUE SCREEN OF DEATH (BSOD) every time I rebooted, after about 5 minutes, even without running any apps.

I would like a short term workaround if possible. If I disable the Applian network driver will Applian products still work? If so, how do I disable it?

On the short term I am going to remove VirtualBox, but that is a major app and I really need both apps.
You can try running RMC INSIDE VB, other than that - contact VB and ask them to fix this issue :)

[sjm]

I suffered through BSOD incidents when sleeping or hibernating my computer for nearly two years before finally tracking this culprit down to Applian. A full account of my experience is posted at "http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/f93ce928-ec63-4878-871b-10a64e6817be/?prof=required" posted under the heading "DRIVER_POWER_STATE_FAILURE (9f) - BSOD - Multiple offending drivers"

My computer never had Virtual Box installed. For me, the best solution was giving up on having Media Catcher on my notebook computer and moving it to a PC, where it works fine. For some reason, the network drivers that Applian installed on my HP Elitebook 8530w appears to have caused the BSOD issues. Once I uninstalled the hidden networking devices installed by Applian, the computer has gone through several sleep/wake cycles with no issues. Previously, it would BSOD every few times I'd put it to sleep. My resolution was as follows:

I uninstalled Applian Media Catcher, but hidden network devices remained (in device manager, on the view tab, select to view hidden devices, and Applian devices will show up). These could not be uninstalled by device manager, even as an administrator, but I found a procedure for editing the registry to remove the devices at http://www.annoyances.org/exec/forum/winxp/t1041235229 . This string recommended editing the registry key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E972-E325-11*CE-BFC1-08002BE10318}" by deleting all of the Applian devices in the registry key, I was able to uninstall them from windows device manager, which seemed to resolve the problems.

I did create a case with Applian for this issue and agreed to provide them with requested dump information, but the link that they sent for the dump file preparation didn't work.

[kbachler]

I have a brand new Lenovo X230 running Win 7 Professional 64 bit. After installing RMC I did not get a BSOD, but the computer would not reconnect to wireless networks on waking. Removing RMC using "Your Uninstaller" (which also removes registry entries, etc.) returned the functionality. There is no Oracle VirtualBox or other Oracle product installed that I know of. My Network drivers include - Shrew Soft Lightweight Filter (a VPN adapter), DNE Lightweight Filter, Virtual PC Network Filter Driver, QoS Packer Scheduler, File and Printer Sharing.

I'll also fill out a ticket.

[Jeff Lenney]

I have a brand new Lenovo X230 running Win 7 Professional 64 bit. After installing RMC I did not get a BSOD, but the computer would not reconnect to wireless networks on waking. Removing RMC using "Your Uninstaller" (which also removes registry entries, etc.) returned the functionality. There is no Oracle VirtualBox or other Oracle product installed that I know of. My Network drivers include - Shrew Soft Lightweight Filter (a VPN adapter), DNE Lightweight Filter, Virtual PC Network Filter Driver, QoS Packer Scheduler, File and Printer Sharing.

I'll also fill out a ticket.

Ticket received and responded to - please make sure you answer all the questions and include the requested dump file

Thanks! :)

[byoungsd]

I have a brand new Lenovo X230 running Win 7 Professional 64 bit. After installing RMC I did not get a BSOD, but the computer would not reconnect to wireless networks on waking. Removing RMC using "Your Uninstaller" (which also removes registry entries, etc.) returned the functionality. There is no Oracle VirtualBox or other Oracle product installed that I know of. My Network drivers include - Shrew Soft Lightweight Filter (a VPN adapter), DNE Lightweight Filter, Virtual PC Network Filter Driver, QoS Packer Scheduler, File and Printer Sharing.

I'll also fill out a ticket.

I have the exact same setup wit the same issues. Has this issue been resolved?

[pmatt]

I also had this problem, and as it turned out, in my case it was an incompatibility between the network drivers for MediaCatcher and VirtualBox. If I disabled the network driver for one, the other would work fine, but with both enabled, BSOD. Hope this helps someone.

[JohnHind]

I think I have found a workaround for this:

Right-click on the network taskbar icon and bring up "Network and Sharing Centre". Click on your primary network connection (probably "Ethernet"). Click on "Properties".

As long as "VirtualBox Bridged Networking Driver" is above "Applian Network Driver" in the list, both can be simultaneously enabled without problems. If the Applian driver is first, the computer will crash unless one of the two is disabled.

As far as I can discover, the only way to reverse the order if the Applian driver is first is to make sure RMC is installed before VirtualBox. You can achieve this by un-installing VirtualBox, restarting the computer and then re-installing VirtualBox.

Not ideal, but does prove it is VirtualBox at fault not Applian, and enables both to be used at once.

Hope this is helpful!