BSOD; STOP: 0x0000007F -- HELP??

Page 1 of 2 12 LastLast

  1. Posts : 13
    Windows 7 Home Premium 64bit
       #1

    BSOD; STOP: 0x0000007F -- HELP??


    I'm lost....And I feel like the largest fool to be honest. I'm not one to tamper with registry files, but I've been having networking/ping complications in an online multiplayer game and I feel victim to something that I shouldn't have done. I'm going to do my ABSOLUTE BEST to highlight all the important parts to best have my issue assessed.

    I attempted to use this link;
    Windows 7 Ping Spikes [FIX] - Steam Users' Forums. More importantly this;
    * Open regedit
    * Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile
    * There will be an entry for network performance throttling, default value is 10; set it to FFFFFFFF hex (willl look like 0xFFFFFFFF to the right of the entry)
    * Reboot
    What I did was followed that very route right-clicked NetworkThrottlingIndex > Modify and put the FFFFFFFF in the Value Data field, where 'a' is. Pressed Ok (received a message, but forgot what it said...something about confirming I believe. Like a stooge, I didn't backup my registry before altering anything, restart and I receive a BSOD. I have a full boot, no issues that I can see and I've been running non stop the past few days since trying the initial process. I have since changed the Value Data back to a and I receive the BSOD every restart. Below is the error code I receive, and nothing more. Doesn't give me any files, or any other codes.


    STOP: 0x0000007f (0x000000000000008, 0x0000000080050031, 0x00000000000006f8, 0xfffff80002cc55a4)


    I'm hoping SOMEONE will be my saving grace. I view multimedia and think graphics driver. I've not gone and reinstalled it because I'm a bit hesitant because I'm not really having any graphics card issues (that I know of). I'm not too advanced, but I'm no dummy. I'm open to ANY help and/or assistance. I truly hope there's a fix out there. I've googled the error...and nothing out there. -Thank You

      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2
      My Computer


  3. Posts : 13
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    My apologies for improperly posting a thread, below is the information needed. i THANK YOU GREATLY!

    BSOD_info_n_health_report.zip

    C: Properties says 64-bit, but my program files is x86
    Original OS. I've only had the CPU one year. OS is as was purchased from Best Buy.
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    BSODs caused by MAudioMobilePre.sys, a driver from Avid Technology, Inc.
    Update the software using it Avid | Avid Support & Services

    Code:
    BugCheck 7F, {8, 80050031, 6f8, fffff80002cd5284}
    
    Unable to load image \SystemRoot\system32\DRIVERS\MAudioMobilePre.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for MAudioMobilePre.sys
    *** ERROR: Module load completed but symbols could not be loaded for MAudioMobilePre.sys
    Probably caused by : MAudioMobilePre.sys ( MAudioMobilePre+14515 )
      My Computer


  5. Posts : 13
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    yowanvista said:
    BSODs caused by MAudioMobilePre.sys, a driver from Avid Technology, Inc.
    Update the software using it Avid | Avid Support & Services

    Code:
    BugCheck 7F, {8, 80050031, 6f8, fffff80002cd5284}
    
    Unable to load image \SystemRoot\system32\DRIVERS\MAudioMobilePre.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for MAudioMobilePre.sys
    *** ERROR: Module load completed but symbols could not be loaded for MAudioMobilePre.sys
    Probably caused by : MAudioMobilePre.sys ( MAudioMobilePre+14515 )
    Reinstalled and the issue still stands. I received the BSOD IMMEDIATELY following the process I explained in my original post.
      My Computer


  6. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #6

    iamblackk said:
    yowanvista said:
    BSODs caused by MAudioMobilePre.sys, a driver from Avid Technology, Inc.
    Update the software using it Avid | Avid Support & Services

    Code:
    BugCheck 7F, {8, 80050031, 6f8, fffff80002cd5284}
    
    Unable to load image \SystemRoot\system32\DRIVERS\MAudioMobilePre.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for MAudioMobilePre.sys
    *** ERROR: Module load completed but symbols could not be loaded for MAudioMobilePre.sys
    Probably caused by : MAudioMobilePre.sys ( MAudioMobilePre+14515 )
    Reinstalled and the issue still stands. I received the BSOD IMMEDIATELY following the process I explained in my original post.
    Then remove this software completely
      My Computer


  7. Posts : 13
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    yowanvista said:
    Then remove this software completely
    Removed, restarted, still receive the BSOD. My audio interface [M-Audio] has been installed and used since I purchased the CPU. I didn't start receiving the BSOD until I tampered with the reg key.
      My Computer


  8. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #8

    iamblackk said:
    yowanvista said:
    Then remove this software completely
    Removed, restarted, still receive the BSOD. My audio interface [M-Audio] has been installed and used since I purchased the CPU. I didn't start receiving the BSOD until I tampered with the reg key.
    Upload the most recent dump files located in C:\Windows\Minidump
      My Computer


  9. Posts : 13
    Windows 7 Home Premium 64bit
    Thread Starter
       #9
      My Computer


  10. Posts : 13
    Windows 7 Home Premium 64bit
    Thread Starter
       #10

    Bumping disallowed?
      My Computer


 
Page 1 of 2 12 LastLast

  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 09:07.
Find Us