We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask

I suspect it is your 360 that is causing the issue.  Please run driver verifier to confirm this

Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.


If you are over-clocking anything reset to default before running these tests. In other words STOP!!!  If you do not know what this means you probably are not

1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)

those really helps, it comes out to be kprocesshacker.sys

i still need some time to disable it. it will be loaded after i login.

but even i didnt login, it would crash.

Might want to upload the verified dump.

i met the previous problem(0x109) again...

so i setup the vedifier again, and i met a new problem:KMODE_EXCEPTION_NOT_HANDLED (1E)

here is the dump files http://1drv.ms/1GTko7Q

im wondering if it is efficient to go through a driver verification.

Hi,

Since this thread has been marked, we suggest you open a new thread with new title and new DMP file link, so everyone can see it and you might get more effective suggestions.

Check the resolution section from this webpage

Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557408%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

For this debug error, driver verification is helpful since it is normally caused by problematic driver. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

Regards,

D. Wu

A new thread? But I don't know what title to use.(Actually i didn't finish the verification. Problems just come up continually. So I deleted the suspicious drivers and the problem 0x107 is gone(with verifier setup)).

Suspicious dirvers(deleted):

kdhacker64.sys(belongs to Kingsoft Co.) and another 3 drives provided by Kingsoft Antivirus Software.

The dump file related to kdhacker64.sys:http://1drv.ms/1TjcA8g

All dump files:http://1drv.ms/1TjcFbS (some of them founded at C:\)

This is my first time going through such kind of processes.I have to reboot the machine(even in secure mode) manually several times during the verification. 

I should not have installed Kingsoft and 360 togather...

Unsure where you are and what you are doing..  I would start by removing both Klingsoft & 360 and running a system file check & DISM

Please run a system file check (SFC) & DISM (if necessary) if you are on win 8 or higher
All instructions are in our Wiki article below...
Should you have any questions please ask us.

System file check (SFC) Scan and Repair System Files

SFC&DISM is OK.

I think its just a random accident. Just let it go.

• Marked as answer by Deason WuMicrosoft contingent staff, Moderator 6 hours 29 minutes ago

SFC&DISM is OK.

I think its just a random accident. Just let it go.

• Marked as answer by Deason WuMicrosoft contingent staff, Moderator Friday, July 10, 2015 12:53 AM

SFC&DISM is OK.

I think its just a random accident. Just let it go.

• Marked as answer by Deason WuMicrosoft contingent staff, Moderator Friday, July 10, 2015 12:53 AM