BSOD/BCCode: a when playing any games

Page 1 of 3 123 LastLast

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

    BSOD/BCCode: a when playing any games


    Hi guys

    I installed a new CPU about 3 days ago and was getting the BSOD for the first day or so of installing it. So, I asked a friend about it and he said I had to update my BIOS drivers and reset the BIOS to default settings when I was done. I did all that and the issue went away for the last 2 days so I thought I'd fixed it, but I've just gotten the same error twice in the last 45 minutes or so. I'm fairly certain this is hardware related though as I never had this issue prior to installing my new CPU. Could someone here help me figure this out?
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Welcome aboard. :)

    XBox USB wireless controller, BSOD issues in Win7 with 2009 driver. I known issue, very common.
    Code:
     lmvm xusb21
    start             end                 module name
    fffff880`0bde0000 fffff880`0bdf0d80   xusb21     (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\xusb21.sys
        Image name: xusb21.sys
        Timestamp:        Wed Apr 08 19:58:44 2009 (49DCB49C)
        CheckSum:         000135AC
        ImageSize:        00010D80
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Update it from Software Downloads | Microsoft Hardware.

    Also, there is some USBPORT.sys issues.
    Code:
    fffff800`0443e018  fffff880`0440358f usbhub!UsbhFdoUrbPdoFilter+0x107
    
    fffff800`0443e048  fffff880`04433d8f usbhub!UsbhPdoInternalDeviceControl+0x373
    
    fffff800`0443e080  fffff880`05f1d110 USBSTOR!WPP_GLOBAL_Control
    It may be caused by the previously stated issue, or may be independent. Dont take a risk, do some maintenance. For the port, first, uninstall and reinstall the USB ports drivers.

    1. Right click on Computer icon > manage. It will open the computer management window.
    2. Click on "Device Manager" in the left pane, it will list all installed devices up.
    3. Expand "USB Serial Bus Controllers" by clicking on the triangle in front of it.
    4. Click on one item to select, then right click and uninstall.
    5. Do the same for all.
    6. Restart the computer.
    7. At restart, windows will auto configure the appropriate drivers.

    And, Disable USB Selective Suspense too.
    USB Selective Suspend - Turn On or Off

    For the devices, first, detach all the USB devices other than the keyboard and mouse.
    Then, Update the drivers for them all, including the keyboard and mouse, if any third party drivers are installed for them.

    You are using a beta of the display driver.
    Code:
    lmvm nvlddmkm
    start             end                 module name
    fffff880`048b1000 fffff880`053d2000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Dec 01 08:54:02 2012 (50B97852)
        CheckSum:         00B0A675
        ImageSize:        00B21000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Apply the latest version of nVidia display driver.
    You may download it directly, from our forum link Latest NVIDIA ForceWare Video Drivers Windows 7; or you may opt for the Option 2 of Drivers- Download NVIDIA Drivers for “Automatically find drivers for my NVIDIA products” (it requires java installed).



    Symantec Heuristics Driver
    Code:
    fffff880`09cc83e0  fffff880`04566050Unable to load image BHDrvx64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for BHDrvx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
     BHDrvx64+0x44050
    Description here: Driver Reference Table - BHDrvx64.sys

    Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

    Download and install those, and then run full system scans with both of them, one by one.

    Let us know the results.
      My Computer


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

    Hey Arc, thanks for the help. I got new drivers for the 360 controller, uninstalled all of the USB drivers, turned off USB selective suspend, got the correct NVidia drivers and removed everything related to symantec from my PC. While MSE was scanning my system I got the BSOD again, this time BCCode: 1e instead of the "a" I have been getting. Gonna try running MSE and MBAM again.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Upload the latest dump here :)
      My Computer


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

    Here you go, thanks again.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    The latest crash dump is not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


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

    Ok, I've been running DV for awhile now with no crashes, but I'm posting because i was looking around online for people with the same issues and on another forum someone recommended "who crashed 4.01". I downloaded it and i've got 10 crashes in the past week and about 8 are from ntoskernel.exe, 1 from amdppm.sys and 1 from nvlddmkm.sys (which is the nvidia drivers we fixed already). I haven't stopped DV or anything, I'm sorta just hoping this information helps or narrows the search.
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    Sorry I did not get you?

    You cannot trust on whocrashed, coz ntoskrnl.exe is not any cause of a crash, but the kernel on which it crashed. As the crash is driver related, (driver IRQL less or not equal) I suggested you Driver verifier.

    But, if you continue taking multiple suggestion, there is a good chance of conflict of opinion, and the situation will become worse.

    Decide, let us know. Depending on your decision, next steps will be taken or not.
      My Computer


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

    Alright, I was just trying to help. From now on I'll leave it to you guys. :)

    DV is still running.
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    With DV enabled, do the most crash prone actions ... those crashed your computer mostly ... gaming, surfing net ... whatever. Try to replicate the crashes.

    Are you feeling it a bit slow and laggy?
      My Computer


 
Page 1 of 3 123 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 06:07.
Find Us