Win7 32bit repeative BSODs

Yesterday I was playing a non processor intensive game (Civilization IV) and suddenly I had a BSOD for the first time on my computer since I installed Win7. The computer automatically restarted and after it booted in normal mode, as I was in the login screen, another BSOD occured. I again restarted my computer and I managed to log in my user. Everything was seeming normal, but when I started the game again, after 10 minutes of playing, a third BSOD occured. I again restarted the computer and booted in Windows, Ilogged in my user and surfed in the internet trying to find a solution. After an hour of surfing in the internet I turned off my computer but it had 4 important updates to install. During the installation of the 1st update the system froze. I left it 2 hours with the hope that it will automatically respond again but nothing happened so I resetted the computer and I booted windows again. I was out of my house for a couple of hours and during that time my sister reported me that while she was playing a game (Age of Empires 3) another BSOD happened... What might cause that trouble? :/
______________________________
Processor; Intel Core2Duo 2.66Ghz
Motherboard; Asus P5K
Graphics Card; Nvidia GeForce 9600GSO
RAM; 2Gb
______________________________
Windows7 Installation; OEM
Windows7 Installation Age; 8 months
Age of system (hardware); 2 years

Hi Chris and welcome to the forum. Have recently installed any software or hardware? Unfortunately, due to the language barrier, I cannot read some of the reports you uploaded.

Error code A (2X), IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.

Error code 8E (2X), KERNEL_MODE_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

Code:

Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x83244000 PsLoadedModuleList = 0x8338c810
Debug session time: Wed Oct 27 06:05:44.166 2010 (GMT-4)
System Uptime: 0 days 1:55:40.633
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {2f3, 2, 1, 8328434d}

Probably caused by : bthport.sys ( bthport!RefObj_UpdateRefHistory+18 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000002f3, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8328434d, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 833ac718
Unable to read MiSystemVaType memory at 8338c160
 000002f3 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!__InterlockedIncrement+5
8328434d f00fc101        lock xadd dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  807e1850 -- (.trap 0xffffffff807e1850)
ErrCode = 00000002
eax=00000001 ebx=83210700 ecx=000002f3 edx=00000000 esi=86483e70 edi=82f7daa8
eip=8328434d esp=807e18c4 ebp=807e18cc iopl=0         nv up ei pl nz ac pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010216
nt!__InterlockedIncrement+0x5:
8328434d f00fc101        lock xadd dword ptr [ecx],eax ds:0023:000002f3=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8328434d to 8328a82b

STACK_TEXT:  
807e1850 8328434d badb0d00 00000000 50485442 nt!KiTrap0E+0x2cf
807e18c0 82f78db6 86483e70 807e18f4 82f78fca nt!__InterlockedIncrement+0x5
807e18cc 82f78fca 86483e70 00000087 82f7c13a bthport!RefObj_UpdateRefHistory+0x18
807e18f4 82f4563d 86483e70 86483e58 00000087 bthport!RefObj_ReleaseEx+0x28
807e1918 82f456be 864cab68 864b60f4 88241008 bthport!HCI_CompleteAclRdHciPkt+0x59
807e1930 82f6858e 864caad8 00000000 88241008 bthport!HCI_CompleteAclRdChain+0x52
807e1954 82f79077 02241008 88241014 807e19c8 bthport!L2CapCon_Destroy+0x84
807e196c 82f4e501 00000000 82f5178c 00000b15 bthport!RefObj_ReleaseEx+0xd5
807e198c 82f51aff 8801d228 807e19c8 c000009d bthport!HCI_CxnDrainMoveList+0x41
807e19f0 82f51bc1 880dc008 0201d228 0dc40208 bthport!HCI_HandleDisconnectionComplete+0x373
807e1a14 82f4969a 880dc008 00000000 88165ac8 bthport!Fn_EVENT_DisconnectionComplete+0x39
807e1a6c 82f57d9e 880dc008 00000000 88165ac8 bthport!HCI_DoCmdCompletion+0x2a2
807e1a94 82f607c0 880dc008 88165ac8 83210700 bthport!HCI_ProcessAsynchronousEvent+0x70
807e1ab8 82f60d29 880dc008 85923008 880e26e0 bthport!HCI_ProcessEventAtDPC+0xfc
807e1adc 82f3f122 020dc008 85923008 00000006 bthport!HCI_ProcessMpBip+0xe5
807e1af0 82f2c5d9 85923008 832107a0 880f9350 bthport!BTHPORT_RecvMpBip+0x38
807e1b0c 82f31910 880e26e0 88165ac8 00000006 BTHUSB!BthUsb_EventTransferComplete+0x87
807e1b64 82f31d13 880e2b08 807e1b80 880dcdcf BTHUSB!UsbWrapWorkRoutine+0xce
807e1b8c 832acb33 880e2b08 880dcca8 01000003 BTHUSB!UsbWrapInterruptReadComplete+0x11d
807e1bd0 90db0868 83284354 889de178 00000000 nt!IopfCompleteRequest+0x128
807e1c00 90db1178 851a8710 880dcca8 880f9280 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
807e1c2c 90db49af 86c10028 86c100f0 86c10a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
807e1c54 90daed18 86c10028 86c10a98 86c10002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
807e1c78 832ac3b5 86c10aa4 86c10002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e1cd4 832ac218 807c5120 807ca800 00000000 nt!KiExecuteAllDpcs+0xf9
807e1d20 832ac038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
807e1d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
bthport!RefObj_UpdateRefHistory+18
82f78db6 48              dec     eax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  bthport!RefObj_UpdateRefHistory+18

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bthport

IMAGE_NAME:  bthport.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc882

FAILURE_BUCKET_ID:  0xA_bthport!RefObj_UpdateRefHistory+18

BUCKET_ID:  0xA_bthport!RefObj_UpdateRefHistory+18

Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 83287897, 8b127b38, 8b127710}

