BSOD

We need the actual .dmp file for analysis...

Blue Screen of Death (BSOD) Posting Instructions

pryskna said:

Tews said:

We need the actual .dmp file for analysis...

Blue Screen of Death (BSOD) Posting Instructions

Edit upper: its that ok?

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

pryskna said:

Tews said:

We need the actual .dmp file for analysis...

Blue Screen of Death (BSOD) Posting Instructions

Edit upper: its that ok?

Very good.

I suspect AVG is the cause. Please remove it with this tool: http://download.avg.com/filedir/util...removerx64.exe

Replace it with MSE (also free): http://www.microsoft.com/security_essentials

...Summary of the Dumps:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 30 05:45:28.602 2010 (UTC - 4:00)
System Uptime: 0 days 3:38:29.007
BugCheck 109, {a3a039d897852568, b3b7465eea01f75e, fffff8000334ec08, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
*** WARNING: Unable to verify timestamp for Unknown_Module_ed129f14`ff7c918f
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_ed129f14`ff7c918f
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 16:40:48.313 2010 (UTC - 4:00)
System Uptime: 0 days 7:19:35.827
*** WARNING: Unable to verify timestamp for Unknown_Module_ed129f14`ff7c918f
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_ed129f14`ff7c918f
BugCheck 101, {31, 0, fffff88002fd3180, 3}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 09:20:16.070 2010 (UTC - 4:00)
System Uptime: 0 days 7:01:47.475
BugCheck 3B, {c0000005, 0, fffff880076f0d90, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 28 08:04:18.595 2010 (UTC - 4:00)
System Uptime: 0 days 6:20:00.626
BugCheck 109, {a3a039d89788350f, b3b7465eea050705, fffff8000330e408, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 24 05:38:25.015 2010 (UTC - 4:00)
System Uptime: 0 days 3:11:57.420
BugCheck 3B, {c0000005, fffff80003397b4b, fffff88003d55bf0, 0}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x3B
PROCESS_NAME:  avgrsa.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 23 04:52:43.688 2010 (UTC - 4:00)
System Uptime: 0 days 2:53:23.718
BugCheck 3B, {c0000005, 0, fffff8800665b400, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

If the BSODs persist, enable driver verifier: Using Driver Verifier to identify issues with Drivers

Keep it enabled until we get new .dmp files and we'll go from there..

That is just the removal tool, it appears that AVG was successfully un-installed..