New
#1
BSOD's and problems booting computer.
To start off with I'm not all that great with computers, for a little while now the computer has been suffering badly from random freezing up, restarting itself multiple times in a row and lots of different BSOD's. As of recently there's been a real struggle to even get it to boot properly; alot of the time it'll crash at the very first screen and some white lines or dots will flash across it, if it does happen to get past the first screen it either restarts itself or crashes at the 'loading windows' screen. Sometimes there'll be a blank screen with a message saying either 'detecting arrays' or that the BIOS settings have been set to default, or sometimes just a string of 0's.
It also does a short beep and then a long beep if it's been restarting itself too much even though once it did just do one constant beep.
I really have no idea what's wrong with it and don't even know where to begin with trying to fix it, i've done all the windows updates but it's still not working properly.
I'd appreciate it if someone could help try to find the cause of this as I can't understand what alot of these errors even mean.
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ (2 CPUs), ~2.6GHz
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601)
System Manufacturer: HP-Pavilion
System Model: KA777AA-ABU a6305.uk
BIOS: Phoenix - AwardBIOS v6.00PG
Memory: 2048MB RAM
Page file: 659MB used, 3177MB available
DirectX version: DirectX 11
On Thu 15/09/2011 15:56:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091511-26925-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFFFFFECF8E80, 0x2, 0x8, 0xFFFFFFFFFECF8E80)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 15/09/2011 15:56:25 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: 0xD1 (0xFFFFFFFFFECF8E80, 0x2, 0x8, 0xFFFFFFFFFECF8E80)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 15/09/2011 15:39:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091511-25318-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD6 (0xFFFFF98012ABB000, 0x0, 0xFFFFF8800F352D86, 0x0)
Error: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates the driver accessed memory beyond the end of its pool allocation.
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 15/09/2011 15:28:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091511-29858-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x4E (0x99, 0x50CA0, 0x2, 0x1802)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 which cannot be identified at this time.
On Wed 14/09/2011 17:13:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091411-26551-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70590)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Tue 13/09/2011 16:30:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091311-32479-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1A (0x403, 0xFFFFF6800002AAF8, 0x8CC0000041140025, 0xFFFFF68000005402)
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 which cannot be identified at this time.
On Mon 12/09/2011 14:44:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091211-28953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x95A4F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800028E5A4F, 0xFFFFF880033D05C8, 0xFFFFF880033CFE30)
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.
I've tried opening the little memory dump files but it's a DMP file which I can't open.