Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Win7 Pro x64 IPBusEnum Locks System


25 Oct 2009   #1

Win7 x64 Pro
 
 
Win7 Pro x64 IPBusEnum Locks System

I have recently (yesterday) upgraded from XP 32 bit to Windows 7 Pro 64-bit. I have done a clean install. After installing most of my applications I decided to install Steam (for my games.) After installation my system immediately locked up, no BSOD just a frozen screen and cursor. After a hard reboot my system seemed to operate fine, until I attempted to run Steam, then it would lock again. Another hard boot not only showed that running Steam locked the system but seconds after opening Windows Live Mail would lock the system as well. After another hard boot I viewed the system logs and would find that the following error occurred before the system lock each time:

the application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{C97FCC79-E628-407D-AE68-A06AD6D8B4D1}
and APPID
{344ED43D-D086-4961-86A6-1106F4ACAD9B}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Even if I remove Steam my system will continue to throw this error whenever I attempt to run Windows Live Mail (WLM). I even tried to do a system restore to a point in time before I installed Steam and I got the same thing. That didn't work, WLM still locked the system quickly after launch. I even tried removing and re-installing all Windows Live software to no evail. I also tried a restore from image as I made an image after installing all win updates on a clean install, still got the error and lockup. I tried many things to fix this and several re-installs to be sure it didn't happen until after i installed Steam. I have no idea what to do from here, I have done as much troubleshooting as I can to verify that the issue does not arise until after the Steam installation. I found this post on the forums but I still couldn't change any IPBusEnum settings: Event ID 10016 -- DCOM permissions error
Maybe a better explanation of how to change the IPBusEnum would help (not that this was a bad explanation but rather just not enough hand holding for me i guess.) Any help or suggestions would be greatly appreciated as I would like to run Steam on my system since I have a few games that require its installation.

Thanks

My System SpecsSystem Spec
.

26 Oct 2009   #2

Windows 7 Professional 64 bit
 
 

J0SH44,

I can tell you that WLM may have something to do with this error. Steam does not create that error. If it does then something on my system is creating the same error. I don't have Steam -I don't even know what that is.

I have EXACTLY THE SAME ERROR on my system also. I went from XP 32 bit to Win 7 Pro 64 bit via an upgrade. Same CLSID and same APPID. however it does not cause a system lockup. Everything seems to run perfectly well.

Followed the instructions to grant permission to that APPID and all selections were grayed out.

It seems that error might have something to do with a wireless network printer? I don't know yet, I'm still researching it.

I would think that that type of error you're having with a locked up system is probably a device or a device driver.

If I find out what it is I'll let you know. If you find out what it is let me know.

Thanks.
My System SpecsSystem Spec
26 Oct 2009   #3

Win7 x64 Pro
 
 

you say
It seems that error might have something to do with a wireless network printer? I don't know yet, I'm still researching it.
I use a Brother Wireless Laser Printer, the 2170W.
Yeah, i am no longer thinking STEAM is the culprit but it is a trigger. That may be the case for WLM as well. Maybe neither one is the cause but both trigger the problem. What really sucks for me is that the system just locks. It happened overnight and i don't even have WLM or STEAM installed on this build. My system locked at 2:04 AM this morning and it didn't log a single event until i restarted it. Any info you find would be great. I will keep posting any info that I find.


Just looked on my system and I have not installed the printer yet. It is on my network and my computer can see it but I have not installed it or printed to it. I have installed Windows 7 so many times I get it mixed up what I have installed and what I have not installed.
My System SpecsSystem Spec
.


26 Oct 2009   #4

Windows 7 Professional 64 bit
 
 

Have you tried MSCONFIG -> disabling everything in the Start up tab, Services Tab -> check mark "Hide all Microsoft Services" and then disabling the rest of them. Reboot and see if it goes away. If it does it's something in Start up or in Services. If it doesn't then it's probably a device.

I'm making an assumption here that you're cooling fans are running efficiently. I've seen this happen when the system overheats and just locks up and no error is thrown.
My System SpecsSystem Spec
26 Oct 2009   #5

Win7 x64 Pro
 
 

Have not tried that yet, i may go to that. The only problem is that it has only happened once when WLM or STEAM hasn't been installed and it took a very long time for it to happen (I messed around on the system for hours without trouble and then decided to go to bed.) The system didn't freeze until after that while it was idle for a good twenty minutes. The only way i know to force the freeze to happen is to install and run WLM and STEAM.

