BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ntoskrnl.exe

TaeGuWang Please give us more information about your problem, when it occurs, what programs and

Please fill out your System Specs

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible. We have to, on occasion look up a component, so detailed Manufacturer and model info necessary to do that would make it much easier to help you.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs

You have some unusual circumstances occurring. Numerous times I found this, which I have never seen before

Code:

BUCKET_ID:  CPU_CALL_ERROR
FAILURE_BUCKET_ID:  CPU_CALL_ERROR
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:cpu_call_error
FAILURE_ID_HASH:  {03d3857e-8d42-432f-c638-a5118c31ce68}
Followup: MachineOwner

Which in basic terms seems to mean the CPU was unable to send or receive necessary information

We also have this which is a Windows Update

Code:

ataport
start    end        module name
88b84000 88ba7000   ataport    (pdb symbols)          c:\symcache\ataport.pdb\C9AF9FE9166548FD86EFAC017F6023011\ataport.pdb
    Loaded symbol image file: ataport.SYS
    Mapped memory image file: c:\symcache\ataport.SYS\4CE788E823000\ataport.SYS
    Image path: \SystemRoot\system32\drivers\ataport.SYS
    Image name: ataport.SYS
    Timestamp:        Sat Nov 20 02:38:00 2010 (4CE788E8)
    CheckSum:         0002B87F
    ImageSize:        00023000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ataport.sys
    OriginalFilename: ataport.sys
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  ATAPI Driver Extension
    LegalCopyright:   © Microsoft Corporation. All rights reserved

There were several instances of this

Code:

Use !analyze -v to get detailed debugging information
BugCheck A, {14, 2, 0, 83c874e6}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+5 )
Followup: MachineOwner

Also found this

Code:

Rt86win7
start    end        module name
9aa55000 9aa7a000   Rt86win7 T (no symbols)           
    Loaded symbol image file: Rt86win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt86win7.sys
    Image name: Rt86win7.sys
    Timestamp:        Thu Feb 26 03:04:22 2009 (49A65B16)
    CheckSum:         0002BDEF
    ImageSize:        00025000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which is your Realtek Network connection

There were a few others, but before proceeding too much I need the information I previously asked as well as

Please fill out your System Specs

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs

I would also like you to run

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

And open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

That's up to you. It may help solve some of your problems. Another problem you have is an Asrock retail Motherboard and an OEM_SLP HP Window7 key. An OEM_SLP Key is legal only on the computer it came from the factory installed on. As I am sure you are aware, the only way it can be Activated is to heavily modify protected system files.

Counterfeit installations such as yours contain heavily modified code that causes the installation to behave it unexpected ways. Analyzing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimize the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a Genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them