Thanks.
If you are overclocking any hardware, please stop.
Bug checks:
1. STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL BSOD Index Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
2. STOP 0x0000001A: MEMORY_MANAGEMENT BSOD Index Usual causes: Device driver, memory, kernel
3. STOP 0x00000019: BAD_POOL_HEADER BSOD Index Usual causes: Device driver
Code:
Start Menu\Programs\ASRock Utility Public:Start Menu\Programs\ASRock Utility Public
Start Menu\Programs\avast! Free Antivirus Public:Start Menu\Programs\avast! Free Antivirus Public
Suggestions:
Recommend removing your ASRock utilities through Start Menu -> Control Panel -> Uninstall a program. They can provide software interfaces with the hardware for overclocking, and even when the overclock is not enabled, that interface can cause instability. They are also not needed for the system to function properly and may reduce system resources.
Please uninstall Avast! antivirus and keep MSE while we troubleshoot with your computer.
Microsoft Security Essentials - Free Antivirus for Windows
After uninstalling these, run memtest86+ on each stick for 8 passes preferably overnight:
RAM - Test with Memtest86+
Post back results
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff8a01b4f6260, 7ffff8a01b4f6260, fffff8a01b4f6260}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )
Followup: Pool_corruption
---------
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {5002, fffff70001080000, e643, 8000e644fffffffe}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+464b8 )
Followup: MachineOwner
---------
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa8018e6e010, 2, 1, fffff80003192366}
Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )
Followup: MachineOwner
---------
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.