Windows 10: BSOD While Rendering - 0x...0C5 ntoskrnl.exe

Hi, I hope someone can help identify my problem. I had a blue screen while rendering a 3D image on Blender (full CPU load, after about 10 minutes, temperatures where fine). I've done that several times (including on the exact same session) without problems, not sure what caused as I didn't install anything between the point when it didn't happen and the point it did.
I use BlueScreenViewer and it says it's 0x...0C5 caused by ntoskrnl.exe, I would like to know how to proceed and try to fix it.

As you may notice from the attached file this is not the first time I get BSOD on this system, but I don't think the ones from 01/16/16 are related to the one today (02/26/16). Yet, I'm far from being an expert, so they might be. Just wanted to point out I believe the relevant dump file on the .zip is the last one, from today.

Attachment 66574

Thanks in advance to anyone who takes the trouble to look it up.

Best,
Joaquín.

PS: In case it's relevant, I also have that problem where Windows freezes on the desktop after startup, the one that it's suppose to be solved by disabling "Fast start". In my case that did not help, it keeps happening from time to time. I'm pretty sure it's a service not initializing properly, but I couldn't identify which one.

:)

 

BSOD ntoskrnl.exe+142480, 0x00000101, did test: DRIVER_VERIFIER_DETECTED_VIOLATION (avc3.sys)

While last reply I had 3 more BSODS, 3 more .dmps.

All of them were while playing like before.

All of them with those causes:

0x00000101

ntoskrnl.exe+142480

The "0x00000124, ntoskrnl.exe" which I had once in that time seems to be unique.

Done things:

No BSOD

-prime95 4hours

-3dMark Benchmarks

Still BSOD

-deinstalled bitdefender

-deinstalled gigabyte center software with components (oc software etc.)

-installed old nvidia driver

-set ram profile from xmp (3000) to normal 2133

 

Continuing BSOD issue

OK, I will try that for a while. There has only been one more BSOD in the last two days. Again, occurring while the system was idle (Checked for any scheduled activities during that time - none). Again, it was the same fault ntoskrnl.exe +142940.

 

Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.
Code: <ActivePartialProductKey>T83GX</ActivePartialProductKey> <ActiveProductKeyPid2>00331-10000-00001-AA867</ActiveProductKeyPid2> <OSVersion>10.0.10586.2.00010100.0.0.048</OSVersion> <ProductName>Windows 10 Pro</ProductName> <ProcessorArchitecture>x64</ProcessorArchitecture> <EditionId>Professional</EditionId> <BuildLab>10586.th2_release.160126-1819</BuildLab> <TimeZone>Argentina Standard Time(GMT-03:00)</TimeZone> <ActiveSkuId>2de67392-b7a7-462a-b1ca-108dd189f588</ActiveSkuId> <ActiveSkuDescription>Windows(R) Operating System, VOLUME_KMSCLIENT channel</ActiveSkuDescription> <ProductUniquenessGroups>55c92734-d682-4d71-983e-d6ec3f16059f</ProductUniquenessGroups> <ActiveProductKeyPKeyId>08e404fb-41f3-77ac-59ef-6e9f2d3f499d</ActiveProductKeyPKeyId> <ActiveProductKeyPidEx>03612-03311-000-000001-03-11274-10586.0000-0162016</ActiveProductKeyPidEx> <ActiveProductKeyChannel>Volume:GVLK</ActiveProductKeyChannel> <ActiveVolumeCustomerPid>55041-00168-313-562954-03-1033-7601.0000-2242014</ActiveVolumeCustomerPid> <OfflineInstallationId>364552304152003677215859785353404346920265749658132149049181606</OfflineInstallationId> <DomainJoined>false</DomainJoined>[/quote] Forum rules