Probably caused by : afd.sys ( afd!AfdFreeConnectionResources+45 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 83287897, The address that the exception occurred at
Arg3: 8b127b38, Exception Record Address
Arg4: 8b127710, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!PspReturnQuota+25
83287897 8b3e            mov     edi,dword ptr [esi]

EXCEPTION_RECORD:  8b127b38 -- (.exr 0xffffffff8b127b38)
ExceptionAddress: 83287897 (nt!PspReturnQuota+0x00000025)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000100
Attempt to read from address 00000100

CONTEXT:  8b127710 -- (.cxr 0xffffffff8b127710)
eax=00000080 ebx=00000400 ecx=00000001 edx=00001edf esi=00000100 edi=00000080
eip=83287897 esp=8b127c00 ebp=8b127c1c iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!PspReturnQuota+0x25:
83287897 8b3e            mov     edi,dword ptr [esi]  ds:0023:00000100=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000100

READ_ADDRESS: GetPointerFromAddress: unable to read from 8337e718
Unable to read MiSystemVaType memory at 8335e160
 00000100 

FOLLOWUP_IP: 
afd!AfdFreeConnectionResources+45
8e8a97a2 83660c00        and     dword ptr [esi+0Ch],0

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 83437a36 to 83287897

STACK_TEXT:  
8b127c1c 83437a36 00000080 00000000 00000001 nt!PspReturnQuota+0x25
8b127c3c 834379ac 00000400 000000f8 850d4040 nt!PsReturnSharedPoolQuota+0x21
8b127c68 8343778d 885850f8 885850e0 00000000 nt!ObpFreeObject+0x213
8b127c7c 8327ef60 00000000 00020000 88585180 nt!ObpRemoveObjectRoutine+0x5e
8b127c90 8327eed0 885850f8 8e8a97a2 88585180 nt!ObfDereferenceObjectWithTag+0x88
8b127c98 8e8a97a2 88585180 8e897ea8 8e89f3e9 nt!ObfDereferenceObject+0xd
8b127cac 8e889795 88585180 885851f8 8e897ea8 afd!AfdFreeConnectionResources+0x45
8b127cc4 8e89e75c 88585180 8b127cec 8e88929e afd!AfdFreeConnectionEx+0xd6
8b127cd0 8e88929e 885851f8 865100d8 8649ef08 afd!AfdFreeConnection+0x1d
8b127cec 83436815 8649ef08 00000000 850d6798 afd!AfdDoWork+0x51
8b127d00 83283f3b 865100d8 00000000 850d6798 nt!IopProcessWorkItem+0x23
8b127d50 834246d3 00000001 a374a225 00000000 nt!ExpWorkerThread+0x10d
8b127d90 832d60f9 83283e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  afd!AfdFreeConnectionResources+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf62

STACK_COMMAND:  .cxr 0xffffffff8b127710 ; kb

FAILURE_BUCKET_ID:  0x7E_afd!AfdFreeConnectionResources+45

BUCKET_ID:  0x7E_afd!AfdFreeConnectionResources+45

Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 81f93174, a61c7670, 0}

