Enter your system specs in the "My System Specs' drop box in any of your posts.
This will help:
Speccy Free System information Utility
Be sure to include PSU information.
What BIOS version did you flash to?
If not 1.60, then flash back to it.
Are you overclocking anything in your system?
Uninstall all ASRock Utilities, these are known to cause system instability.
Did you run the Avira uninstaller?
Check this site for info:
Instructions for manual uninstallation
Which ATI graphics card driver are you using now?
Uninstall ATI CCC, or get the driver without it.
Did you re-seat the graphics card as Arc recommended in post#8?
When you take it out make sure the slot and pin on the card are clean and free of any debris.
Significant crash from 12 Oct.
Code:
STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT
Usual causes: Device driver, BIOS bug, hardware defect
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) - can be caused by several things, needs further investigation.
Arg4: 0000000000000002, 0. - error from processor #2
STACK_TEXT: indicates > amdppm!C1Halt+0x2 - [COLOR="red"]amdppm[/COLOR] is the Windows Processor Device Driver
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_3_PROC_ANALYSIS_INCONCLUSIVE (actual processor #2 when starting from processor #0)
This is telling us that the CPU (processor) hung, failed to process information that was asked in a timely fashion.
We need to figure out what caused the CPU to not be able to resume from a interrupt request.
As mentioned above it can be caused by a device driver, BIOS or hardware defect.
The device driver that seems to keep coming up is the ATI graphics driver.
You mentioned that the crashes started when you updated the to BIOS version 1.70.
This is a CPU issue, might not be caused by the CPU, but needs to be checked.
17 crashes since your last download.
The last crashes:
Code:
STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Usual causes: Device driver, Memory
Probably caused by : [COLOR="Red"]amdppm.sys[/COLOR] ( amdppm!C1Halt+2 )
IMAGE_NAME: amdppm.sys
FAILURE_BUCKET_ID: X64_0xBE_amdppm!C1Halt+2
From the crash on 12 Oct. and the 0xBE crash, in a clean install, leads to blame hardware.
We need some information.
Can you
download 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
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.
After we get some information, check system settings and voltages, system temps, we can run OCCT CPU test. This will give some information that will help to analyze the cause.
Code:
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_iEndpointInsertStateList+c4 )
PROCESS_NAME: csrss.exe
IMAGE_NAME: USBPORT.SYS
FAILURE_BUCKET_ID: X64_0xD1_USBPORT!USBPORT_iEndpointInsertStateList+c4
The stated cause is a windows driver and likely not the cause, so let's look at hardware.
What devices do you have connected to you computer?
Disconnect anything that is not required, leave only keyboard and mouse connected.
Post a list of devices you have had connected, and what remains connected.
Code:
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
Probably caused by : hardware ( nt!IoRemoveIoCompletion+264 )
IMAGE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
Confirming the first two crashes above.
Code:
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
PROCESS_NAME: System
FAILED_INSTRUCTION_ADDRESS: +000000000`34dafab4
IMAGE_NAME: ntkrnlmp.exe
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
Inconclusive.
Code:
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
FAULTING_IP: nt!KiDpcInterrupt+d5
FAILURE_BUCKET_ID: X64_0x50_nt!KiDpcInterrupt+d5
Blaming hardware.
The System Events Log stops at 12 Oct.
Is this the current logs?
From your System Events Log:
Code:
Event[17306]:
Log Name: System
Source: Service Control Manager
Date: 2012-10-12T11:15:13.031
Event ID: 7000
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Ivan-PC
Description:
The AODDriver4.2.0 service failed to start due to the following error:
The system cannot find the file specified.
Event[16446]:
Log Name: System
Source: Service Control Manager
Date: 2012-10-11T19:33:30.171
Event ID: 7000
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Ivan-PC
Description:
The AMD FUEL Service service failed to start due to the following error:
The system cannot find the file specified.
This is from the motherboard utilities, uninstall all Asrock utilities.
Code:
Event[3394]:
Log Name: Application
Source: Microsoft-Windows-WMI
Date: 2012-10-12T10:27:09.000
Event ID: 10
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Ivan-PC
Description:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
This is a CPU errror, usually caused by overheating.