As for cooling, CoreTemp shows me at about 50 degrees for all the cores. I set my AV scanner to scan the system, Started up an MPEG video, started converting AVI to MPEG files, started ripping CDs to MP3s, tranfering a large 15GB file between disks and was playing a slide show all at the same time for a mini load test. The system didn't even flinch and as for temps they actually dropped, I am thinking the cpu fan must have noticed the increased load and rev'd up. I was thinking about running Prime95 just to see what that does.
My System SpecsSystem Spec
26 Oct 2009   #6

Windows 7 Professional 64 bit
 
 

It doesn't look like a cooling issue.

I see ASUS has a memory update 10/20/2009 for your board. I don't know what that means, but check it out if you want.
My System SpecsSystem Spec
26 Oct 2009   #7

Win7 x64 Pro
 
 

That is just a Qualified Vendor List of tested memory and their settings. I do see there is a BIOS update but it looks like it is just for the logitech G15 keyboard. Also I should mention that Prime95 pretty much errors out instantly on my system. The best I have had so far is four threads running (out of the eight possible) after one minute. The other threads just error out. Here is the results.txt file:
[Mon Oct 26 12:56:40 2009]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.48828125, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4921875, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

I think I will throw memtest86+ at the system again and see how that goes unless anyone knows a better/different memory testing program. I am still not sure that hardware is the cause for sure (since it is reproduceable running WLM or STEAM) but I do need to eliminate any hardware problems. I also wish i knew how to edit that IPBusEnum permissions to test that.
My System SpecsSystem Spec
26 Oct 2009   #8

Windows 7 Professional 64 bit
 
 

Just use the Memory Test that's included in Windows 7. It's in Administrative tools. It does a good job.

Can you find the "Stress.txt" file that it refers to anywhere on your system?

WLM and Stream probably cause that Hardware to fail quickly, but it really looks like you've got a device, including a memory stick, that's pretty sick.

I've run Prime95 and no errors. I believe that Prime95 stresses the Processor and Memory with an overload of bit streams.

My first guess then would be either the processor, the processor cooling fan, or a memory stick. Since you've had a lock up at idle, I doubt that it would be the cooling fan, because the processor is not under stress. That would lead me to believe that either the processor or a memory stick is at fault.

Are you over clocking?

If you are, set it back to default and see if that resolves it.
My System SpecsSystem Spec
26 Oct 2009   #9

Win7 x64 Pro
 
 

No OC on my part but something isn't acting right, that is for sure. My sticks pass memtest86+ (left running for 13 hours) and the Windows Memory Test that is included with Windows 7. The stress.txt file isn't much, doesn't have information relative to my specific test, just the test in general. I did have to set my memory speed in the BIOS as OCZ ships their memory at a lower speed to ensure it is more likely to be compatible with the system. I have my memory set at 1600mhz 8-8-8-24 @ 1.64v which is what the memory is rated to handle. I was throwing errors in memtest until I got these setting correct and eliminated the one bad stick.
I just ran the sticks through memtest86+ again and they didn't show any errors after one pass (8 tests), so memtest and Windows Memory Test are not finding any errors yet. So that could mean my Proc or HDD, both of which Prime95 stresses a little. Maybe WD has some tools for me to test my HD. I just wouldn't think that a HD would cause such problems.Otherwise it would seem like it is down to my proc.
My System SpecsSystem Spec
26 Oct 2009   #10

Windows 7 Professional 64 bit
 
 

I followed the instructions at: Event ID 10016 -- DCOM permissions error
and I no longer have that error showing up.

All I did was copy {344ED43D-D086-4961-86A6-1106F4ACAD9B} and did a search in Regedit. Gave the Local user and Network names full control and it went away.

Now I have some stupid DNS error that my wireless printer is trying to ping my ISP, whatever settings there are are wrong somewhere.

I found this about upping your processor voltage:
OC E6850 - Overclockers Forums

Maybe try dropping 1600 to 800 mhz and set the rest to default or auto and test it.

It's all pointing to either the Memory or Processor causing the problem. Memtest may show everything is OK with the sticks, but voltage and speed may be wrong for the processor or the processor is not set right for the memory. 64 bit does add another twist to this that x86 would be fine with.
My System SpecsSystem Spec
Reply

 Win7 Pro x64 IPBusEnum Locks System




Thread Tools



Similar help and support threads for2: Win7 Pro x64 IPBusEnum Locks System
Thread Forum
Windows 7 System locks up BSOD Help and Support
Win7 Home x64 - Locks at Personalized Settings Installation & Setup
System Hard Locks for Gaming BSOD Help and Support
win7 locks up installing ITUNES Performance & Maintenance
System locks up at random times during the day BSOD Help and Support
System hangs/locks randomly BSOD Help and Support
System locks up. Can I track with logging? Hardware & Devices

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:54 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33