New
#30
hey i just followed your instructions which are very goodbtw :)
what will this do? will it test all the drivers i have selected for problem or what?
I tried to use this and that was impossible because my pc crashed before Windows even started to load. Had to Go into safe mode to disable Verifier.exe for my PC to boot into windows Any help please..
That's the whole idea: any bad driver will instantly crash your system and generate a minidump file with crash information, if you enabled minidump files to be written to your Windows folder before using verifier. To switch verifier off, simply boot in Safe Mode open verifier again and disable it.
Ran the verifier and had to restart manually. Upon restart Windows didn't start normally and had to perform a Repair and then a System Restore. Any ideas?
In the end, in my case, it was bad memory...
I put off the memory test since it's new but there's still the possibility it may be bad. I'll run MEMTEST to check. Thanx for the info.
Hi, I followed the instructions but the computer was unable to restart normally.
I started in Safe Mode and changed the settings back
Not sure where to go from here any advice appreciated
a copy of the Whocrashed report as follows
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 08/08/2014 09:40:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080814-16754-01.dmp
This was probably caused by the following module: netbt.sys (netbt+0x24D30)
Bugcheck code: 0xC9 (0xC, 0xFFFFFFFF8891B380, 0xFFFFFFFF9D6B8F68, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\netbt.sys
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: MBT Transport driver
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Hello Mike, and welcome to Seven Forums.
See if you may be able to do a system restore (in safe mode or at boot) using a restore point dated before this happened to hopefully undo and fix it for you.
Hope this helps for now, :)
Shawn
Hi Brink, thanks for your response, I am still working on the problem ( when I do not need the computer )
My next move was to decrease the amount of drivers selected to just the first 10 and the result was the same
Next time I shall limit it to the first 5
Iam also checking/updating drivers