*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+158174 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81f93174, The address that the exception occurred at
Arg3: a61c7670, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nvlddmkm+158174
81f93174 3b480c          cmp     ecx,dword ptr [eax+0Ch]

TRAP_FRAME:  a61c7670 -- (.trap 0xffffffffa61c7670)
ErrCode = 00000000
eax=6a0e75f9 ebx=8651ad30 ecx=108550b6 edx=18000000 esi=00000000 edi=00000000
eip=81f93174 esp=a61c76e4 ebp=a61c76e4 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nvlddmkm+0x158174:
81f93174 3b480c          cmp     ecx,dword ptr [eax+0Ch] ds:0023:6a0e7605=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  Civ4BeyondSwor

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8235e2dc to 81f93174

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
a61c76e4 8235e2dc 18000000 108550b6 a61c770c nvlddmkm+0x158174
a61c76fc 82363758 4c44444d 18000000 108550b6 nvlddmkm+0x5232dc
a61c7724 81f6343d 850e4008 8651ad30 008338b1 nvlddmkm+0x528758
a61c782c 81f65f2a 8651ad30 00000000 00000000 nvlddmkm+0x12843d
a61c78b4 81ef5f0a 00000000 85474008 a61c78f4 nvlddmkm+0x12af2a
a61c78d0 81ef7172 a61c78f4 85474008 85474008 nvlddmkm+0xbaf0a
a61c78e4 81e85626 a61c78f4 85185260 c1d00781 nvlddmkm+0xbc172
a61c798c 81e87646 caf003e5 00000000 854c6a08 nvlddmkm+0x4a626
a61c79ac 81e62df6 85185260 00000000 00000000 nvlddmkm+0x4c646
a61c79fc 823a6574 a61c7a9c 832236ee a61c7a9c nvlddmkm+0x27df6
a61c7a18 828e0779 85474008 823a654c a963d208 nvlddmkm+0x56b574
a61c7a44 828df514 85474008 a61c7a9c a963dc40 dxgkrnl+0x25779
a61c7abc 828dd481 00000000 00000000 9719f8f8 dxgkrnl+0x24514
a61c7ae4 828df95e 00000001 00000000 00000000 dxgkrnl+0x22481
a61c7b08 828dfd6e 00000000 00000000 ad68b388 dxgkrnl+0x2495e
a61c7b64 828e0594 a61c7b98 00000001 24912973 dxgkrnl+0x24d6e
a61c7d28 8329844a 0ef4fee0 0ef4fef0 776564f4 dxgkrnl+0x25594
a61c7d28 776564f4 0ef4fee0 0ef4fef0 776564f4 nt!KiFastCallEntry+0x12a
0ef4fef0 00000000 00000000 00000000 00000000 0x776564f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+158174
81f93174 3b480c          cmp     ecx,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+158174

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c379162

FAILURE_BUCKET_ID:  0x8E_nvlddmkm+158174

BUCKET_ID:  0x8E_nvlddmkm+158174

Followup: MachineOwner
---------

All of the dumps point to hardware or hardware related errors. Mos of them blame Windoes system drivers (very likely not the real cause) and one blames nvlddmkm.sys, an Nvidia video driver.

I do find an almost guaranteed BSOD maker on your system:

ASACPI.sys Wed Oct 18 01:44:46 2006.
The 2006 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.

Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2006).

