Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Stress test the CPU.
Hardware - Stress Test With Prime95
Seatool for dos: SeaTools | Seagate download
- Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
Update JMicron JMB36X Controller driver from ftp://driver.jmicron.com.tw/SATA_Controller/Windows/
If bluetooth is not needed, disable it. Otherwise update the driver from manufacturor's site.
Let us know the results.
_________________________________________________________________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff800039914ed, fffff880031bc798, fffff880031bbff0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800039914ed, The address that the exception occurred at
Arg3: fffff880031bc798, Exception Record Address
Arg4: fffff880031bbff0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!RtlpNewSecurityObject+11d
fffff800`039914ed 0000 add byte ptr [rax],al
EXCEPTION_RECORD: fffff880031bc798 -- (.exr 0xfffff880031bc798)
ExceptionAddress: fffff800039914ed (nt!RtlpNewSecurityObject+0x000000000000011d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
CONTEXT: fffff880031bbff0 -- (.cxr 0xfffff880031bbff0)
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a000006630
rdx=0000000000000000 rsi=fffffa80066fe080 rdi=fffff880031bcf30
rip=fffff800039914ed rsp=fffff880031bc9d0 rbp=fffffa80066fe0cc
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff8a000006630 r12=fffffa800998e5f0 r13=fffff880031bcf10
r14=fffffa80066ed5f0 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!RtlpNewSecurityObject+0x11d:
fffff800`039914ed 0000 add byte ptr [rax],al ds:002b:00000000`00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800038b8100
GetUlongFromAddress: unable to read from fffff800038b81c0
0000000000000000 Nonpaged pool
FOLLOWUP_IP:
nt!RtlpNewSecurityObject+11d
fffff800`039914ed 0000 add byte ptr [rax],al
BUGCHECK_STR: 0x7E
LOCK_ADDRESS: fffff80003884be0 -- (!locks fffff80003884be0)
Resource @ nt!PiEngineLock (0xfffff80003884be0) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff80003884be0
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff8000396d0f2 to fffff800039914ed
STACK_TEXT:
fffff880`031bc9d0 fffff800`0396d0f2 : fffff880`031bcf10 fffffa80`0998e5c0 fffffa80`066fe080 fffff8a0`011f3970 : nt!RtlpNewSecurityObject+0x11d
fffff880`031bcc60 fffff800`03963c27 : 00000000`00000000 fffffa80`0998e5a0 fffffa80`0998e5c0 00000000`00000000 : nt!ObpAssignSecurity+0x82
fffff880`031bccd0 fffff800`0397bd27 : fffff880`031bcf10 fffffa80`0998e5f0 fffffa80`08ca68a0 00000000`00000250 : nt!ObpInsertOrLocateNamedObject+0x14b
fffff880`031bcd90 fffff800`0396c046 : fffffa80`00000000 fffffa80`0998e5f0 00000000`00000000 fffff880`031bd000 : nt!ObpCreateHandle+0x687
fffff880`031bcea0 fffff800`038e6e02 : fffffa80`00000188 fffff880`031bd100 fffffa80`0998e5c0 fffff800`0366137a : nt!ObInsertObjectEx+0x276
fffff880`031bd0f0 fffff800`03a6b4a7 : 00000000`00000188 fffff880`028920f8 00000000`00000000 00000000`00000000 : nt!ObInsertObject+0x22
fffff880`031bd140 fffff800`03aff4d0 : 00000000`00000001 00000000`00000000 fffff880`031bd6e8 ffffffff`800002d4 : nt!IopLoadDriver+0x727
fffff880`031bd410 fffff800`0393cfbe : 00000000`00000001 fffff880`00000000 fffff8a0`011cc720 00000000`00000000 : nt!PipCallDriverAddDeviceQueryRoutine+0x390
fffff880`031bd510 fffff800`0393ccce : ffffffff`800002dc 00000000`00000000 fffff880`031bd720 fffff880`031bd6e8 : nt!RtlpCallQueryRegistryRoutine+0x106
fffff880`031bd590 fffff800`03a6ea5c : fffffa80`09988510 00000000`00000000 00000000`c0000034 fffff880`031bd6e8 : nt!RtlQueryRegistryValues+0x17e
fffff880`031bd660 fffff800`03a701f2 : fffffa80`09988510 fffffa80`09988510 00000000`00000000 fffff8a0`0000004c : nt!PipCallDriverAddDevice+0x45c
fffff880`031bd810 fffff800`03a70768 : fffff800`03882560 00000000`00000000 00000000`00000001 fffff800`038ed6e8 : nt!PipProcessDevNodeTree+0x2b2
fffff880`031bda80 fffff800`03783817 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`031bdad0 fffff800`0368a261 : fffff800`037834f0 fffff800`03978a01 fffffa80`06703100 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`031bdb70 fffff800`0391ebae : 00000000`00000000 fffffa80`06703170 00000000`00000080 fffffa80`066ed5f0 : nt!ExpWorkerThread+0x111
fffff880`031bdc00 fffff800`036718c6 : fffff880`02f65180 fffffa80`06703170 fffff880`02f6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdc40 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bc9d0 00000000`00000000 : nt!KxStartSystemThread+0x16
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff800039914e0 - nt!RtlpNewSecurityObject+110
[ 89:81 ]
1 error : !nt (fffff800039914e0)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT
STACK_COMMAND: .cxr 0xfffff880031bbff0 ; kb
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
---------
Quote