New
#11
I have new bsods for you, one from before driver verifier, and two after. They occurred during gaming and startup.
Attachment 101857
I have new bsods for you, one from before driver verifier, and two after. They occurred during gaming and startup.
Attachment 101857
Sorry it's taken so long for me to respond. Life sort of got in the way for a bit.
Only two new dumps form the 17th in the zip file. Neither has Verifier data in it. Both respond with:
so it looks like Driver Verifier was not enabled. Please try it again and make sure you follow the instructions exactly.Code:2: kd> !verifier fffff803b455d780: Unable to get verifier list.
No problem, my response also did take some time.
So I tried verifier again and this time I got bsods right on startup.
Here are the files:
Attachment 104099
To clarify, the error codes I got are IRQL_NOT_LESS_OR_EQUAL, and occurred on the same time as I submitted this reply.
The latest dump indicates a problem with MBfilt64.sys.
This belongs to Creative Audio Driver. It's very old, 31/07/2009.Code:BugCheck A, {1000000a, 2, 0, fffff800c7f3a018} *** WARNING: Unable to verify timestamp for MBfilt64.sys *** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys Probably caused by : MBfilt64.sys ( MBfilt64+1817 )
Please see if you can update your Creative audio driver to a much newer level.
So after all this time without a bsod I got two new ones yesterday and today.
While writing this I am running driver verifier again, indicating it doesn't find a problem at this moment.
I tried to fix the first one by updating my graphics driver.
Attachment 108996
Neither of the new dumps contains any verifier data.
Make sure Verifier is setup as indicated in the link I provided.
I got a bsod during gaming with driver verifier active, it took a day for it to happen.
If the latest bsod still isn't what you need, then I don't know what I did wrong, as I followed every given step to enable verifier.
Attachment 109225
I don't know what is going on with this either as all 2 of the latest dumps, 2 from 11/6 and one from 11/7 contain no verifier data.
You could try DDU and get the latest Nvidia driver again since 375.76 is now availabel (you have 375.70).Code:0: kd> !verifier fffff801bc58f000: Unable to get verifier list.
Also, we haven't tried testing your RAM yet. I suggest removing half and running for awhile, see if any BSODs occur.
If no, swap installed and removed RAM and test again. If yes, you can remove half of the remaining 8GB leaving 4GB then test. Repeat as needed till you find the bad one.
Alternatively you can run memtest86+ (note the +) overnight for a minimum of 8 full passes as follows:
===================================================
RAM:
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
Information
MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:
- RAM will accept and keep random patterns of data sent to it
- There are no errors when different parts of memory try to interact
- There are no conflicts between memory addresses
Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.
WarningMemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.
If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.
NoteMemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.
Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
Hello,
My PC just froze and made a loud buzzing noise during gaming.
Also, I have run memtest86+ for 2 consecutive days not long before I started this thread, without any errors, however I did that with all my RAM modules, so do I need to do it again, the way you told me?
I also installed the new GPU driver update, after DDU, and updated my windows drivers, still received a bsod.
I guess I'll check for other driver updates too.
Latest bsod info, but I doubt it's useful: Attachment 109467
Last edited by potatocrisps; 09 Nov 2016 at 17:10.
Are you still using a Microsoft mouse and keyboard? If so, the driver for it is old, from 2012 so see if a newer one is available.
You haven't tested memory yet so that would be a good thing to do. With 16GB it's going to take 12 hours or more so an overnight run would be the best way to go:
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:
- RAM will accept and keep random patterns of data sent to it
- There are no errors when different parts of memory try to interact
- There are no conflicts between memory addresses
Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.
WarningMemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.
If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.
NoteMemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.
Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.