Bsod : Kmode_exception_not_handled

Concerned about the validity of Windows 10 on this computer since you are using KMS.

I heard after x amount of times it stops being valid

Not true. Once Windows 10 is activated the digital license is stored on the Windows servers and you can then install it as many times as you want.

Please activate the install and run the V2 log collector again and upload the zip file. Once I can verify it's a legally activated install I (and others) will see what we can find out about your problem.

Thanks for the explanation.

Zassie said:

I heard after x amount of times it stops being valid

For Windows 8.1 and below that is true yes, Windows 10 deals with a different kind of activation. Windows 10 activation the first time around does need a key, but once the key is entered you will normally not need a key again for reactivation. It does this by binding your key to your account.

See Link Microsoft Account to Windows 10 Digital License

Sorry, but now it shows as ActiveSkuDescription : Windows(R) Operating System, VOLUME_MAK channel.
What I'm expecting to see is Retail or OEM_DM channel.

Where did VOLUME_MAK come from?

Okay, that's fine, thanks. Onward.

I see 5 of these in the System event log:

Code:

Event[2252]:
  Log Name: System
  Source: volmgr
  Date: 2020-06-18T17:52:32.2350000Z
  Event ID: 161
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-AFL1NRM
  Description: 
Dump file creation failed due to error during dump creation.

No indication of what failed though, never is. This is why there is only one dump in the zip file.

Let's start by checking RAM and hard drives.

Looks like you have

Crucial_CT256MX100SSD1 250GB
Samsung SSD 970 EVO 250GB C:
WDC WD10EADS-00L5B1 1TB

C: is on the Samsung.

===================================================
Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review

Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They 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

They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

   Warning

MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.

If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

   Note

Both of these diagnostics 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+ or 4+4 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 it overnight, starting just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

===================================================
HDD TEST

Run HDTune to

• check the health,
• scan for errors, not quick scan but full scan
• run a benchmark.

Run CrystalDiskInfo Portable and CrystalDiskMark Portable to

• Check health of drive
• Check performance of drive

Run SeaGate SeaTools for Windows (test ALL hard drives - HDD/SSD/USB/etc)

You can also try the various options available with chkdsk.

Test the Samsung first then the Crucial SSD. Test the 1TB WDC last as it will take the longest.

These tests will take a long time to run so some of them can run over night. If none of them show problems then run Driver Verifier as follows:

Run Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

If you have questions, see this additional tutorial which may help to clear things up.

Enable and Disable Driver Verifier in Windows 10

Any error or failures please take a picture and post in this thread. For the RAM test, any error means defective ram that needs to be replaced. The tutorial tells you how to uidentify the bad DIMM.