New
#11
Actually the driver is outdated, not a cause.
However my experience is that if outdated drivers are not taken care of that they'll cause stability problems in matter of time.
Actually the driver is outdated, not a cause.
However my experience is that if outdated drivers are not taken care of that they'll cause stability problems in matter of time.
i did first click the button download, but now i see a button for more and it says 32 or 64bit so i install now the 64bit version
okeu i did that....
i got a new bluescreen:)
file:///C:/Program%20Files%20(x86)/bluescreenview-x64/report.html
and now ?...
file:///C:/Program%20Files%20(x86)/bluescreenview-x64/report.html Again... >.<
C:\WINDOWS\system32>sfc/scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
Please explain to me why you add the text
Please run the DM Log Collector, the tool from the BSOD Posting Instructions, again and upload a new zip.file:///C:/Program%20Files%20(x86)/bluescreenview-x64/report.html
Please follow below instructions for sfc.
Please try following:
- Open an admin command prompt
- Copy/paste "sfc/scannow" (without quotes) and press enter
- When it finished reboot your system
- Open again an admin command prompt
- Enter sfc/scannow again
If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.