I also find some outdated drivers loaded on your system. Outdated drivers can and do cause memory corruption and BSOD's. The first two drivers on the list were shown in one of your dumps as being part of the crash. Update the following drivers.

LHidFilt.Sys Wed Jun 17 12:49:04 2009 - Logitech SetPoint HID Filter Driver Downloads

LMouFilt.Sys Wed Jun 17 12:49:08 2009 - Logitech Mouse Filter driverDownloads

RTKVHDA.sys Fri May 22 14:03:37 2009 - Realtek HD Audio Codec Driver Realtek

How to find drivers -

- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
- - To remove any left over driver remnants, especially from graphics cards, use driver sweeper Guru3D - Driver Sweeper

Update ASACPI.sys and the other three drivers, reboot your system and see how it does. If you get another BSOD, upload it to us and we will go from there. Please let us know how your system is doing.

Very good job on following the suggestions.

Does the fact it happened during gameplay indicates that it is a graphics card issue?

Not necessarily. Games stress the system more than, say, a word processing program or browsing the internet. When the system is stressed, faults will show up. If I had to bet, I would put my money on ASACPI.sys being the cause or at least one of the causes. There could be another problem lurking about. Troubleshooting these kinds of issues is a process of elimination until the problem is solved. That process begins with taking care of all known potential causes of crashes - which you have done. The video card is a possibility as is memory. We will just have to take it step by step. I hope what you have done will solve the problem. That would be simple and nice. :)

You are welcome for the help.

There is not an easy way to generate the reports in English. I can use Google translator when I need something. It is a little cumbersome; but no big deal.

Yes, please upload the dumps. You can use the instructions and upload just the dumps now since there are no changes to your systems: https://www.sevenforums.com/tutorials...en-forums.html. Once we get these we decide on the next steps.

You can run Memtest in the meantime to test your memory. Memtest is more thorough than the built in Windows memory test. It stresses the RAM more. It needs to run for at least 7 passes and this will take 6-8 hours. Errors, if any, will show on your screen in red. If you see errors, you can stop the test. Follow the instructions in this tutorial and post your results. RAM - Test with Memtest86+

I uploaded the updated minidumps and I hope that you will get something from them. I am going to run memtest86 but I have a question, does it automatically restart when it finishes or does it stay open so that you will be able to see the errors? I ask this question because it is night here in Greece and I can't wait so many hours so I am planning to leave it the whole night doing its work and when I will get up in the morning, see the results.

I apologize for missing your post back.

Error code 19, BAD_POOL_HEADER. Usual causes: Device driver

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8323a000 PsLoadedModuleList = 0x83382810
Debug session time: Sat Oct 30 10:54:21.463 2010 (GMT-4)
System Uptime: 0 days 3:17:00.008
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
..............
0: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 88532910, 88532938, 8050001}

GetPointerFromAddress: unable to read from 833a2718
Unable to read MiSystemVaType memory at 83382160
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+1b1 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 88532910, The pool entry we were looking for within the page.
Arg3: 88532938, The next pool entry.
Arg4: 08050001, (reserved)

Debugging Details:
------------------

GetPointerFromAddress: unable to read from 833a2718
Unable to read MiSystemVaType memory at 83382160

BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from 833a2718
Unable to read MiSystemVaType memory at 83382160
 88532910 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  age3.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 832edfc6 to 833591b6

STACK_TEXT:  
a0547c84 832edfc6 88532918 00000000 85777619 nt!ExFreePoolWithTag+0x1b1
a0547d1c 8327d44a ffffffff 0012fc30 0012fc34 nt!NtFreeVirtualMemory+0x78e
a0547d1c 77ae64f4 ffffffff 0012fc30 0012fc34 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fc24 00000000 00000000 00000000 00000000 0x77ae64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExFreePoolWithTag+1b1
833591b6 cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExFreePoolWithTag+1b1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

FAILURE_BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+1b1

BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+1b1

Followup: MachineOwner
---------

