BSOD Help

[BrandonPaul15]

Hey, thank you in advance for all of your help. When I originally bought the PC from Best Buy about a year ago, I was having no problems at all. About 6 months after that, I received a BSOD, occasionally - about every two weeks. Couple months after that, it started to get worse. At one point it was doing it every hour or so. Took it to CompUSA, they eventually just restored Windows with my Windows 7 Upgrade Disk. Was good for another like 2-3 months, now its back and just getting worse again. BSOD's in Safe Mode as well.

Windows 7 x64
Not the original, was originally Vista
OEM
1 Year Old
Windows 7 was reinstalled about 8 months ago.

 

[usasma]

The perfmon report cites issues with your Multimedia Video Controller and your Mouse.
The MSINFO32 report cites these issues:

Multimedia Video Controller PCI\VEN_14F1&DEV_8852&SUBSYS_D57512AB&REV_04\4&371C1E4D&0&0020 The drivers for this device are not installed.

Microsoft PS/2 Mouse ACPI\PNP0F03\4&2A700557&0 This device is not present, is not working properly, or does not have all its drivers installed.

Interestingly, the system reports that Windows was installed on 18 Feb 2010
The memory dump files in the uploaded reports date from 17 Jun 2010 and later (50 of them) - but MSINFO32 shows memory dumps from Feb, Mar, and Apr also (curiously, there's none that were reported in May).

Most likely this is a hardware issue, but it can also be due to incompatible software or hardware.
I would start with your AVG as it's cited in several of the memory dumps:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the AVG from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of AVG using this free tool: AVG - Tools download
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

I'd also uninstall Daemon Tools as a driver from that frequently can cause BSOD's. Once we're finished with the troubleshooting you can reinstall it.

Check compatibility here: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

Then, please try these free hardware diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  2 02:57:10.811 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:12.559
BugCheck C4, {f6, 290, fffffa800a62db30, fffff88003b357d9}
*** WARNING: Unable to verify timestamp for AVGIDSDriver.sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSDriver.sys
Probably caused by : AVGIDSDriver.sys ( AVGIDSDriver+167d9 )
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  avgdiagex.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  2 02:23:03.905 2010 (UTC - 4:00)
System Uptime: 0 days 4:38:16.996
BugCheck 50, {fffffb8007e24014, 1, fffff80002cd590a, 7}
Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+40e0b )
BUGCHECK_STR:  0x50
PROCESS_NAME:  ffxivboot.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Aug 24 23:44:32.196 2010 (UTC - 4:00)
System Uptime: 0 days 2:21:42.288
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 22 22:27:41.356 2010 (UTC - 4:00)
System Uptime: 0 days 1:49:08.462
BugCheck A, {fffff7ff85f05908, 2, 0, fffff80002cd2401}
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+521 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  ffxivboot.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 18 11:55:33.885 2010 (UTC - 4:00)
System Uptime: 0 days 0:43:11.976
BugCheck 50, {ffffb8a024177fa0, 0, fffff80002f79d85, 7}
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+125 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  SC2.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 18 01:01:41.218 2010 (UTC - 4:00)
System Uptime: 0 days 1:17:48.309
BugCheck A, {fffffffffffffff9, 0, 0, fffff80002ca6849}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 16 00:03:01.629 2010 (UTC - 4:00)
System Uptime: 0 days 2:52:33.260
BugCheck 3B, {c0000005, fffff80002fb612d, fffff8800a1ce240, 0}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SC2.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 13 09:52:37.621 2010 (UTC - 4:00)
System Uptime: 0 days 1:19:55.713
BugCheck A, {fffff794000003b8, 2, 0, fffff80002a11692}
Probably caused by : tcpip.sys ( tcpip!TcpUpdateMicrosecondCount+79 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Aug  6 21:43:15.699 2010 (UTC - 4:00)
System Uptime: 0 days 0:51:42.415
BugCheck 50, {ffffe20028584cc2, 1, fffff80002a497c8, 7}
Probably caused by : ntkrnlmp.exe ( nt!KiOpIsPrefix+68 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug  4 21:44:27.750 2010 (UTC - 4:00)
System Uptime: 0 days 4:31:22.841
BugCheck 50, {fffffa7fca35eb00, 0, fffff80002b03d4c, 7}
Probably caused by : hardware ( nt!KiPreprocessFault+30 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  Empire.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Aug  3 02:42:26.611 2010 (UTC - 4:00)
System Uptime: 0 days 3:06:26.702
BugCheck A, {fffff10005ec837e, 2, 1, fffff80002a8c965}
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+5 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 27 01:03:21.255 2010 (UTC - 4:00)
System Uptime: 0 days 3:05:57.971
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 7F, {8, 80050031, 6f8, fffff80002a7c6e9}
Probably caused by : ntoskrnl.exe ( nt+70600 )
BUGCHECK_STR:  0x7f_8
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 26 00:59:47.832 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:58.549
BugCheck 50, {ffffffff8b41fff6, 0, fffff80002d76a13, 5}
Probably caused by : hardware ( nt!ObReferenceObjectByHandleWithTag+1d3 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  audiodg.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 26 00:50:49.668 2010 (UTC - 4:00)
System Uptime: 0 days 9:21:58.505
BugCheck 3B, {c0000005, fffff80002ae1273, fffff88006cee0a0, 0}
Probably caused by : hardware ( dxgkrnl!COREACCESS::Release+6f )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul 25 15:26:46.164 2010 (UTC - 4:00)
System Uptime: 0 days 1:31:31.251
BugCheck 50, {fffff8807dfce0c0, 0, fffff80002ad77ea, 5}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40ecb )
BUGCHECK_STR:  0x50
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 23 21:49:20.701 2010 (UTC - 4:00)
System Uptime: 0 days 2:20:08.417
BugCheck A, {0, 2, 1, fffff80002a8ab27}
Probably caused by : ntkrnlmp.exe ( nt!KiRetireDpcList+7 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 20 02:10:35.869 2010 (UTC - 4:00)
System Uptime: 0 days 1:43:07.586
BugCheck 50, {fffff87f945fe4c4, 1, fffff8800100ef84, 5}
Probably caused by : hardware ( Ntfs!NtfsPrepareSimpleBuffers+2a4 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 20 00:26:15.903 2010 (UTC - 4:00)
System Uptime: 0 days 3:09:41.994
BugCheck 3B, {c0000005, fffff80002a9184a, fffff8800949b8b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceExclusiveLite+da )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 17 02:39:09.988 2010 (UTC - 4:00)
System Uptime: 0 days 6:39:09.080
BugCheck A, {fffff7ff8dcf3908, 2, 0, fffff80002ac0301}
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+521 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  audiodg.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 16 01:21:25.111 2010 (UTC - 4:00)
System Uptime: 0 days 1:57:35.202
BugCheck A, {ffffd3ceb8de97cd, 2, 1, fffff80002a8fe06}
*** WARNING: Unable to verify timestamp for AVGIDSFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.sys
Probably caused by : AVGIDSFilter.sys ( AVGIDSFilter+58c3 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 14 22:30:56.280 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:54.371
BugCheck A, {13aa0ea4, 2, 0, fffff80002aa1bc6}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+6c6 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  audiodg.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 20:44:20.996 2010 (UTC - 4:00)
System Uptime: 0 days 3:43:34.087
BugCheck 7F, {8, 80050031, 6f8, fffff80002aea80c}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 13 16:59:36.167 2010 (UTC - 4:00)
System Uptime: 0 days 3:03:58.258
BugCheck A, {fffffffffffffff9, 2, 0, fffff80002ac7b48}
Probably caused by : ntkrnlmp.exe ( nt!KiRetireDpcList+28 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul  9 02:24:07.330 2010 (UTC - 4:00)
System Uptime: 0 days 0:38:47.421
BugCheck 50, {fffff8803ae24109, 0, fffff80002adf4c6, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40f00 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul  9 01:44:10.829 2010 (UTC - 4:00)
System Uptime: 0 days 2:51:56.920
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
BugCheck 1000007E, {ffffffffc000001d, fffff880048e5a07, fffff88003aed478, fffff88003aecce0}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atipmdag.sys ( atipmdag+296a07 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul  8 02:17:23.793 2010 (UTC - 4:00)
System Uptime: 0 days 2:29:48.884
BugCheck 7F, {8, 80050031, 6f8, fffff80002a83590}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul  7 23:46:47.797 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:37.513
BugCheck A, {162f1, 2, 1, fffff80002ad4208}
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+428 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul  7 23:21:39.561 2010 (UTC - 4:00)
System Uptime: 0 days 2:40:43.278
BugCheck A, {5112000, 2, 1, fffff80002ad79f4}
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+94 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 22:13:19.054 2010 (UTC - 4:00)
System Uptime: 0 days 8:01:53.891
BugCheck 3B, {c000001d, fffff80002ac1852, fffff880065500b0, 0}
Probably caused by : hardware ( nt!KiCommitThreadWait+2d2 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Ventrilo.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 12:19:23.834 2010 (UTC - 4:00)
System Uptime: 0 days 0:48:17.551
BugCheck 1E, {ffffffffc000001d, fffff80002ad7047, 2, fffff80002a62000}
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+267 )
BUGCHECK_STR:  0x1E_c000001d
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul  2 22:31:06.236 2010 (UTC - 4:00)
System Uptime: 0 days 2:50:06.327
BugCheck 1E, {fffff88008d6c150, fffff88008d6c490, fffff6fc4001cb58, 0}
Probably caused by : hardware ( nt!KiDispatchException+1b9 )
BUGCHECK_STR:  0x1E_8d6c150
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 28 00:36:32.993 2010 (UTC - 4:00)
System Uptime: 0 days 0:58:56.710
BugCheck A, {ffffd3ba61322da6, 2, 0, fffff80002a83eec}
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+10c )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 23:36:44.215 2010 (UTC - 4:00)
System Uptime: 0 days 0:56:05.931
BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42be5 )
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 22:39:34.587 2010 (UTC - 4:00)
System Uptime: 0 days 10:16:54.415
BugCheck D1, {fffff7ff8deef85b, 2, 8, fffff7ff8deef85b}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  avgwdsvc.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 23 23:41:25.285 2010 (UTC - 4:00)
System Uptime: 0 days 5:50:22.001
BugCheck 1E, {0, 0, 0, 0}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ataport.SYS - 
Probably caused by : ataport.SYS ( ataport!AtaPortInitialize+1e94 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 23 17:50:13.258 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:36.350
BugCheck 50, {fffff87f8c224020, 0, fffff80002ae66ca, 5}
Probably caused by : ntkrnlmp.exe ( nt!IopAllocateIrpPrivate+6a )
BUGCHECK_STR:  0x50
PROCESS_NAME:  avgcsrva.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 22 01:34:10.891 2010 (UTC - 4:00)
System Uptime: 0 days 2:39:19.982
BugCheck 1000007E, {ffffffffc000001d, fffff80002bf2189, fffff88003c1e2f8, fffff88003c1db60}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::UnmapViewOfAllocation+78 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 21 21:11:48.622 2010 (UTC - 4:00)
System Uptime: 0 days 0:28:45.339
BugCheck 50, {fffff32015977a0d, 1, fffff880010d9705, 7}
*** WARNING: Unable to verify timestamp for AVGIDSFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.sys
Probably caused by : AVGIDSFilter.sys ( AVGIDSFilter+555b )
BUGCHECK_STR:  0x50
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 20 21:35:45.400 2010 (UTC - 4:00)
System Uptime: 0 days 0:55:03.491
BugCheck 3B, {c0000005, fffff88004da80ce, fffff8800886a810, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+5a )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 20 19:12:18.615 2010 (UTC - 4:00)
System Uptime: 0 days 0:24:02.706
BugCheck 7F, {8, 80050031, 6f8, fffff80002a8d590}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 20 13:48:40.253 2010 (UTC - 4:00)
System Uptime: 0 days 1:52:17.969
BugCheck 1E, {ffffffffc0000005, fffff80002ae1b8d, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!KiIpiProcessRequests+18d )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  Ventrilo.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 20 03:19:41.799 2010 (UTC - 4:00)
System Uptime: 0 days 2:39:03.891
BugCheck 3B, {c000001d, fffff96000179c4d, fffff880098b00a0, 0}
Probably caused by : hardware ( win32k!xxxRealInternalGetMessage+7dd )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Ventrilo.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 20 00:39:49.130 2010 (UTC - 4:00)
System Uptime: 0 days 0:32:02.714
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 19 11:57:50.361 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:56.452
BugCheck 7F, {8, 80050031, 6f8, fffff80002b0d7fd}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 19 02:15:55.276 2010 (UTC - 4:00)
System Uptime: 0 days 0:45:46.367
BugCheck 7F, {8, 80050031, 6f8, fffff80002ff25d8}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 19 01:29:15.271 2010 (UTC - 4:00)
System Uptime: 0 days 0:53:33.362
BugCheck 3B, {c0000005, fffff80002c03186, fffff88009b12090, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+d6 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 19 00:34:56.632 2010 (UTC - 4:00)
System Uptime: 0 days 0:20:00.349
BugCheck 50, {fffff960483b7cf4, 8, fffff960483b7cf4, 5}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40ecb )
BUGCHECK_STR:  0x50
PROCESS_NAME:  Ventrilo.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 18 21:19:33.077 2010 (UTC - 4:00)
System Uptime: 0 days 1:20:02.794
BugCheck 50, {ffffea00225da4f0, 0, fffff80002ae1105, 7}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+505 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 18 00:23:28.075 2010 (UTC - 4:00)
System Uptime: 0 days 1:19:44.166
BugCheck 3B, {c0000005, fffff80002bfa186, fffff880099db9a0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+d6 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  aion.bin
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 17 23:02:34.415 2010 (UTC - 4:00)
System Uptime: 0 days 2:45:54.507
BugCheck A, {2d8c7f4, f, 0, fffff80002a6fd4e}
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
Probably caused by : hardware ( dxgkrnl!DpQueueDpc+8e )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/font]

 

[BrandonPaul15]

I removed the AVG Anti-Virus, and installed the Avira free anti-virus.

- UNInstalled Daemon Tools
- Wasn't exactly sure what you wanted me to do with the compatibility check.
- Memory Test , 6 Passes 0 Errors
- HD Test , 0 Errors aswell
- Ran the ESET Malware Online Scanner, cam across only 1 Infected file - Was some file in my Java.
- Ran FurMark and it never got hotter then like 96 degrees.

 

[usasma]

I'm stumped. Try running Driver Verifier using these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[Jonathan_King]

Are you still having BSODs?

Keep in mind, removing Daemon Tools doesn't usually actually remove the offending driver. Here is a tool to actually uninstall SPTD: http://www.duplexsecure.com/download/SPTDinst-v172-x64.exe

 

[BrandonPaul15]

I used that program to completely get rid of Daemon Tools. I was BSOD bad last night. I put up verifier, and crazy enough i didn't BSOD yet. But last time i ran it, i had crashed within seconds of loading in. It seems more frequent to crash while playing games. But i have a game up, and running with verifier for about 2 hours now, and nothing. Ill report back.

 

[BrandonPaul15]

Ran verifier, came across several more BSODs. Thanks.

 

[Jonathan_King]

Ran verifier, came across several more BSODs. Thanks.

I ran the last 4 dumps, and 3 of them are blaming your ATI graphics drivers.

Try completely removing your current ones, and install these ones: https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/10-7_vista64_win7_64_dd.exe

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 19:59:26.140 2010 (UTC - 4:00)
System Uptime: 0 days 3:29:45.262
BugCheck 3B, {c0000005, fffff880046ebb23, fffff8800692b390, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+b6b23 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 16:28:42.628 2010 (UTC - 4:00)
System Uptime: 0 days 0:48:42.376
BugCheck 3B, {c0000005, fffff88001868440, fffff88007530890, 0}
Probably caused by : atikmpag.sys ( atikmpag+23440 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 15:25:18.291 2010 (UTC - 4:00)
System Uptime: 0 days 0:16:24.429
BugCheck 3B, {c0000005, fffff88003e56440, fffff88006dd2890, 0}
Probably caused by : atikmpag.sys ( atikmpag+23440 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 00:25:15.441 2010 (UTC - 4:00)
System Uptime: 0 days 0:25:21.548
BugCheck A, {ffffea0022da7564, 2, 1, fffff80002c8c109}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+f9 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  ffxivgame.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[BrandonPaul15]

I know stupid question, but , how am i going to completely remove them lol?

I want to make sure its done right.

I just Express UNIntstalled, and downloaded and INstalled the drivers from link. Will keep updated, should i run verifier again?

But posted link just takes me to AMD Website. Doesn't link the exact driver you were thinking.

 

[Jonathan_King]

Here is a tool to remove drivers, that supports ATI drivers: Guru3D - Driver Sweeper

Here is the download page for the drivers I would like you to install: ATI Catalyst™ Display Driver

Install the display driver only, found in the Option 2 section.

 

[BrandonPaul15]

Ran the Guru3D - Got rid of all the ATI Drivers. Weird enough, I found NVidia drivers in there as well, I don't know if that might be causing a problem. Im not even sure where they came from.

I downloaded the Display Driver, installed it, its not working properly. Once restarted I keep receiving a box saying that my ATI Drivers are not functional. To download the appropriate ATI Drivers.

 

[BrandonPaul15]

INstalled the driver, but a screen is still popping up saying that I need to install more correct drivers. Im not getting all my resolutions at the moment at stuff. Graphics still look like crap. But i left comp on while at work, and no BSOD , was on for about 9 hours.


Edit : Had to download Motherboard Display Drivers to make everything right. If I shouldn't have, ill get rid of them.

 

[BrandonPaul15]

So i also UNInstalled the Multimedia Device, which i have no idea what it is, and why I can not find drivers for it? But I ran games last night fine, for about 4 hours. NO BSOD at all, then when I was about to go to sleep, my computer randomly restarted. But then was no .dmp file for it. If its not one thing its another it seems.

 

[Jonathan_King]

Could you please follow the BSOD Posting Instructions sticky again?

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[BrandonPaul15]

Here.

 

[Jonathan_King]

I still see the latest ATI drivers installed. Try installing the Driver Only package from here: ATI Catalyst™ Display Driver

 

[BrandonPaul15]

It seems to just not be going away. Im getting close to just going and buying a small external HD, copying my important stuff to it. Then completely reinstalling Windows 7.

 

[Jonathan_King]

Hello,

Sorry for the delay...I just found this thread again.

The latest BSOD had a generic stack, ntkrlnmp.exe blamed, etc.

If the BSODs are still a problem, please enable driver verifier, as usasma recommended here: http://www.sevenforums.com/crashes-debugging/108992-bsod-help.html#post945854