Windows 10: Bsod - kmode_exception_not_handled

Hi,

I got this error twice this week. I was just doing regular work with Visual Studio, Chrome, Spotify, Dropbox, TotalCmd running. I checked MEMORY.DMP with WinDbg on the crash today and it shows chrome.exe as the process where the error happened but I guess it could be hardware error and nothing related to Chrome.

:)

 

KMODE_EXCEPTION_NOT_HANDLED(RTKVDHA.sys)

my computer frequently started to have a new BSOD. KMODE_EXCEPTION_NOT_HANDLED(RTKVDHA.sys). can you help me solve this problem?

 

BSOD system_service_exception Windows 10 + DMP files

Thank you for your prompt reply. I ran malewarebytes and nothing was found. Interestingly I encountered too other BSOD !!! KMODE_EXCEPTION_NOT_HANDLED and system_thread_exception_not_handled. I actually got this device last week and all these BSODs!!!

 

You are required to remove all programs that have been illegal activated before any support may be provided.
Forum rules

 

I am sorry but I am not aware of any illegally activated software on my PC. I have Windows 10 through my university (Dreamspark Windows 7 upgraded to Windows 10), Total Commander is activated with license provided by my university, Visual Studio 2015 Community (where WinDbg is included i believe) is a freely available software, so are Dropbox, Spotify and Chrome.

 

Code: 127.0.0.1 activate.adobe.com[/quote]

 

[/quote] Ah, you caught me with my pants down, I am sorry. I deleted the Adobe apps and uploaded new system info archive.

 

Update this driver Driver Reference Table - aksdf.sys and run driver verifier to see if it catches something.





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.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
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.