BSOD Playing LoL (Possible Flash/Graphics Error)

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 11
    Microsoft Windows 7 Ultimate 64-bit
    Thread Starter
       #11

    Malwarebyte and MSE both came back with nothing.

    Had a bsod while running MSE though

    On Wed 12/26/2012 8:03:37 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122612-11840-01.dmp
    This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x16E216)
    Bugcheck code: 0xF7 (0xFFFFD000022054C0, 0x2B992DDFA232, 0xFFFFD466D2205DCD, 0x0)
    Error: DRIVER_OVERRAN_STACK_BUFFER
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 310.70
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 310.70
    Bug check description: This indicates that a driver has overrun a stack-based buffer.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 310.70 , NVIDIA Corporation).
    Google query: NVIDIA Corporation DRIVER_OVERRAN_STACK_BUFFER
      My Computer

  2.    #12

    Upload the dump as a attachment :)
      My Computer


  3. Posts : 11
    Microsoft Windows 7 Ultimate 64-bit
    Thread Starter
       #13

    Uploaded, should be the most recent dump
      My Computer

  4.    #14

    Code:
    BugCheck F7, {ffffd000022054c0, 2b992ddfa232, ffffd466d2205dcd, 0}
    
    Probably caused by : nvlddmkm.sys ( nvlddmkm+16e216 )
    Code:
    Usual causes:  Device driver, Malware
    To avoid any possibility of driver corruption or conflict, follow these steps:
    1. Download Driver
    2. Start Type: Device Manager
    3. Expand Display Adapters
    4. Right-Click Driver Name, Uninstall
    5. Reboot
    6. Run Driver Sweeper
    7. Reboot
    8. Install Downloaded Driver

    Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

    Driver Sweeper:

    Scan for any malware or rootkits using:

    If you are running Driver Verifier, then I suggest you disable it for now.
      My Computer


  5. Posts : 11
    Microsoft Windows 7 Ultimate 64-bit
    Thread Starter
       #15

    I started to use my desktop again today. I ran fine for about an hour then I had two bsods within a span of 10 minutes.
      My Computer

  6.    #16

    Code:
    BugCheck FC, {fffff88003d07710, 800000010a0b3963, fffff88003d07440, 0}
    
    *** 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+dfe60 )
    Code:
    Usual causes:  Device driver
    Code:
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`04c29000 fffff880`0574a000   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 03:24:02 2012 (50B97852)
        CheckSum:         00B0A675
        ImageSize:        00B21000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Have you scanned with Windows Defender Offline?

    Memory:

    Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

    Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

    Test each RAM stick and every motherboard DIMM slot available.
      My Computer


  7. Posts : 11
    Microsoft Windows 7 Ultimate 64-bit
    Thread Starter
       #17

    I ran memtest overnight with no errors.

    I am starting to think its my SSD since thats the only thing that has changed. Here are a few more ssds
      My Computer

  8.    #18

    Code:
    BugCheck FC, {fffff88003d07710, 800000010a0b3963, fffff88003d07440, 0}
    
    *** 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+dfe60 )
    Have you tried using an older driver certified with WHQL?
      My Computer


  9. Posts : 11
    Microsoft Windows 7 Ultimate 64-bit
    Thread Starter
       #19

    x BlueRobot said:
    Code:
    BugCheck FC, {fffff88003d07710, 800000010a0b3963, fffff88003d07440, 0}
    
    *** 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+dfe60 )
    Have you tried using an older driver certified with WHQL?
    Yeah I tried an older driver with no luck. I reverted back to a newest one. I also played around with my bios thinking that something in the failsafe bios was causing me to bsod (voltages, etc).

    I am starting to lose hope in my PC. It might just be that my mobo is dying; I bought it back in 2008. When I get some extra time I might set my bios back to IDE and try my old HDD and see if I have any luck with that.

    But for now, I uploaded a few of my recent minidumps, maybe something new popped up.
      My Computer

  10.    #20

    Remove:

    Code:
    Pando Media Booster	c:\program files (x86)\pando networks\media booster\pmb.exe
    You may want to remove PMB due to it's high network ususage, and some of the network problems it seems to cause in this thread:

    Code:
    BugCheck 1E, {ffffffffc0000096, fffff80002c93f56, 0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSpinLock+26 )
    Code:
    Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
    Scan for any missing, modified or corrupted protected Windows files with:

    Scan with SuperAntiSpyware:

    Remember to unselect the trail option of the installation, and make sure you install the free edition.
      My Computer


 
Page 2 of 3 FirstFirst 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 05:50.
Find Us