Windows 10: BSOD Driver_Corrupted_Expool OxC5 - While 3d rendering

Hi guys!

Hope someone can help me out here. The other day while suing my PC and rendering a 3d model. I got this blue screen. I have not yet run Light wave my 3d rendering software yet again since the blue screen but would like to try to figure out what driver has caused this issue. A few months ago i had a similar issue and it had something to do with a USB 3.0 key driver or something that light wave needed. As far as im aware all my drivers are up to date and I cant think of any new software that i Installed recently that would cause an issue. If any more information is required as to the specs of my pc please let me know.

Thanks in advanced.

:)

 

BSOD - DRIVER_CORRUPTED_EXPOOL & DRIVER_OVERRAN_STACK_BUFFER

Hello,

I've been getting a few different BSOD since I've started to do 3D rendering using 3DS MAX. Most common errors are DRIVER_CORRUPTED_EXPOOL & DRIVER_OVERRAN_STACK_BUFFER. Here are 6 recent dump files I've uploaded, can anyone please help me identify the problem.
Thank you.

DUMP FILES:

https://1drv.ms/f/s!AjWUmvzIdGqihVRA_hRFdl8y_jBV

Intel Core i5 4670K @ 3.40GHz

16.0GB Dual-Channel DDR3 @ 800MHz

3071MB NVIDIA GeForce GTX 780 Ti

MSI Z87-G43 GAMING

 

Repeated BSOD

Had another bsod. DRIVER_CORRUPTED_EXPOOL was the stopcode this time. Any ideas?

 

1 of the crashes is caused by a driver from CPU-Z which is showing when CPU-Z opens, update the sofware.
Code: 9: kd> lmvm cpuz138_x64 start end module name fffff801`5ca40000 fffff801`5ca4a000 cpuz138_x64 T (no symbols) Loaded symbol image file: cpuz138_x64.sys Image path: \??\C:\Users\Kirk\AppData\Local\Temp\cpuz138\cpuz138_x64.sys Image name: cpuz138_x64.sys Timestamp: Thu Feb 26 08:04:34 2015 (54EEC582) CheckSum: 0000793A ImageSize: 0000A000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] For the other crash, follow below instructions





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.

 

OK. So i ran Driver Versifier for 48 hours. But no blue screen or crash. So what is the next option. I also updated CPU-Z.