0: kd> lmtsmn
start    end        module name
88e9e000 88ee6000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8dcf0000 8dd4a000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
8eed1000 8eee3000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
88ff2000 88ffb000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8eeb8000 8eeb96c0   ASACPI   ASACPI.sys   Wed May 13 07:11:32 2009 (4A0AAAE4)
8a9fc000 8a9feb00   aswFsBlk aswFsBlk.SYS Tue Sep 07 10:47:05 2010 (4C865069)
96489000 964c0000   aswMonFlt aswMonFlt.sys Tue Sep 07 10:47:28 2010 (4C865080)
8dd4a000 8dd4e100   aswRdr   aswRdr.SYS   Tue Sep 07 10:47:44 2010 (4C865090)
8eca3000 8ecc9c80   aswSP    aswSP.SYS    Tue Sep 07 10:52:01 2010 (4C865191)
8dcb4000 8dcbdc00   aswTdi   aswTdi.SYS   Tue Sep 07 10:52:23 2010 (4C8651A7)
a98f5000 a98fe000   asyncmac asyncmac.sys Mon Jul 13 19:54:46 2009 (4A5BC946)
88fae000 88fb7000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
88fb7000 88fda000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
893ef000 893f6000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
8ec95000 8eca3000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
88cc0000 88cc8000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
96582000 9659b000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
9e10b000 9e118000   BthEnum  BthEnum.sys  Mon Jul 13 19:51:35 2009 (4A5BC887)
9e133000 9e145000   bthmodem bthmodem.sys Mon Jul 13 19:51:34 2009 (4A5BC886)
9e118000 9e133000   bthpan   bthpan.sys   Mon Jul 13 19:51:43 2009 (4A5BC88F)
9e083000 9e0e7000   bthport  bthport.sys  Mon Jul 13 19:51:30 2009 (4A5BC882)
9e071000 9e083000   BTHUSB   BTHUSB.sys   Mon Jul 13 19:51:36 2009 (4A5BC888)
97f90000 97fae000   cdd      cdd.dll      Mon Jul 13 21:04:18 2009 (4A5BD992)
a997c000 a9992000   cdfs     cdfs.sys     Mon Jul 13 19:11:14 2009 (4A5BBF12)
88c00000 88c1f000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
88d0a000 88db5000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8939b000 893c0000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
88cc8000 88d0a000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8916e000 891cb000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
8eec4000 8eed1000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
96d94000 96da1000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8ec7d000 8ec95000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
8ec71000 8ec7d000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
8938a000 8939b000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
96c8d000 96ca6000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
96da1000 96dac000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
96db6000 96dc7000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
96dac000 96db6000   dump_msahci dump_msahci.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
96ca6000 96cb0000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
8ed01000 8edb8000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 20:48:33 2009 (4AC54DE1)
8edb8000 8edf1000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
88e00000 88e11000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
88db5000 88de9000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
891d9000 891e2000   Fs_Rec   Fs_Rec.sys   unavailable (00000000)
89358000 8938a000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
89564000 89595000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
83203000 8323a000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
8ee89000 8eea8000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
9e152000 9e16d000   hidbth   hidbth.sys   Mon Jul 13 19:51:33 2009 (4A5BC885)
96cc8000 96cdb000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865)
96cdb000 96ce1480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863)
96cbd000 96cc8000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868)
964fd000 96582000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
89410000 89418000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
8ecef000 8ed01000   intelppm intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07)
8ef85000 8ef92000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
96cea000 96cf6000   kbdhid   kbdhid.sys   Mon Jul 13 19:45:09 2009 (4A5BC705)
80bc9000 80bd1000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
8efbb000 8efef000   ks       ks.sys       Wed Mar 03 22:57:52 2010 (4B8F2FC0)
8915b000 8916e000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
89306000 8932b000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
8eea8000 8eeb8000   L1E62x86 L1E62x86.sys Sun Aug 23 01:06:36 2009 (4A90CE5C)
96ce2000 96ce9080   LHidFilt LHidFilt.Sys Wed Jun 17 12:49:04 2009 (4A391E80)
96deb000 96dfb000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
96d4c000 96d53800   LMouFilt LMouFilt.Sys Wed Jun 17 12:49:08 2009 (4A391E84)
96dc7000 96de2000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
88c37000 88caf000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
9e145000 9e152000   modem    modem.sys    Mon Jul 13 19:55:24 2009 (4A5BC96C)
96cf6000 96d01000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
8ef92000 8ef9f000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
96d41000 96d4c000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
88f98000 88fae000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
9659b000 965ad000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
965ad000 965d0000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
9e003000 9e03e000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
9e03e000 9e059000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
88fda000 88fe4000   msahci   msahci.sys   Mon Jul 13 19:45:50 2009 (4A5BC72E)
8dc79000 8dc84000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
88eef000 88ef7000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
89130000 8915b000   msrpc    msrpc.sys    unavailable (00000000)
8ec67000 8ec71000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
89400000 89410000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
89211000 892c8000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
8eefb000 8ef06000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
8ef06000 8ef28000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
96478000 96489000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
8dd75000 8dd83000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
8dcbe000 8dcf0000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
892c8000 89306000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
9e16d000 9e173f00   npf      npf.sys      Fri Jun 25 12:47:37 2010 (4C24DDA9)
8dc84000 8dc92000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
8ec5d000 8ec67000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
8323a000 8364a000   nt       ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC)
89001000 89130000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
893e8000 893ef000   Null     Null.SYS     unavailable (00000000)
8fdc6000 8fdc7040   nvBridge nvBridge.kmd Sat Oct 16 13:04:23 2010 (4CB9DB17)
8f429000 8fdc55a0   nvlddmkm nvlddmkm.sys Sat Oct 16 13:07:56 2010 (4CB9DBEC)
8dd56000 8dd75000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
88f2c000 88f3d000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
88ef7000 88f21000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
88fe4000 88ff2000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
891cb000 891d9000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
a7e3d000 a7ed4000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
96c5e000 96c8d000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
88caf000 88cc0000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
8eee3000 8eefb000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
8ef28000 8ef40000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
8ef40000 8ef57000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
8ef57000 8ef6e000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
8ec1c000 8ec5d000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
8dc61000 8dc69000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
8eceb000 8eceec80   rdpdispm rdpdispm.sys Thu Aug 19 18:04:18 2010 (4C6DAA62)
8dc69000 8dc71000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
8dc71000 8dc79000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
8932b000 89358000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
9e0e7000 9e10b000   rfcomm   rfcomm.sys   Mon Jul 13 19:51:41 2009 (4A5BC88D)
964c0000 964d3000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
96a1e000 96c5d040   RTKVHDA  RTKVHDA.sys  Fri May 22 14:03:37 2009 (4A16E8F9)
895dc000 895f4000   sbp2port sbp2port.sys Mon Jul 13 19:11:28 2009 (4A5BBF20)
a7ed4000 a7ede000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
8eeba000 8eec4000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717)
8dd83000 8dd9d000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
a7ede000 a7f6a000   Sftfslh  Sftfslh.sys  Fri Apr 23 14:18:40 2010 (4BD1E480)
a7f6a000 a7fa0000   Sftplaylh Sftplaylh.sys Fri Apr 23 14:19:38 2010 (4BD1E4BA)
a9882000 a988b000   Sftredirlh Sftredirlh.sys Fri Apr 23 14:19:31 2010 (4BD1E4B3)
96de2000 96deb000   Sftvollh Sftvollh.sys Fri Apr 23 14:18:31 2010 (4BD1E477)
895d4000 895dc000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
a9831000 a9882000   srv      srv.sys      Thu Aug 26 23:31:26 2010 (4C77318E)
9e174000 9e1c3000   srv2     srv2.sys     Thu Aug 26 23:30:45 2010 (4C773165)
a7fa0000 a7fc1000   srvnet   srvnet.sys   Thu Aug 26 23:30:39 2010 (4C77315F)
96d18000 96d25180   STREAM   STREAM.SYS   Mon Jul 13 19:50:57 2009 (4A5BC861)
8efb9000 8efba380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8941b000 89564000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
a7fc1000 a7fce000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
8dca9000 8dcb4000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
8dc92000 8dca9000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
8dddb000 8ddeb000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
97f20000 97f29000   TSDDD    TSDDD.dll    unavailable (00000000)
8ecca000 8eceb000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
96d54000 96d94000   udfs     udfs.sys     Mon Jul 13 19:14:09 2009 (4A5BBFC1)
8efef000 8effd000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
96d2d000 96d40b00   usbaudio usbaudio.sys Mon Jul 13 19:51:23 2009 (4A5BC87B)
96d01000 96d18000   usbccgp  usbccgp.sys  Mon Jul 13 19:51:31 2009 (4A5BC883)
96cbb000 96cbc700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
8ee7a000 8ee89000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
96434000 96478000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
8ee2f000 8ee7a000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
96cb0000 96cbb000   usbprint usbprint.sys Mon Jul 13 20:17:06 2009 (4A5BCE82)
8fdc8000 8fdd3000   usbuhci  usbuhci.sys  Mon Jul 13 19:51:10 2009 (4A5BC86E)
8ddb9000 8ddda540   VBoxDrv  VBoxDrv.sys  Thu Aug 05 08:07:59 2010 (4C5AA99F)
8ef6e000 8ef84e80   VBoxNetAdp VBoxNetAdp.sys Thu Aug 05 08:08:00 2010 (4C5AA9A0)
8ef9f000 8efb88c0   VBoxNetFlt VBoxNetFlt.sys Thu Aug 05 08:07:59 2010 (4C5AA99F)
8ddb0000 8ddb89c0   VBoxUSBMon VBoxUSBMon.sys Thu Aug 05 08:08:00 2010 (4C5AA9A0)
88f21000 88f2c000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
89200000 8920c000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
8dc33000 8dc54000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
88f3d000 88f4d000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
88f4d000 88f98000   volmgrx  volmgrx.sys  unavailable (00000000)
89595000 895d4000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8a803000 8a9fc000   VX6000Xp VX6000Xp.sys Tue Oct 06 22:09:09 2009 (4ACBF845)
96d26000 96d2c880   VX6KCamd VX6KCamd.sys Tue Oct 06 21:52:35 2009 (4ACBF463)
8dd9d000 8ddb0000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
8dc54000 8dc61000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
88e1f000 88e90000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
88e90000 88e9e000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8dd4f000 8dd56000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
97cc0000 97f0b000   win32k   win32k.sys   Tue Aug 31 22:34:29 2010 (4C7DBBB5)
88ee6000 88eef000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
96a00000 96a1a000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)

