Results 1 to 1 of 1
Thread: Crash Dump ! !
Hybrid View
-
15th January 2013 11:04 #1
Crash Dump ! !
whocrashed:
System Information (local)
--------------------------------------------------------------------------------
computer name:
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3220488192 total
VM: 2147352576, free: 1977204736
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 15.1.2013 / 08:45:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011513-15625-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCC17E)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF91BFA318, 0xBFA318, 0xFFFFFFFF91BFA318)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 15.1.2013 / 08:45:19 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngUnlockSurface+0x257F)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF91BFA318, 0xBFA318, 0xFFFFFFFF91BFA318)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
p.s. . !!




Reply With Quote
windwos 10
5th May 2023, 00:01 in Windows