If you are overclocking any hardware please stop.
AMD OverDrive
Code:
AODDriver2.sys * * * * * * *Thu Apr *5 15:23:37 2012 (4F7D6499)
(AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems. Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program. Then, download (but DO NOT install) a fresh copy of the ATI drivers from
Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page) Use this procedure to install the DRIVER ONLY:
ATI video cards - DRIVER ONLY installation procedure
If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item. Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect. Sometimes the driver remains and continues to cause BSOD's.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {114e2394, 2, 1, fffff88005611758}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_UsbDoneDpc_Worker+38 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000114e2394, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88005611758, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc4100
GetUlongFromAddress: unable to read from fffff80002cc41c0
00000000114e2394 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Core_UsbDoneDpc_Worker+38
fffff880`05611758 4c8b4f40 mov r9,qword ptr [rdi+40h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: TurboV_EVO.exe
TAG_NOT_DEFINED_c000000f: FFFFF880030B7FB0
TRAP_FRAME: fffff880030b7ce0 -- (.trap 0xfffff880030b7ce0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000114e2394 rbx=0000000000000000 rcx=fffffa8007de61d0
rdx=0000000043787254 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005611758 rsp=fffff880030b7e70 rbp=fffffa8009ac51a0
r8=0000000043787254 r9=00000000ffffffff r10=fffffa8009ac51a0
r11=0000000000026161 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
USBPORT!USBPORT_Core_UsbDoneDpc_Worker+0x38:
fffff880`05611758 4c8b4f40 mov r9,qword ptr [rdi+40h] ds:00000000`00000040=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a8c1a9 to fffff80002a8cc00
STACK_TEXT:
fffff880`030b7b98 fffff800`02a8c1a9 : 00000000`0000000a 00000000`114e2394 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`030b7ba0 fffff800`02a8ae20 : 00000000`ffffffff 00000000`00000000 00000000`00000000 fffffa80`09ac5050 : nt!KiBugCheckDispatch+0x69
fffff880`030b7ce0 fffff880`05611758 : fffffa80`09ac5050 fffffa80`09ac5ba0 fffff880`030b7ed8 fffffa80`09ac51a0 : nt!KiPageFault+0x260
fffff880`030b7e70 fffff880`05602f89 : fffffa80`09ac5050 00000000`00000000 fffffa80`09ac5b02 fffffa80`09ac5ba0 : USBPORT!USBPORT_Core_UsbDoneDpc_Worker+0x38
fffff880`030b7ed0 fffff800`02a972fc : fffff880`03088180 fffffa80`09ac5ba0 fffffa80`09ac5bb8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`030b7f00 fffff800`02a8fd05 : 00000000`00000000 fffffa80`06ec4910 00000000`00000000 fffff880`05602db0 : nt!KiRetireDpcList+0x1bc
fffff880`030b7fb0 fffff800`02a8fb1c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`092d0be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Core_UsbDoneDpc_Worker+38
fffff880`05611758 4c8b4f40 mov r9,qword ptr [rdi+40h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: USBPORT!USBPORT_Core_UsbDoneDpc_Worker+38
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a670
FAILURE_BUCKET_ID: X64_0xD1_USBPORT!USBPORT_Core_UsbDoneDpc_Worker+38
BUCKET_ID: X64_0xD1_USBPORT!USBPORT_Core_UsbDoneDpc_Worker+38
Followup: MachineOwner
---------
Safely remove and unplug any USB device connected to your system.
Norton
Norton tends to cause BSOD-s and seen it create several issues for users. Recommend uninstalling it with the Norton Removal Tool and replace with Microsoft Security Essentials. See if this stops the BSOD-s.
Download and run the Norton Removal Tool to remove the Norton Product
Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.
Microsoft Security Essentials, Free antivirus for windows and Malwarebytes Anti-Malware Free
Information
- :warn: Do not start the free trial of MalwareBytes, unselect that option when prompted.
- :tip: Update and make full scans with both separately.
System Temperature
Ensure that there are no heat issues, For monitoring heat of the system use
Speccy or
HWMonitor
Hard Drive/Storage
Post disk summary using CrystalDiskInfo software:
CrystalDiskInfo Standard Edition
- :info: For how to upload a screenshot or file, read here
Make a hard drive test from the hard drive manufacturers website:
Hard Drive Diagnostic Procedure
For errors on your Hard drive(s):
How to Run Disk Check in Windows 7
Memtest86+
Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
How to Test and Diagnose RAM Issues with Memtest86+
Note
Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.
Tip
Do this test overnight.
Then go through these links, they may help.
Thermal Paste and How To Use It | techPowerUp
Avoid Static Damage to Your PC | PCWorld
Power Supply Information and Selection - Tech Support Forum
Basic computer troubleshooting
How To Clear CMOS
How to clean your PC of dust and dirt
How to clean a computer