Unloaded modules:
a995b000 a997c000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a9952000 a995b000   WinUsb.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a9931000 a9952000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a9928000 a9931000   WinUsb.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a9907000 a9928000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a98fe000 a9907000   WinUsb.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
964dc000 964fd000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
964d3000 964dc000   WinUsb.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a988b000 a98f5000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
9e059000 9e071000   parport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
893c0000 893cd000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
895f4000 895ff000   dump_pciidex
    Timestamp: unavailable (00000000)
    Checksum:  00000000
893cd000 893d7000   dump_msahci.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
893d7000 893e8000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

I see you have updated drivers. Good job. But I find the following out of date drivers loading on your system. Older drivers can and do cause conflicts, memory corruption and BSOD's. Update these drivers.

LHidFilt.Sys Wed Jun 17 12:49:04 2009 - Logitech SetPoint HID Filter Driver Downloads

LMouFilt.Sys Wed Jun 17 12:49:08 2009 - Logitech SetPoint HID Filter Driver Downloads. This is possibly a mouse driver.

RTKVHDA.sys Fri May 22 14:03:37 2009 - Realtek HD Audio Codec Driver Realtek

Update these drivers. If you get another BSOD, uninstall Avast. Avast generally works well with Win 7; but it has been known to cause BSOD's on some Win 7 systems. Upload any new BSOD's to us.

Again thank you for your response! :) Well, you suggested me updating those two drivers at your first response and I did so, but from your post I realise that those drivers were not installed whatsoever... Maybe that installation was only for the application companion of those pieces of hardware... So I am going to update my sound card's driver (Realtek) and I am gonna see if there is still a problem and I will inform you Thanks for your assistance!

You are welcome, Chris. Let us know. We may need to do some hardware testing.