Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\061011-11980-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:  
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82e3d000 PsLoadedModuleList = 0x82f87850
Debug session time: Fri Jun 10 10:53:07.648 2011 (UTC + 2:00)
System Uptime: 0 days 1:55:32.584
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041790, The subtype of the bugcheck.
Arg2: c08020fe
Arg3: 0000ffff
Arg4: 00000000
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0x1a_41790
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
PROCESS_NAME:  chrome.exe
 
CURRENT_IRQL:  0
 
LAST_CONTROL_TRANSFER:  from 82edd2f4 to 82edcd22
 
STACK_TEXT:  
a6a5fab8 82edd2f4 0b5e0002 0bbc9fff 859ada58 nt!MiDeleteVirtualAddresses+0x41a
a6a5fb88 82edcfa9 859ada58 87a8a670 85d2a3a0 nt!MiRemoveMappedView+0x325
a6a5fbb0 83085299 85d2a3a0 00000000 a6a5fc44 nt!MiRemoveVadAndView+0xe5
a6a5fc14 830a368f 859ada58 0b5e0000 00000000 nt!MiUnmapViewOfSection+0x265
a6a5fc34 82e7b1ea ffffffff 0b5e0000 a6a5fd08 nt!NtUnmapViewOfSection+0x55
a6a5fc34 82e7a579 ffffffff 0b5e0000 a6a5fd08 nt!KiFastCallEntry+0x12a
a6a5fcb4 9b4bc2b0 ffffffff 0b5e0000 3dc58c98 nt!ZwUnmapViewOfSection+0x11
a6a5fd08 82e7b1ea 73011d42 000002d0 0b5e0000 win32k!NtGdiCreateDIBSection+0x227
a6a5fd08 77c270b4 73011d42 000002d0 0b5e0000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
003ef3b0 00000000 00000000 00000000 00000000 0x77c270b4
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP:  
win32k!NtGdiCreateDIBSection+227
9b4bc2b0 ff75e4          push    dword ptr [ebp-1Ch]
 
SYMBOL_STACK_INDEX:  7
 
SYMBOL_NAME:  win32k!NtGdiCreateDIBSection+227
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: win32k
 
IMAGE_NAME:  win32k.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7900f
 
FAILURE_BUCKET_ID:  0x1a_41790_win32k!NtGdiCreateDIBSection+227
 
BUCKET_ID:  0x1a_41790_win32k!NtGdiCreateDIBSection+227
 
Followup: MachineOwner
---------

.............
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041790, The subtype of the bugcheck.
Arg2: c0802074
Arg3: 0000ffff
Arg4: 00000000
 
Debugging Details:
------------------
 
 
BUGCHECK_STR:  0x1a_41790
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
PROCESS_NAME:  LWEMon.exe
 
CURRENT_IRQL:  0
 
LAST_CONTROL_TRANSFER:  from 82ea32f4 to 82ea2d22
 
STACK_TEXT:  
ab08bba8 82ea32f4 02cb0002 030bffff 87ef39b0 nt!MiDeleteVirtualAddresses+0x41a
ab08bc78 82ea2fa9 87ef39b0 871160e0 87ef4620 nt!MiRemoveMappedView+0x325
ab08bca0 8304b299 87ef4620 00000000 ffffffff nt!MiRemoveVadAndView+0xe5
ab08bd04 8306968f 87ef39b0 02cb0000 00000000 nt!MiUnmapViewOfSection+0x265
ab08bd24 82e411ea ffffffff 02cb0000 0012f764 nt!NtUnmapViewOfSection+0x55
ab08bd24 771c70b4 ffffffff 02cb0000 0012f764 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f764 00000000 00000000 00000000 00000000 0x771c70b4
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP:  
nt!MiDeleteVirtualAddresses+41a
82ea2d22 cc              int     3
 
SYMBOL_STACK_INDEX:  0
 
SYMBOL_NAME:  nt!MiDeleteVirtualAddresses+41a
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78a09
 
IMAGE_NAME:  memory_corruption
 
FAILURE_BUCKET_ID:  0x1a_41790_nt!MiDeleteVirtualAddresses+41a
 
BUCKET_ID:  0x1a_41790_nt!MiDeleteVirtualAddresses+41a
 
Followup: MachineOwner
---------

On Fri 10/06/2011 16:08:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061011-11887-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9FD22)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC0802074, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Fri 10/06/2011 16:08:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!ExFreeToPagedLookasideList+0x4B8)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC0802074, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .  
Google query: ntkrpamp.exe MEMORY_MANAGEMENT

On Fri 10/06/2011 08:53:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061011-11980-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9FD22)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC08020FE, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Tue 07/06/2011 07:56:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-11247-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9FD22)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC08020CE, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.