1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

BSOD when trying to install program

Discussion in 'Windows 7' started by Bear, 2014/04/12.

  1. 2014/04/12
    Bear

    Bear Well-Known Member Thread Starter

    Joined:
    2003/07/05
    Messages:
    36
    Likes Received:
    0
    I am running Win7 Pro 64bits.
    Yesterday I bought a program (PathWiz v9) that will locate missing photo exhibits in my genealogy program, The Master Genealogist (TMG).
    The first time I started installation I got a BSOD with the following Technical Information:>***Stop: 0x0000007F
    (0x0000000000000008,0x0000000080050031,0x00000000000426F8,
    CxFFFFF80002EFD836).
    Trying with a new download of the program, I did not get a BSOD but the computer restarted immediately. I have tried to run the installation as Admin but no change :confused:.

    Coincidentally, I had a similar experience when working in TMG and tried to preview a report on screen. The same Technical Information message came up once but with EEA instead of EFD in the last sequence. TMG runs flawlessly otherwise. Saving the same report in MSWord worked fine.

    What could be the problem? I don't know where to start so any suggestions are welcome. What other information do you need to pinpoint the problem?
     
    Bear,
    #1
  2. 2014/04/13
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,285
    Likes Received:
    249
    Steve R Jones,
    #2


  3. to hide this advert.

  4. 2014/04/13
    Bear

    Bear Well-Known Member Thread Starter

    Joined:
    2003/07/05
    Messages:
    36
    Likes Received:
    0
    This link is to Windows XP and "This article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. ":(
     
    Bear,
    #3
  5. 2014/04/13
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    7,158
    Likes Received:
    503
    Try this link Bear. It's a Wiki explanation of the 0x0000007F error. Scroll down to Ways to Repair 0x0000007F error. Then click on the highlighted link and Download the repair. Neil.

    How to fix the "0x0000007f" error
     
    retiredlearner,
    #4
  6. 2014/04/14
    Bear

    Bear Well-Known Member Thread Starter

    Joined:
    2003/07/05
    Messages:
    36
    Likes Received:
    0
    Thanks, Neil.
    I tried to download the file but my virus program stopped me. It is infected (hkP1mWMK.exe), it seems.
    Any other link or suggestion?
     
    Bear,
    #5
  7. 2014/04/14
    James Martin

    James Martin Geek Member

    Joined:
    2003/05/15
    Messages:
    2,655
    Likes Received:
    79
    James Martin,
    #6
  8. 2014/04/14
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,680
    Likes Received:
    104
    PC Speedup.exe is just Snake Oil!!!

    Don't use it!
     
    Admin.,
    #7
  9. 2014/04/14
    James Martin

    James Martin Geek Member

    Joined:
    2003/05/15
    Messages:
    2,655
    Likes Received:
    79

    I figured as much, but I didn't say anything.
     
    James Martin,
    #8
  10. 2014/04/14
    Bear

    Bear Well-Known Member Thread Starter

    Joined:
    2003/07/05
    Messages:
    36
    Likes Received:
    0
    Thank you, Admin.
    Just for your information, the link in wikifix.com points to:
    http://www.tweakbit.com/external/wikifixes/pc-speed-up/?variant=b
    When I clicked on the wikifix link, Avast quarantined this: hkP1mWMK.exe.part

    This still leaves me with the problem. Any other suggestions?
     
    Bear,
    #9
  11. 2014/04/14
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    7,158
    Likes Received:
    503
    Strange - when I click on the wiki "click here to download the error repair application" the download opens to SAVE 'rcpsetup.31378.exe'

    I have downloaded to my comp without any problems. You may need to adjust your security level in Avast or make it an exception. Neil.
     
    retiredlearner,
    #10
  12. 2014/04/14
    James Martin

    James Martin Geek Member

    Joined:
    2003/05/15
    Messages:
    2,655
    Likes Received:
    79
    Avast is now blocking it here as well. I would assume this is a false positive, but the software in question looks like the paid version of a registry cleaner.

    According to a Google search, RegClean Pro (rcpsetup.exe) can be difficult to remove once you install it...


    I would avoid it like Arie mentioned.

    EDIT: Found this online...

    RegClean Pro it’s technically not a virus, but it does exhibit plenty of malicious traits, such as rootkit capabilities to hook deep into the operating system, browser hijacking, and in general just interfering with the user experience. The industry generally refers to it as a "PUP," or potentially unwanted program.​
     
    James Martin,
    #11
  13. 2014/04/14
    Bear

    Bear Well-Known Member Thread Starter

    Joined:
    2003/07/05
    Messages:
    36
    Likes Received:
    0
    Thanks, James!!:)
    I don't need more problems! Just need a fix for the 0x0000007F error!
     
    Bear,
    #12
  14. 2014/04/14
    James Martin

    James Martin Geek Member

    Joined:
    2003/05/15
    Messages:
    2,655
    Likes Received:
    79
    James Martin,
    #13
  15. 2014/04/15
    Bear

    Bear Well-Known Member Thread Starter

    Joined:
    2003/07/05
    Messages:
    36
    Likes Received:
    0
    I don't see anything in there that would apply to my case.

    I installed Debugging Tools for Windows and ran the debugwiz.exe on the minidump, BUT no debuglog.txt is saved (it says the analysis should be saved in c:\debuglog.txt). Why?
     
    Bear,
    #14
  16. 2014/04/16
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,890
    Likes Received:
    387
    As I recall there is an error in the command string .....

    C:debuglog.txt has the wrong syntax - should be C:\debuglog.txt

    Check the Advanced box and add the backslash and you should be good to go.
     

    Attached Files:

    PeteC,
    #15
  17. 2014/04/16
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,285
    Likes Received:
    249
    The link that James posted for WIn 7 is the same I posted for WIn XP... They both say:

    So running a testing app like MemTest86 would be a good thing to do.
     
    Steve R Jones,
    #16
  18. 2014/04/16
    Bear

    Bear Well-Known Member Thread Starter

    Joined:
    2003/07/05
    Messages:
    36
    Likes Received:
    0
    Thanks, Pete.
    I changed the syntax but there is still no debuglog.txt generated -anywhere:(
     
    Bear,
    #17
  19. 2014/04/16
    Bear

    Bear Well-Known Member Thread Starter

    Joined:
    2003/07/05
    Messages:
    36
    Likes Received:
    0
    Thanks, Steve.
    I have run the memorytest utility on the computer and the extended version directly off the OM disk, and both times it was indicated a result would be shown after the reboot. Not so. I don't know if that indicates that there were no problems or if it is the same problem as not getting a debuglog.txt generated....
    However, I will now start the MemTest86 and hope something will show...
     
    Bear,
    #18
  20. 2014/04/16
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,890
    Likes Received:
    387
    I seem to have an issue with my Windows SDK and cannot complete a dump debug -and no time at present to seek out a fix.

    However try running the dump file through Blue Screen View - it may give you a pointer.
     
    PeteC,
    #19
  21. 2014/04/16
    Bear

    Bear Well-Known Member Thread Starter

    Joined:
    2003/07/05
    Messages:
    36
    Likes Received:
    0
    Just to continue on Steve's suggestion of MemTest86 - I ran 3 full passes without any errors.

    I have looked at the BlueScreenView of the minidump, and it shows ntoskrnl.exe with address in the stack ntoskrnl.exe+a0836 and caused by address ntoskrnl.exe+75bc0.

    I don't know what this means, so, now what do I do, if memory is OK?
     
    Bear,
    #20

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...