Hello, I am having a lot of problems with my pc crashing all the time, I thought that upgrading to Windows 8 will help but it is still crashing, also my web browsers crash all the time. I dont know what the problem is, so i am hoping this comunnity can help me.
WHOCRASHED LOGS:
System Information (local)
--------------------------------------------------------------------------------
computer name: VILIUSI7
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17156706304 total
VM: 2147352576, free: 1921753088
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 2013-01-11 20:43:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011113-30796-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960000F8FF9)
Bugcheck code: 0x50 (0xFFFFF96000BC98A0, 0x0, 0xFFFFF960000F8FF9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 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 Fri 2013-01-11 20:43:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngAcquireSemaphore+0x3899)
Bugcheck code: 0x50 (0xFFFFF96000BC98A0, 0x0, 0xFFFFF960000F8FF9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 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 Fri 2013-01-11 18:22:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011113-39250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803F4083D35, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 that cannot be identified at this time.
On Fri 2013-01-11 17:02:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011113-46875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340)
Bugcheck code: 0x1A (0x41793, 0xFFFFF680000A5F10, 0x1F, 0x1E)
Error: MEMORY_MANAGEMENT
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 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 that cannot be identified at this time.
On Thu 2013-01-10 14:05:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011013-49625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340)
Bugcheck code: 0xA (0xFFFFFA001128A340, 0x2, 0x0, 0xFFFFF800D86F2ACC)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.
WHOCRASHED LOGS:
System Information (local)
--------------------------------------------------------------------------------
computer name: VILIUSI7
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17156706304 total
VM: 2147352576, free: 1921753088
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 2013-01-11 20:43:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011113-30796-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960000F8FF9)
Bugcheck code: 0x50 (0xFFFFF96000BC98A0, 0x0, 0xFFFFF960000F8FF9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 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 Fri 2013-01-11 20:43:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngAcquireSemaphore+0x3899)
Bugcheck code: 0x50 (0xFFFFF96000BC98A0, 0x0, 0xFFFFF960000F8FF9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 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 Fri 2013-01-11 18:22:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011113-39250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803F4083D35, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 that cannot be identified at this time.
On Fri 2013-01-11 17:02:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011113-46875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340)
Bugcheck code: 0x1A (0x41793, 0xFFFFF680000A5F10, 0x1F, 0x1E)
Error: MEMORY_MANAGEMENT
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 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 that cannot be identified at this time.
On Thu 2013-01-10 14:05:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011013-49625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340)
Bugcheck code: 0xA (0xFFFFFA001128A340, 0x2, 0x0, 0xFFFFF800D86F2ACC)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.