Windows 10: Here is my Dump file per instructions,

Neither of the crash dumps are seeming to be driver verifier enabled.
They are not listing up the verifier properties.
Code: 1: kd> !verifier fffff803e58f47a0: Unable to get verifier list.[/quote] And the DEFAULT_BUCKET_ID is not also pointing to verifier.
Code: DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT[/quote] When it is verifier enabled, it states VERIFIER_ENABLED_MINIDUMP.

Please make it sure that you have enabled verifier properly. Open a command prompt and enter verifier /query.

If a verifier enabled computer yields such dumps, then it is a strong indication of a hardware related issue.
Code: BugCheck 1000007E, {ffffffffc0000005, fffff8010c8961b2, ffffd000d0fa0db8, ffffd000d0fa05d0} Probably caused by : dxgmms2.sys ( dxgmms2!VIDMM_SEGMENT::ReserveResource+462 ) Followup: MachineOwner ---------[/quote] Code: BugCheck 3B, {c0000005, fffff801f871ab9f, ffffd001ec72e640, 0} Probably caused by : NTFS.sys ( NTFS!NtfsFsdCreate+42f ) Followup: MachineOwner ---------[/quote] ** READ FROM HERE FIRST:
EDIT: Wait a bit ....before doing anything further, please uninstall (not disable, disabling will not stop loading the modules) Trend Micro Maximum Security, at least on a test basis. Activate Windows Defender.
Code: ffffd001`ec72eee8 fffff801`f8e38c11Unable to load image tmcomm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for tmcomm.sys *** ERROR: Module load completed but symbols could not be loaded for tmcomm.sys tmcomm+0x8c11[/quote] Code: ffffd001`ec72ee98 fffff801`f9843f98Unable to load image tmevtmgr.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for tmevtmgr.sys *** ERROR: Module load completed but symbols could not be loaded for tmevtmgr.sys tmevtmgr+0x3f98[/quote] Now let the computer run and keep a sharp observation on it (with verifier disabled) for at least next 24 hours. See how it goes. Let us know.

 

Trend Micro is uninstalled. I have run their anti-viral software since the mid-1990's. I have become increasingly unhappy with it. It has become bloatware. Trend Micro's password vault is a bad joke. Windows Defender is very good.

 

All the security programs have their own pros and cons. *Smile
Here we are uninstalling Trend Micro because a couple of its modules are flagged in the dumps, for the purpose of troubleshooting. If the uninstallation does not make any good, we will not have anything to say against Trend Micro.

Let us see how it goes.

 

I looked it up and Tmevtmgr.sys file is a known issue with Trend Micro which can cause all of the BSOD types I have been getting. Even though I have uninstalled Trend Micro this file still is on my boot drive should I delete it?

 

If it is still there even after uninstalling Trend Micro, feel free to delete it.

 

This resides in the install file, After reading up on Trend Micro it is not going to be reinstalled. BitDefender is number 1 right now and has been for several years.

 

I seems my BSOD problem is finally solved. A note to Trend Micro told me the fix was to completely uninstall and reinstall the Trend Micro package. I am am going to give things a couple of weeks before I do that. If the BSOD resume I will know what to do. Thanks Arc, you fixed me up. I'll declare this issue solved.

Now the only issue I have left is my screen freezing randomly necessitating a restart. Can you point to a thread here the covers this issue.

 

Well done on the BSOD issue. *Thumbs

For the screen freezing issue, IMHO Performance Maintenance - Windows 10 Forums would be the best place.

 

looks like I spoke too soon; *Sad woke up to this BSOD this morning;

From "WhoCrashed":
On Fri 6/24/2016 07:24:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062416-26625-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800C91CE71C, 0xFFFFD001334499C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

What Driver????? I guess I can run the Driver Verifier again and this time configure it correctly. This is getting very, very, very..........very old. Gosh I miss XP it ran, and ran, and ran. But Windows 10 has WASPI which the Radeon graphic's card uses with it's AMD True Audio feed to the Onkyo AVR, great sound. Phooey I built this PC to be the hotrod I have always wanted, not that I needed it I just wanted it. I would have just purchased an iMac but I have been a PC man for 35 years it is hard to change.

Mean while........Siri talking from the iPad is saying come to Apple*Wink

 

Let us see the crash dump?

 

Looked at what "WhoCrashed":told me and it picked up on the Trend Micro Problems, and it also showed problems earlier with the drivers for the Radeon P9 380 graphic card. blew those out and reinstall them. I will get the crash dump for you. .

 

OK lets get this is the correct thread......*Redface

Here is the requested dump file.

Attachment 86612

 

The latest crash dump is not flagging a specific module, but shows a 0x3B BSOD.

A 0x3B may be the following things:

• A device driver malfunction
• A failing RAM .... that we have already nullified as the cause.
• Something else passing bad info to the memory. It may be anything including a third party antivirus.
• Faulty system services.

Now, As the RAM is free from errors, IMHO it would be the best to go for a clean install; because that will blow out all the other possibilities in a single go. Just make two things sure:

• Get the driver updates via windows update
• Use Windows Defender as your antivirus. If extra security is needed, opt for MBAM.

Dont use the driver CD that came with the motherboard. Go to ASUS, get the network drivers for your motherboard, save them externally. If the clean install does not accept the network driver automatically, then apply it, and get the rest of the drivers via windows update.

IMHO it will be the right step at this stage.

 

That is what I am beginning to think myself, a real PIA. Would it do any good to do a repair run, I have a full version DVD of Windows 10 home? Frankly this has never worked in the past would it be worth a tried this time. Steve Gibson at GRC has a utility I might try what is does is it pulls off all of the non Microsoft drivers and puts them in a separate file that you can put else where when you get done with the clean install you can then selectively reload these drivers, all of the or one at a time.

 

I was looking up the OEM windows 10 Home purchase I made from Amazon. I purchased W10 Pro, and the packaging was marked as such. But after I loaded it turned out to be Windows 10 Home. Amazon made it good by refunding me the difference. The OS updates OK and and is varified by Microsoft over the phone. Looking at the reviews on Amazon of what I purchased I am beginning to wonder if what I have is a fake copy. A bunch of others have complained about the same thing I did. I wonder if I should purchase a new copy but this time directly from Microsoft.