Frequently getting different kinds of BSODs

Page 1 of 2 12 LastLast

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

    Frequently getting different kinds of BSODs


    Hi, I've had this problem a few months ago which was apparently caused by my WLAN driver but that shouldn't be the case now. The BSOD seem to be different this time around, as well.


    Additional Info:







    Probably another useless info but I want to include everything just to be sure:

    ------------------

    Machine name: USER-PC
    Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532)
    BIOS: BIOS Date: 08/24/11 14:48:54 Ver: 04.06.04
    Processor: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8 CPUs), ~3.4GHz
    Memory: 8192MB RAM
    Available OS Memory: 8104MB RAM
    Page File: 5848MB used, 10359MB available
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    Card name: NVIDIA GeForce GTX 570
    Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um




    Thanks in advance.
      My Computer


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

    Additionally, most of the time, ntoskrnl.exe seems to be the cause.
      My Computer


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

    bump

    got a few more Bluescreens in the last few days, had no problems the days before

    for some reason most Bluescreens don't get "saved" (no data saved on bluescreenview), sometimes it just freezes without the blue screen appearing.

    Last BSOD that I actually get infos from displayed "ntoskrnl.exe" and "cfosspeed6.sys" as the causes.
      My Computer


  4. Posts : 1,436
    Windows 8.1 Pro x64
       #4

    I will look at the previous files, in the mean time can you post up the latest files using the tool?
      My Computer


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

    Ok, here it is (last minidump only).
      My Computer


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

    The last BSOD was caused by cFosSpeed for faster Internet connections
    (c:\windows\system32\drivers\cfosspeed6.sys)
    Code:
    BugCheck D1, {fffff880034889b0, 2, 0, fffff880034889b0}
    
    *** WARNING: Unable to verify timestamp for cfosspeed6.sys
    *** ERROR: Module load completed but symbols could not be loaded for cfosspeed6.sys
    Probably caused by : cfosspeed6.sys ( cfosspeed6+30e09 )
    
    Followup: MachineOwner
    ---------
    I would suggest you to uninstall it, as it is a problem wherever it is installed.

    Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

    • Double click to open it.
    • Click this button only:
    • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

    Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept then restart.

    Let us know the results.
      My Computer


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

    Thanks, I've done all of that now. I'll report back if there's another BSOD (or if the problem is solved).
      My Computer


  8. Posts : 25
    Windows 7 Home Premium 64-bit
    Thread Starter
       #8

    Bump

    Got another one just minutes ago.
      My Computer


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

    Code:
    BugCheck 7F, {8, 80050031, 406f8, fffff8000327ff3a}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    Hi. It indicates a double fault. It may be caused either by a kernel stack overflow or by a hardware issue.

    The first step to troubleshoot this issue would be to perform a clean install using a genuine media, and activating that installation by a legit key. The key that is in use is not legit for a retail ASRock motherboard, but for a Packard OEM.
    _______________________
    Code:
    BaseBoardManufacturer = ASRock
    BaseBoardProduct = Z68 Pro3 Gen3
    Code:
    *****-OEM-8992687-00006
      My Computer


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

    Thanks a ton. I haven't understood much of it, though (since I'm not knowledgable in this field). Especially the info you provided that is in quotes.

    What am I supposed to install? What is a "genuine media"? Where to get a "legit key"?

    I assume the key that I currently use is not the correct one?

    Thanks in advance again.
      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 17:58.
Find Us