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: BSOD after "Remote procedure call failed and did not execute"

20 Nov 2011   #1

Windows 7 Home Premium x64
BSOD after "Remote procedure call failed and did not execute"

-Windows Home Premium x64
-Windows Vista initially installed; Dell provided a windows 7 Installation CD once it came out.

Hardware was bought ~December 2009. Installed Windows 7 once in 2010 and once earlier this year.

When I tried to make the System Health Report, it came up with "The system cannot find the specified path." I'm currently running everything from Safe Mode with networking since if I tried to boot up regularly, the system locks up with little CPU usage, explorer.exe fails and I get the error "The remote procedure call failed and did not execute" when I try to open any folder, the computer locks up again before finally BSOD.

My System SpecsSystem Spec
21 Nov 2011   #2

Win 7 Ultimate 64-bit. SP1.


These crashes were caused by memory corruption.
Run these two tests to verify your memory and find which driver is causing the problem.

*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.
RAM - Test with Memtest86+

2-Driver verifier
I'd suggest that you first backup your data 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/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.
Driver Verifier - Enable and Disable

3. Also of note is your Avast which is a contributing cause of BSOD'S.
Please remove and replace your Avast with Microsoft Security Essentials.

Microsoft Security Essentials - Free Antivirus for Windows
My System SpecsSystem Spec
28 Nov 2011   #3

Windows 7 Home Premium x64

Well after a week of adventure, here's what I got.

After 12 hours of no responses, I tried reinstalling windows from an .iso. System crashed halfway through so both OS went to BSOD with the unbootable OS. Managed to reformat my hard drive after 3 days of fun and had to install windows a couple of times before it worked correctly. System ran fine for a couple of days, with extreme system delay at times.

Did the memory tests and those passed fine. Ran the general dell diagnostics and it came back with a hard drive error. Had another BSOD. Afterwards, I ran the verifier and restarted laptop. As soon as the computer booted and started loading windows, I recieved a BSOD and could not get into safe mode.

Currently at system restore.
My System SpecsSystem Spec

28 Nov 2011   #4

Win 7 Ultimate 64-bit. SP1.

Good luck!
My System SpecsSystem Spec
28 Nov 2011   #5

Windows 7 Home Premium x64

Alright system restore didn't work so I went ahead and reinstalled windows Should I post the files from that BSOD?
My System SpecsSystem Spec
28 Nov 2011   #6

Win 7 Ultimate 64-bit. SP1.

Well done too.
You did what so many avoid like the plague.
{The old files are now past History.}
My System SpecsSystem Spec
29 Nov 2011   #7

Windows 7 Home Premium x64

I don't mind reinstalling windows, I have an external HD the same size as my Internal HD so that's not a problem transferring files. However, I still have the same lag and general slow reaction from the computer as I did moments before the initial bsod.

By the way, what do the files in the zip contain that let's you know what the problem is?
My System SpecsSystem Spec
29 Nov 2011   #8

Win 7 Ultimate 64-bit. SP1.

The DMP files are analyzed by WinDbg.
Your crashes pointed to Memory Corruption.
Avast is also often implicated in crashes.

WinDbg - Wikipedia, the free encyclopedia

Download and Install Debugging Tools for Windows

My System SpecsSystem Spec

 BSOD after "Remote procedure call failed and did not execute"

Thread Tools

Similar help and support threads
Thread Forum
The remote procedure call failed [Images]
Hello, I've recently encountered a problem with the service, RPC. Everytime I try opening a picture it gave me an error saying: "The remote procedure call failed "C:\user....." This only apply to images. And as well, it's started to affect windows explorer. I've tried a sfc scan,...
Music, Pictures & Video
AuditMode: explorer.exe remote procedure call failed & did not execute
I've been customising the default user profile in Audit Mode ready to sysprep a clean install of Win7 Pro x64 on a 250GB SSD (C: ) and a 1TB HDD (D: ) using Kari's guide. However, I've run into some apparently unrelated problems. 1. First of all, Macrium was hanging during installation. It did...
Installation & Setup
Windows failed the logon. the remote procedure call failed and did not
I have three users on a Windows 7 computer. none will log on, they all give "Windows failed the logon. the remote procedure call failed and did not execute" it doesn't matter how many time i reboot the computer, all three accounts same error. Googling the problem produces spammy results. exact...
General Discussion
Error : The Remote Procedure Call Failed and did not execute
Hello, I keep getting the The Remote Procedure Call Failed and did not execute error when opening my control panel or windows explorer on Windows 7. I've made sure the RPC is on and that the second service is on manual so that isn't the problem. Any ideas? Thanks in advance.
BSOD Help and Support
1st low disk space rmvd files then error remote procedure call failed
I started getting messages that disk space was low and so i went through with revo uninstaller and rmvd a bunch of programs and apps i really was not using but all the while my disk space was not really improving still kept getting the pop up messages that it was low. I did the disk cleanup...
Performance & Maintenance

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 21:13.
Twitter Facebook