1) done.
2) link file with Everything: Dropbox - NDIS-20181001-2257.rar
3) DriverBooster Uninstall, done.
4) and how do I know what they are?
5) during the full exam with hdtune I went to the blue screen, here is the beta file:
Attachment 207125
afterwards I launched the scan again and I still went in blue screen .. that is a problem of the ssd?
It is the same storage driver from day one. As I reported other Dell users were having issues. Rolloback youor storage driver using device manager and block driver updates.
sorry I did not answer, I did not do what you said.
I uninstalled the software and driver and re-installed version 15.7.5.1025.
There was no need to block updates as I noticed that I do not detect updates for the driver.
I probably updated it with the software that automatically downloads the drivers.
I launched HD Tune again and the error scan did not give me any problems. it was completed without errors. No blue screen has happened.
What is really solved? let's see if blue screen happens again, otherwise I'll go back to writing.
Meanwhile, thank you very much for your help.
1) For all steps/tests please post images into the thread.
2) When available please post the HD Tune and memtest86+ version 5.01 test result images into the thread.
3) When available please post chkdsk notepad report into the thread.
4) For software that install drivers they can install unknown files.
If the drivers are not identified it can be fixed by a system restore to a date that predates the installation of the software.
Sometimes a clean install is needed.
At this time you can uninstall the iorbit software.
5) Open everything and search for: C:\windows\memory.dmp
zip the file > post a share link into the thread using one drive, drop box or google drive
Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 10/06/2018 13:36:50
Size on disk: 792 MB
6) Open device manager > click view > show hidden devices > manually expand all rows > look for any row displaying a yellow triangle with black exclamation mark or unknown device > post images into the thread
7) Backup all important files to another drive or to the cloud
8) Make a backup image of the drive using Macrium
Macrium Software | Your Image is Everything
9) Save the backup image to another drive or to the cloud
10) Make a brand new restore point
Last edited by zbook; 06 Oct 2018 at 15:05.
the problem seems solved. You do not need to investigate further since I do not want to go to the blue screen anymore ... do not you think?
Keep that driver handy.
When V1809 installs someday MS will enforce all new drivers on you and it very likely will start to BSOD again. You should just be able to search device and select but if not you want it in your back pocket.
If it BSOD's again you can always add to this thread.
Let's see if zbook needs more info as he is far more skilled in the area of BSOD than I am.
When troubleshooting bsod there may be problems found in the logs that are related or unrelated to the bsod.
The computers are tuned up to fix the findings in the logs.
If the bsod are no longer occurring and there is a stable environment (at least one week of typical computer use with stability) then the bsod no longer need to be troubleshooted.
Preventative maintenance can be performed to check all drivers.
If you post the test results of the steps in the prior posts they can be troubleshooted.
Checking device manager and making a back up image are recommended.
Caldedon Ken helped me with a backup image in a complicated thread.
Macrium is highly recommended in Ten Forums.
Sorry to bump in, but @Max90, I would recommend that you only do this
if you understand what could happen.Preventative maintenance can be performed to check all drivers.
Preventative maintenance to check drivers refers to a tool called driver verifier. Driver verifier checks whether drivers that have been selected to test perform operations properly. There are only certain operations driver verifier checks which are chosen before driver verifier runs. Because driver verifier validates if an operation is handled properly, your system might be slower than usual.
The process where driver verifier validates operations with driver verifier is called stress testing drivers.
If a driver is doing something improperly and driver verifier validates it, driver verifier will handle it by crashing your system.
As some drivers can be loaded quite early in the boot process, if driver verifier catches such a driver misbehaving then your system might end up in a boot loop.
A boot loop is 1 of the worst situations that could happen, but there are multiple ways to get out of it and get you back in Windows.
If you would like to do this, please be aware that you should expect your system to crash any second whereafter you might not immediately get back in Windows.
To assist you with these situations, we will provide instructions that you should follow before using driver verifier, like creating a system restore point and recovery media. Macrium is not included as it will remove any traces of the crash.
Only if you understand this and are fine with it, only then I would suggest to do it.
for now we start to see these days as it goes and if problems happen again.
I keep you updated.
P.S: I have already kept the driver aside in case it updates.
Quote