New
#11
ProzacR, please run the DM Log Collector tool again and upload the new zip file.
I am currently going through the dump files and there are more drivers that have caused problems.
ProzacR, please run the DM Log Collector tool again and upload the new zip file.
I am currently going through the dump files and there are more drivers that have caused problems.
I went to device manager->USB controllers and clicked on everything and "update..." Windows said it was up to date already.
Also I uploaded new pack of dump files again yesterday and nobody checked it. You still want yet another one?
The latest dump is from 4 days ago, but according to the event logs a crash occured 2 days ago.
Please check {windows partition}\windows\minidump and check if there are recent dump files saved.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 7 tutorial
My windows/Minidump contains 9 files I can upload them for you if you want?
Also I went to SystemPropertiesAdvanced.exe and canged fromKernel memory dump to Small memory dump.
I think I have to wait from new BSOD before uploading that zip file again right?
I will upload it after i got one.
All those few days I was without BSODs. Thought it is fixed somehow.
Well at least really declined in numbers.
Just today I had win update and another one. Looks quite different.
Adding new info file.
I can't open the dump without errors.
This has some causes,
- symbol problems, usually solved by loading the dump a few times (open, wait until it is loaded, close, open, wait til it is loaded etc.)
- hardware problem,
- counterfeit installation,
- malware
- Microsoft server down for downloading the symbols, rare but happens
- other un-explained behavior.
My thoughts are hardware problem and other un-explained behavior where I think the system files are involved.
Diagnostics Test
System File Check
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 does NOT say "Windows Resource Protection did not find any integrity violation", 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.