Many of your chipset and OEM drivers haven't been updated and appear to be date around 2010 - you need to methodically update all your chipset and device drivers.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {ffffffff8948104a, 2, 0, fffff880040a5ede}
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : hardware ( usbfilter+1bf5 )
Followup: MachineOwner
---------
2: kd> lmvm usbfilter
start end module name
fffff880`06fe3000 fffff880`06ff2000 usbfilter T (no symbols)
Loaded symbol image file: usbfilter.sys
Image path: \SystemRoot\system32\DRIVERS\usbfilter.sys
Image name: usbfilter.sys
Timestamp: Wed Dec 15 21:04:49 2010 (4D0899C9)
CheckSum: 00015056
ImageSize: 0000F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update the AMD USB filter drivers - see link below:
Driver Reference Table
Code:
fffff880`0b707148 00000000`4944494f
fffff880`0b707150 fffffa80`0923e100
fffff880`0b707158 fffff880`00e155f7Unable to load image \SystemRoot\system32\DRIVERS\AiChargerPlus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AiChargerPlus.sys
*** ERROR: Module load completed but symbols could not be loaded for AiChargerPlus.sys
AiChargerPlus+0x5f7
fffff880`0b707160 fffffa80`08b73450
fffff880`0b707168 fffffa80`07103010
.
.
fffff880`00e15000 fffff880`00e16e00 AiChargerPlus T (no symbols)
Loaded symbol image file: AiChargerPlus.sys
Image path: \SystemRoot\system32\DRIVERS\AiChargerPlus.sys
Image name: AiChargerPlus.sys
Timestamp: Mon Nov 08 17:18:26 2010 (4CD79D3A)
CheckSum: 00005A96
ImageSize: 00001E00
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Uninstall the ASUS Charger utility....early versions were a well-known cause of BSOD's.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffff8b491773, 1, fffff880012ab832, 5}
Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCreate+210b )
Followup: MachineOwner
---------
Check your hard disk for mechanical errors by running the LONG test using the DOS version of SeaTools:
SeaTools for DOS and Windows - How to Use
Recommendations:
1. Uninstall that AVG crap if you haven't already - all they produce now is bloated rubbish that stuff's systems up. They have't produced anything good in the last 5 years.
2. Replace MaCrappy with MSE - MSE never BSOD's, and having MaCrappy installed is worse than having a virus
3. Uninstall Daemon Tools Lite - its a well known cause of BSOD's