Critical_structure_corruption bsod

You are required to remove every bypass/crack on your system before we proceed.

Counterfeit programs causes the system to behave in unexpected ways what makes troubleshooting unreliable.
For this reason we won't try it and will not give support until all the bypasses have been removed.
Note, this does NOT mean the bypasses are causing the crash.

Forum rules

4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).

Code:

127.0.0.1 lmlicenses.wip4.adobe.com
127.0.0.1 lm.licenses.adobe.com
127.0.0.1 na1r.services.adobe.com
127.0.0.1 hlrcv.stage.adobe.com
127.0.0.1 practivate.adobe.com 
127.0.0.1 activate.adobe.com
127.0.0.1 activate-sea.adobe.com  
127.0.0.1 activate-sjc0.adobe.com
127.0.0.1 practivate.adobe.com  
127.0.0.1 ereg.adobe.com  
127.0.0.1 activate.wip3.adobe.com  
127.0.0.1 wip3.adobe.com  
127.0.0.1 3dns-3.adobe.com  
127.0.0.1 3dns-2.adobe.com  
127.0.0.1 adobe-dns.adobe.com  
127.0.0.1 adobe-dns-2.adobe.com  
127.0.0.1 adobe-dns-3.adobe.com  
127.0.0.1 ereg.wip3.adobe.com  
127.0.0.1 wwis-dubc1-vip60.adobe.com

Please run the dm log collector again, so nobody gets confused with this :)

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:


The single dump from your first upload doesn't contain anything useful.

Code:

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Following a generic and specific usual cause, please enable driver verifier to find any problematic driver.
Read the instructions carefully!

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

No, the ntoskrnl.exe file is the last file to blame.
If everything else cannot be blamed this file is blamed.
However, this Windows file is used in the boot process, if it is the cause then you would have much more problems.
Also, Windows drivers are rarely the real cause, in almost every case you can assume it is not the real cause.