BSOD possibly related to drivers

Page 1 of 2 12 LastLast

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

    BSOD possibly related to drivers


    I had a couple virus and BSODs and googling directed me to driver issues. I decided to do a factory reset. I'm still expriencing a BSOD. The last one occured when I tried using a Java applet. Please help.
      My Computer


  2. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #2

    TDSSKILLER

    download link TDSSKILLER

    Save to the Desktop

    Right-click the program and select


    When the TDSSKiller console opens, click on: Change Parameters
    Under Additional Options, place a check in the box next to: Detect TDLFS File System

    Click: OK


    Press: Start Scan


    If a suspicious object is detected, the default action is Skip, leave it as is, and click on: Continue
    If malicious objects are found, they show in the Scan results.
    Ensure Cure (the default) is selected, then click: Continue > Reboot now, to finish the cleaning process.
    (Note: If Cure is not available, select Skip, >>Do not select: Delete<<)


    When done, the tool outputs its log to the disk with the Windows Operating System, normally C:\


    Logs have a name like:
    C:\TDSSKiller.X.X.X_12.04.2013_15.31.43_log.txt


    Please post the TDSSKiller log in your reply.
      My Computer


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

    Here you go
      My Computer


  4. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #4

    No rootkit .
      My Computer


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

    Yea I did a factory reset so I didn't think it was a virus. I thought the KMODE_Exception BSOD was related to drivers. Blue Screen View pointed out cpudrv64.sys and ntoskrnl.exe. Any clue what the problem is?
      My Computer


  6. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #6

    Looking at the dmp file . Looks like it was caused by this driver

    lmvm cpudrv64
    start end module name
    fffff880`05ddb000 fffff880`05de3000 cpudrv64 T (no symbols)
    Loaded symbol image file: cpudrv64.sys
    Image path: cpudrv64.sys
    Image name: cpudrv64.sys
    Timestamp: Tue Aug 11 09:39:13 2009 (4A819EB1)
    CheckSum: 0000D622
    ImageSize: 00008000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
    cpudrv64.sys - System Requirements Lab

    If you don't need that piece of software Uninstall it.
      My Computer


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

    done. So I should be safe from bsods for now?
      My Computer


  8. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #8

    Now its a waiting game . Use the PC like you normally would if you get another BSOD upload the dmp file .
      My Computer


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

    Just got this one. Different driver.
      My Computer


  10. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #10

    Its still the same driver as before. Did you remove the program ?
      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 10:15.
Find Us