Your crashes are hardware related, please fill in your system specs in the lower left corner in any of your posts.
This free program will help you find all the information.
SIW - System Information for Windows
This is the latest crash dump report, it blames STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
Run memtest86+ with all your RAM cards installed.
Run a full 7 passes, this may take 12 hours or more with 8GB RAM, best to let it run overnight.
RAM - Test with Memtest86+
Post this information first, it will help to diagnose the RAM as the possible cause of the crashes.
D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information, enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000004d3021b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000308eb21, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b2100
000000004d3021b8
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiInsertTimerTable+171
fffff800`0308eb21 4c3b7df8 cmp r15,qword ptr [rbp-8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9c370 -- (.trap 0xfffff80000b9c370)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000009858 rbx=0000000000000000 rcx=0000000000020994
rdx=fffffa8008e98140 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000308eb21 rsp=fffff80000b9c500 rbp=000000004d3021c0
r8=fffff8000321cf90 r9=000000000000006d r10=fffff800031f5e80
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe cy
nt!KiInsertTimerTable+0x171:
fffff800`0308eb21 4c3b7df8 cmp r15,qword ptr [rbp-8] ss:0018:00000000`4d3021b8=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030822a9 to fffff80003082d00
STACK_TEXT:
fffff800`00b9c228 fffff800`030822a9 : 00000000`0000000a 00000000`4d3021b8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c230 fffff800`03080f20 : ffffffff`ffffffff ffffffff`ffffffff 00000000`00000000 fffff800`0321cf50 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c370 fffff800`0308eb21 : fffff800`031f5e80 fffff800`00b9cc58 fffff800`03203cc0 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c500 fffff800`0308b65a : ffffffff`fffb6c20 fffff800`0308e652 00000000`00000001 00000000`00000000 : nt!KiInsertTimerTable+0x171
fffff800`00b9c560 fffff800`0308e49d : fffff800`0321cf50 00000000`0000206a 00000000`00000000 00000000`00000000 : nt!KiTimerWaitTest+0x15a
fffff800`00b9c5e0 fffff800`0308e3de : 00000000`4d2d311c fffff800`00b9cc58 00000000`0000206b fffff800`031f8fe8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00b9cc30 fffff800`0308e1c7 : 00000000`1a9815c1 00000000`0000206b 00000000`1a9815a9 00000000`0000006b : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`0307aa2a : fffff800`031f5e80 fffff800`03203cc0 00000000`00000000 fffff880`01032f5c : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiInsertTimerTable+171
fffff800`0308eb21 4c3b7df8 cmp r15,qword ptr [rbp-8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiInsertTimerTable+171
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b
FAILURE_BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+171
BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+171
Followup: MachineOwner
---------
Follow the instructions here to correct this error.
Code:
error
symptom: tv_ConfigMgrErr24
cause: A device has a configuration problem that prevents it from working properly.
details: The device, AsIO, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_ASIO\0000.
resolution: 1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.
These are driver errors, Uninstall all the Asus hardware monitoring software including PCProbe, these have been known to cause crashes.
Once the system is stable you can try installing them one at a time to see if they will cause any problems.
You have a Gigabyte motherboard, did you install these Asus apps?
Do you have an Asus graphics card?
cdrom is a windows driver, leave it for now and we'll see if it comes up again.
Code:
Event[67]:
Log Name: System
Source: Service Control Manager
Date: 2011-06-06T11:37:57.893
Event ID: 7026
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: STGDEV2
Description:
The following boot-start or system-start driver(s) failed to load:
AsIO
AsUpIO
cdrom
Another crash, STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred.
The CPUZ snips will help with this error, this usually indicates the RAM settings need adjusted or bad RAM.
Code:
Event[128]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-06-06T11:37:13.000
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: STGDEV2
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000411, 0xfffff680000417f0, 0x8ca00001c0eeb824, 0xfffff680000417d1). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060611-32011-01.
Update the MSE virus definitions, these are available through Windows Update, if they are not set to automatically install you will need to check these every day.
I get MSE virus definitions daily.
Code:
Event[176]:
Log Name: System
Source: Microsoft Antimalware
Date: 2011-06-06T08:06:51.000
Event ID: 3002
Task: N/A
Level: Error
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: STGDEV2
Description:
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
Feature: Behavior Monitoring
Error Code: 0x80004005
Error description: Unspecified error
Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.
Your events log shows a lot of app crashes with no information or explanation, this is usually caused by hardware faults.
Looks like classic Ram issues.
The CPUZ snips are most important, post them soon as you can.
Quote