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


  1. Posts : 4
    Windows 7 Home Premium x64
       #1

    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 Computer


  2. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #2

    CiscoQL,

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

    1-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.
    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.

    http://files.avast.com/files/eng/aswclear5.exe

    Microsoft Security Essentials - Free Antivirus for Windows
      My Computer


  3. Posts : 4
    Windows 7 Home Premium x64
    Thread Starter
       #3

    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 Computer


  4. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #4

    Good luck!
      My Computer


  5. Posts : 4
    Windows 7 Home Premium x64
    Thread Starter
       #5

    Alright system restore didn't work so I went ahead and reinstalled windows Should I post the files from that BSOD?
      My Computer


  6. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #6

    Well done too.
    You did what so many avoid like the plague.
    {The old files are now past History.}
      My Computer


  7. Posts : 4
    Windows 7 Home Premium x64
    Thread Starter
       #7

    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 Computer


  8. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #8

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

    FYI.
    WinDbg - Wikipedia, the free encyclopedia

    Download and Install Debugging Tools for Windows

      My Computer


 

  Related Discussions
Our Sites
Site Links
About 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 19:05.
Find Us