BSOD during gaming or when left overnight (0x0000007f)


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

    BSOD during gaming or when left overnight (0x0000007f)


    Hi everyone, when I first built this computer about a year ago I was getting BSODs. I tracked the problem to a bad stick of RAM, replaced it and for a while everything was fine. Then whenever I would get on my computer after it had been on occasionally overnight I would be greeted by a "Windows has recovered from an unexpected shutdown" message. Shortly after I started getting BSODs when playing games but only ones that were really pushing my graphics card.

    I did a quick once over of everything inside the case, reseated the RAM and graphics card, then started it back up. It hasn't yet given me a BSOD during gaming, but I still return to the message that one happened when I left it overnight.

    I ran Driver Verifier Manager and left the computer on. I came home from work today to see it had a BSOD at some point within the last twelve hours (after Verifier had been running between 36 and 48 hours). The result showed ntoskrnl.ex+b03dd UNEXPECTED_KERNEL_MODE_TRAP for whatever that's worth (although I'm sure it's in the files attached as well.)

    I have also run memtest which detected no errors. I can't remember a specific driver update shortly prior to starting to get these BSODs, so I can't help with any information there.

    I have attached the files as per the instructions on posting here. I also filled out my system specs when registering.

    Thanks for looking. If anyone could provide me with any help I would be eternally grateful.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to the forum.

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

    MBfilt64.sys Fri Jul 31 09:40:32 2009 (4A7267B0)
    Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver) - Was found in the latest Win8 version available from Realtek on 07Sep2013
    Driver Reference Table - MBfilt64.sys

    xusb21.sys Fri Aug 14 04:10:17 2009 (4A848F49)
    XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
    Driver Reference Table - xusb21.sys

    LGBusEnum.sys Tue Nov 24 07:36:48 2009 (4B0B38B0)
    Logitech Keyboard
    Driver Reference Table - LGBusEnum.sys

    LGVirHid.sys Tue Nov 24 07:36:48 2009 (4B0B38B0)
    Logitech Gamepanel Virtual HID Device Driver
    Driver Reference Table - LGVirHid.sys

    NTIOLib_X64.sys Wed Oct 20 12:45:49 2010 (4CBE901D)
    MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5
    Driver Reference Table - NTIOLib_X64.sys

    rtl8192Ce.sys Tue Jul 12 10:09:44 2011 (4E1BC908)
    Realtek RTL8192CE Wireless LAN PCI-E NIC[br]Realtek RTL8188CE 802.11b/g/n WiFi Adapter[br]Other Realtek wifi adapters use this same driver[br]
    Driver Reference Table - rtl8192Ce.sys

    Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

    And you can follow the steps mentioned here:

    Based on the bugchecks, I would recommend you follow and complete the steps given below:
    1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

    2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

    3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

    4. Run SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

    5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

    6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

    7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

    8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

    9. Test and Diagnose RAM issues with RAM - Test with Memtest86+. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

    10. Monitor hardware temperature for overheating issues with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:

    BSOD DUMP OUTPUT:
    Code:
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Tue Mar 11 12:21:59.030 2014 (UTC + 6:00)
    System Uptime: 1 days 2:57:11.967
    BugCheck 7F, {8, 80050033, 406f8, fffff80002ebb3dd}
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME:  dwm.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Sun Mar  9 21:02:02.559 2014 (UTC + 6:00)
    System Uptime: 0 days 7:01:40.360
    BugCheck 1000007E, {ffffffffc0000096, fffff80002e8de47, fffff8800319a668, fffff88003199ec0}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXSave+a7 )
    BUGCHECK_STR:  0x7E
    PROCESS_NAME: NOT FOUND
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Sun Mar  9 13:59:09.554 2014 (UTC + 6:00)
    System Uptime: 0 days 10:03:04.475
    BugCheck 50, {fffff88003d4c760, 1, fffff88003ea7332, 0}
    Probably caused by : afd.sys ( afd+2c332 )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  uTorrent.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Sun Mar  9 03:55:15.351 2014 (UTC + 6:00)
    System Uptime: 1 days 21:36:47.272
    BugCheck 3B, {c0000005, fffff80002e3df6c, fffff88006554f80, 0}
    Probably caused by : ntkrnlmp.exe ( nt!ExfUnblockPushLock+30 )
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  svchost.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Fri Mar  7 05:52:14.042 2014 (UTC + 6:00)
    System Uptime: 0 days 1:08:55.963
    BugCheck 4E, {99, 73ca2, 3, 1e74a1}
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    BUGCHECK_STR:  0x4E_99
    PROCESS_NAME:  firefox.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Thu Mar  6 02:47:34.105 2014 (UTC + 6:00)
    System Uptime: 1 days 3:49:22.026
    BugCheck D1, {178, 9, 1, fffff8800f1155e3}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+c75e3 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Tue Mar  4 22:57:16.412 2014 (UTC + 6:00)
    System Uptime: 0 days 10:53:07.723
    BugCheck 3B, {c0000005, fffff80002e67e63, fffff880095e25b0, 0}
    Probably caused by : ntkrnlmp.exe ( nt!RtlSidHashInitialize+67 )
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  nvstreamsvc.ex
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Sun Mar  2 17:24:35.342 2014 (UTC + 6:00)
    System Uptime: 0 days 7:43:07.080
    BugCheck 1E, {ffffffffc0000005, fffff8800f2091f5, 1, 482275c0}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : hardware ( nvlddmkm+1f31f5 )
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Sun Mar  2 09:40:20.752 2014 (UTC + 6:00)
    System Uptime: 1 days 5:28:37.063
    BugCheck D1, {28, 2, 0, fffff88004ea5628}
    *** WARNING: Unable to verify timestamp for rtl8192Ce.sys
    *** ERROR: Module load completed but symbols could not be loaded for rtl8192Ce.sys
    Probably caused by : nwifi.sys ( nwifi!MP6ReturnNBL+30 )
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
      My Computer


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

    Thank you very much for the response. I am currently in the process of doing as you recommended. I will respond with an update, hopefully stating the problem has resolved. Thanks again.
      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 12:39.
Find Us