Anyone knowledgeable with computer repairs? BSOD!!

31 posts

RELATED
PRODUCTS

Anyone knowledgeable with computer repairs? BSOD!! 2014-01-18T02:28:18+00:00 My computer crashes constantly and not sure how diagnose the crash files, I have whocrashed it which analyzes the computer crash dump files but not sure how to read this or what to do next in narrowing down the problem and fixing it. Here is the crash analyses -------------------------------------------------------------------------------- System Information (local) -------------------------------------------------------------------------------- computer name: GOLDENDAWN-PC windows version: Windows 7 , 6.1, build: 7600 windows dir: C:\Windows CPU: AuthenticAMD AMD Athlon(tm) II X4 610e Processor AMD586, level: 16 4 logical processors, active mask: 15 RAM: 6169759744 total VM: 2147352576, free: 1977933824 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Wed 1/8/2014 2:13:27 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\010714-22713-01.dmp uptime: 00:25:28 This was probably caused by the following module: hal.dll (hal!HalGetScatterGatherList+0x44) Bugcheck code: 0xD1 (0x14, 0x2, 0x8, 0x14) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\hal.dll product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Hardware Abstraction Layer DLL 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 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 Wed 1/8/2014 2:13:27 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp uptime: 00:25:28 This was probably caused by the following module: hal.dll (hal!HalGetScatterGatherList+0x44) Bugcheck code: 0xD1 (0x14, 0x2, 0x8, 0x14) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\hal.dll product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Hardware Abstraction Layer DLL 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 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 1/6/2014 6:17:52 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\010614-16910-01.dmp uptime: 13:55:05 This was probably caused by the following module: ntfs.sys (Ntfs! ?? ::FNODOBFM::`string'+0x2869) Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88001F996E8, 0xFFFFF88001F98F50, 0xFFFFF8000209F8E2) Error: NTFS_FILE_SYSTEM file path: C:\Windows\system32\drivers\ntfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT File System Driver Bug check description: This indicates a problem occurred in the NTFS file system. 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/1/2013 8:18:36 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\090113-14211-01.dmp uptime: 00:22:37 This was probably caused by the following module: usbport.sys (USBPORT!USBPORT_AssertSig+0x25) Bugcheck code: 0xFE (0x6, 0xFFFFFA8008AB9110, 0x66725045, 0x0) Error: BUGCODE_USB_DRIVER file path: C:\Windows\system32\drivers\usbport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB 1.1 & 2.0 Port Driver Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver. 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 Thu 8/22/2013 5:32:30 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\082213-17643-01.dmp uptime: 00:01:11 This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x34 (0x50853, 0xFFFFF88001FA0718, 0xFFFFF88001F9FF80, 0xFFFFF800020996EE) Error: CACHE_MANAGER Bug check description: This indicates that a problem occurred in the file system's cache manager. 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 8/22/2013 5:29:51 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\082213-15865-01.dmp uptime: 00:03:42 This was probably caused by the following module: win32k.sys (win32k!ThreadUnlock1+0x3) Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF960000FC143) Error: UNEXPECTED_KERNEL_MODE_TRAP file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. 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 Thu 8/22/2013 5:25:14 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\082213-16442-01.dmp uptime: 00:00:59 This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 Thu 8/22/2013 3:32:02 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\082113-11325-01.dmp uptime: 01:05:47 This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CFB651) Error: UNEXPECTED_KERNEL_MODE_TRAP Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. 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 8/22/2013 2:25:17 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\082113-10467-01.dmp uptime: 00:47:33 This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CD4CF2) Error: UNEXPECTED_KERNEL_MODE_TRAP Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. 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 8/22/2013 1:11:45 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\082113-11076-01.dmp uptime: 00:01:34 This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xD1 (0x1, 0xB, 0x1, 0xFFFFFA80074B3C50) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL 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 that cannot be identified at this time. On Thu 8/22/2013 1:09:17 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\082113-11247-01.dmp uptime: 00:01:04 This was probably caused by the following module: ntfs.sys (Ntfs!NtfsCopyReadA+0x18F) Bugcheck code: 0x4E (0x2, 0x114FFF, 0x1BFFFF, 0x1000) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\drivers\ntfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT File System Driver 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 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 8/18/2013 12:40:46 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081813-13291-01.dmp uptime: 00:03:49 This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xD1 (0x6470100, 0x2, 0x8, 0x6470100) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL 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 that cannot be identified at this time. On Sun 8/18/2013 12:36:04 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\081813-13993-01.dmp uptime: 00:00:45 This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CA819B, 0xFFFFF880095E6720, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 that cannot be identified at this time. On Sun 8/18/2013 7:18:05 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\081813-13150-01.dmp uptime: 00:00:56 This was probably caused by the following module: ci.dll (CI!I_MapCatalog+0x25B) Bugcheck code: 0x1A (0x41790, 0xFFFFFA80051ED2A0, 0xFFFF, 0x0) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ci.dll product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Code Integrity Module 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 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 8/18/2013 7:16:14 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\081813-13010-01.dmp uptime: 00:40:56 This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x47FFA) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800408FFFA, 0xFFFFF8800318C788, 0xFFFFF8800318BFF0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\bcmwl664.sys product: Broadcom 802.11 Network Adapter wireless driver company: Broadcom Corporation description: Broadcom 802.11 Network Adapter wireless driver 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. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation). Google query: Broadcom Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 21 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: dxgkrnl.sys (DirectX Graphics Kernel, Microsoft Corporation) bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation) If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. Touch The Universe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=190615

t3toooo t3toooo https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=92089: KVRAF
Contact t3toooo

SoundCloud; 2193 posts since 25 Dec, 2005; Contact:
Contact t3toooo

SoundCloud

Post by t3toooo » Sun Jan 19, 2014 8:44 pm

0
Quote

just install the ubuntu 12.4 iso on a usb stick or on a cd.

http://www.ubuntu.com/download/desktop

i 'm not sure but maybe it works better with amd graphics cards,

however,if you have a old spare hard drive just install windows 7 without activation,for testing.

disconnect any peripheral devices,usb,pci.
if you still got problems try to reverse engineer like temporarily replacing,ram,graphics card psu.

clean everything and keep the parts cooled sufficiently.

also check your cpu temp.

http://www.techpowerup.com/realtemp/

..and maybe update your bios as well but the computer should work before you do this.

|\/| _ o _ |\ |__ o
| |__> |(_ | \(_/_|

Post Reply

31 posts

Return to “Computer Setup and System Configuration”