BSOD at least once at the start of the day

Page 1 of 2 12 LastLast

  1. Posts : 12
    Windows 10 Home x64
       #1

    BSOD at least once at the start of the day


    Hi there,

    For last few months, I have been having very frequent BSOD crashes on my desktop. I have attached a zip file with 2 recent dmp files of these crashes. I have looked at a lot of threads about these similar crashes, and performed a few tests. I have tested my hard disk via Chkdsk utility and memory via Memtestx86- both of which showed no error. I also completely removed my nVidia drivers and reinstalled (since mostly the crash happens when I run media- online video or video games). This might just be a coincidence though since those are the two things I do the most on my desktop.

    I have done a lot of cleaning/malware removal with Advanced System Care (Iobit- not currently installed), CCleaner, Disk Cleanup, Malwarebytes, AVG Internet Security, etc. Usually the crashes seize for a couple of days after all this cleaning but start again.

    I know my computer is pretty old so chances are there might be something wrong on the hardware side, but so far I have not been able to figure out what that might be. Any help is appreciated.
      My Computer


  2. Posts : 2,781
    Windows 10 Pro x64
       #2

    Hiya and welcome to SevenForums!
    Code:
    BugCheck 1E, {ffffffffc000001d, fffff960001cc30c, 0, fffff80003661000}
    
    Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : win32k.sys ( win32k+fc30c )
    Code:
    BugCheck 1D0CA30, {fffffffffffff910, 0, 0, 388fc28}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    Run sfc /scannow and chkdsk /r.
    Install the latest updates from Windows Update.

    Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

    SFC /SCANNOW Command - System File Checker
      My Computer


  3. Posts : 12
    Windows 10 Home x64
    Thread Starter
       #3

    Hi there,

    Thanks for the reply.

    I have run chkdsk countless times and it hasn't shown any error. I ran sfc /scannow on your advice, and it didn't show any error either. (Windows Resource Protection did not find any integrity violations).

    Also, I recently updated to Windows 10. The computer was Ok for 2 days but it crashed again today. The crash wasn't a bluescreen, just a restart on its own.
      My Computer


  4. Posts : 2,781
    Windows 10 Pro x64
       #4

    Can you please post the latest dumps?
      My Computer


  5. Posts : 12
    Windows 10 Home x64
    Thread Starter
       #5

    Here is today's crash dump file.
    Last edited by amandeep; 08 Aug 2015 at 15:52.
      My Computer


  6. Posts : 2,781
    Windows 10 Pro x64
       #6

    Hmm,
    Code:
    BugCheck 9F, {3, ffffe001ded2a060, fffff803fe9b9a90, ffffe001ea173010}
    
    Probably caused by : pci.sys
    What do you have in your PCI/PCI-E slots? Only your GPU?
    Also run Driver Verifier for 24 hours. Driver Verifier - Enable and Disable
      My Computer


  7. Posts : 12
    Windows 10 Home x64
    Thread Starter
       #7

    Hey,

    I tried running Driver Verifier twice today, and the computer didn't boot either time (had to Restore both times).

    A dump file was created after first time, and the same file was updated the second time (so I only have the latest dump).

    BlueScreenView of both dump files had ntoskrnl.exe, and the first one also pointed towards Dtsoftbus01.sys (the latest one points to volmgr.sys).

    ntoskrnl.exe has probably been highlighted by BlueScreenView in 98-100% of dmp files created over last few months.

    Edit: Yes, I only have my GPU in PCI-E slot (rest are empty).
      My Computer


  8. Posts : 2,781
    Windows 10 Pro x64
       #8

    Code:
    BugCheck C9, {23e, fffff80172b91324, ffffe0012d97d9d0, 0}
    
    Unable to load image \SystemRoot\System32\drivers\dtsoftbus01.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dtsoftbus01.sys
    *** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
    Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )
    This is the Daemon Tools SPTD driver. Uninstall Daemon tools for testing purposes.
      My Computer


  9. Posts : 12
    Windows 10 Home x64
    Thread Starter
       #9

    I did Uninstall Daemon Tools and removed all the left overs as well (using Iobit Uninstaller). Would you recommend running Driver Verifier once again or just wait and see if crashes continue to happen?
      My Computer


  10. Posts : 2,781
    Windows 10 Pro x64
       #10

    Run DV once again and don't use IOBit tools, they can be malicious.
      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 09:35.
Find Us