New
#21
Ok as soon as i get back to the job i will let u know
Ok as soon as i get back to the job i will let u know
After leaving the laptop playing 4 hours of youtube videos it seem to be ok so will let you know if this comes back to us, and will post the next one if it does.
Another BSOD for you guys,
Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
WarningBefore enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point manually before enabling DV.
Test your RAM modules for possible errors.Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
Let us know the results, with the subsequent crash dumps, if any.
Now we have a new one.
We have check the HDD, done a external chkdsk and local chkdsk,
We have already done a 24 hour memtest and changed the memory.
Here is the BSOD:
The last crash is caused by McAfee Host Intrusion Detection Link Driver.
Description here: Driver Reference Table - mfehidk.sysCode:fffff880`06b27298 fffff880`015bdfdcUnable to load image \SystemRoot\system32\drivers\mfehidk.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for mfehidk.sys *** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys mfehidk+0x42fdc
Uninstall McAfee Using McAfee Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.
Let us know the results.
Hi Arc,
I know it been a long time, that did fix the computer many thanks,
I was wondering if you could help with another one that has had my team confused,
We have just built a brand new system:
CPU: AMD FX 6300
RAM: 4GB
SSD: 120GB
HDD: 1TB
Motherboard: Asus M5A78L-M LE
Once installing Windows 7 to the system it will get to the completing installation then after around 5 mins of sitting there it will then BSOD with a 0x00000101,
We are so confused as why this would do this on brand new stock,
We had a dead identical system built at the same time and that one is running fine.
Could you please help us with our investigation.
Many thanks
Yellowstone
As it is a different PC, and a different issue, start another thread for it. And, put the details in your system specs for that PC.
See your system specs and fill it up here.