Hei. Helt siden pcen var ny, har jeg fått regelmessige bluescreens. Selv om det har skjedd "regelmessig", har det ikke skjedd ofte nok til at jeg har orket å sende inn pcen til Multicom hvor jeg kjøpte den. Er det noen som klarer å finne ut av hva som er galt ved å se på vedlagte crash dumps?
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 9/17/2013 11:31:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091713-34211-01.dmp
This was probably caused by the following module: bowser.sys (bowser+0x162A4)
Bugcheck code: 0x7A (0xFFFFF6FC40068A90, 0xFFFFFFFFC0000056, 0xD7D5860, 0xFFFFF8800D1522A4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\bowser.sys
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Lan Manager Datagram Receiver Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 9/17/2013 11:31:35 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: bowser.sys (bowser+0x162A4)
Bugcheck code: 0x7A (0xFFFFF6FC40068A90, 0xFFFFFFFFC0000056, 0xD7D5860, 0xFFFFF8800D1522A4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\bowser.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Lan Manager Datagram Receiver Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 9/10/2013 8:35:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091013-33992-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xEE758)
Bugcheck code: 0x7A (0xFFFFF6FC4000B7F8, 0xFFFFFFFFC0000056, 0x812DB860, 0xFFFFF880016FF758)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NTFS-driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 9/3/2013 7:03:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090313-33119-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xF0CA8)
Bugcheck code: 0x7A (0xFFFFF6FC4000B9E8, 0xFFFFFFFFC0000056, 0x78440860, 0xFFFFF8800173DCA8)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NTFS-driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Mon 7/1/2013 9:55:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070113-24024-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xEED18)
Bugcheck code: 0x7A (0xFFFFF6FC4000B8E0, 0xFFFFFFFFC0000056, 0x500EC860, 0xFFFFF8800171CD18)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NTFS-driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sun 10/21/2012 6:04:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102112-21122-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x19 (0x22, 0xFFFFFA800D156000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 9/3/2012 9:37:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090312-26098-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009B37060, 0xFFFFFA8009B37340, 0xFFFFF80002DD9510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 9/3/2012 9:32:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090312-31746-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x2CBA0)
Bugcheck code: 0x7A (0xFFFFF6FC4000CE70, 0xFFFFFFFFC000000E, 0x1595EB860, 0xFFFFF880019CEBA0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sun 9/2/2012 8:26:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090212-16333-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009CA4B30, 0xFFFFFA8009CA4E10, 0xFFFFF80002D84510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 9/2/2012 7:27:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090212-27393-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xEF648)
Bugcheck code: 0x7A (0xFFFFF6FC40009868, 0xFFFFFFFFC000000E, 0x1D6BF0860, 0xFFFFF8800130D648)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NTFS-driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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.
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 9/17/2013 11:31:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091713-34211-01.dmp
This was probably caused by the following module: bowser.sys (bowser+0x162A4)
Bugcheck code: 0x7A (0xFFFFF6FC40068A90, 0xFFFFFFFFC0000056, 0xD7D5860, 0xFFFFF8800D1522A4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\bowser.sys
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Lan Manager Datagram Receiver Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 9/17/2013 11:31:35 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: bowser.sys (bowser+0x162A4)
Bugcheck code: 0x7A (0xFFFFF6FC40068A90, 0xFFFFFFFFC0000056, 0xD7D5860, 0xFFFFF8800D1522A4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\bowser.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Lan Manager Datagram Receiver Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 9/10/2013 8:35:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091013-33992-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xEE758)
Bugcheck code: 0x7A (0xFFFFF6FC4000B7F8, 0xFFFFFFFFC0000056, 0x812DB860, 0xFFFFF880016FF758)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NTFS-driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 9/3/2013 7:03:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090313-33119-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xF0CA8)
Bugcheck code: 0x7A (0xFFFFF6FC4000B9E8, 0xFFFFFFFFC0000056, 0x78440860, 0xFFFFF8800173DCA8)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NTFS-driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Mon 7/1/2013 9:55:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070113-24024-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xEED18)
Bugcheck code: 0x7A (0xFFFFF6FC4000B8E0, 0xFFFFFFFFC0000056, 0x500EC860, 0xFFFFF8800171CD18)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NTFS-driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sun 10/21/2012 6:04:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102112-21122-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x19 (0x22, 0xFFFFFA800D156000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 9/3/2012 9:37:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090312-26098-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009B37060, 0xFFFFFA8009B37340, 0xFFFFF80002DD9510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 9/3/2012 9:32:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090312-31746-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x2CBA0)
Bugcheck code: 0x7A (0xFFFFF6FC4000CE70, 0xFFFFFFFFC000000E, 0x1595EB860, 0xFFFFF880019CEBA0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Sun 9/2/2012 8:26:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090212-16333-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009CA4B30, 0xFFFFFA8009CA4E10, 0xFFFFF80002D84510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 9/2/2012 7:27:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090212-27393-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xEF648)
Bugcheck code: 0x7A (0xFFFFF6FC40009868, 0xFFFFFFFFC000000E, 0x1D6BF0860, 0xFFFFF8800130D648)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NTFS-driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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.