computer name: HUGO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8570167296 total
VM: 2147352576, free: 1908830208



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 30/03/2012 19:49:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033012-12370-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x109 (0xA3A039D8A15F581F, 0xB3B7465EF3DD27CD, 0xFFFFF80003014520, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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 30/03/2012 19:49:50 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x109 (0xA3A039D8A15F581F, 0xB3B7465EF3DD27CD, 0xFFFFF80003014520, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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 Thu 29/03/2012 12:03:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032912-14757-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x109 (0xA3A039D8A016C9C7, 0xB3B7465EF293992D, 0xFFFFF8000309C660, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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 Thu 29/03/2012 03:28:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032912-12339-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x31A6B6) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800033246B6, 0xFFFFF88003DAF7F8, 0xFFFFF88003DAF050)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Thu 29/03/2012 01:57:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032912-13852-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xAA590) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000002, 0xFFFFF80003106590, 0xFFFFF880049CC490, 0xFFFFF880049CC530)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Thu 29/03/2012 00:37:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032912-11871-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030D86B3, 0xFFFFF8800BBADE50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.