KVR Audio

Touch The Universe · Post by **Touch The Universe** » Sat Jan 18, 2014 2:28 am

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.

legendCNCD · Post by **legendCNCD** » Sat Jan 18, 2014 8:37 am

Update wireless driver and gfx driver, also run memtest 86..

UltraJv · Post by **UltraJv** » Sat Jan 18, 2014 11:06 am

Id take it to a friend who knows about PCs. You've got problems with drivers, WIFI, USB and god knows what. Could mean a HDD fail or format and re install Windows. Could mean reseating a card. Could be a PSU problem.

Kriminal · Post by **Kriminal** » Sat Jan 18, 2014 11:52 am

Bin it, buy a new one.

tehlord · Post by **tehlord** » Sat Jan 18, 2014 12:13 pm

It's often a borked memory stick.

If you feel comfortable doing it open up the case and pull the memory sticks out. Vacuum out all the crap in the machine and reseat the memory. If it still happens, reseat the memory sticks one at a time and see if one of the sticks causes a problem.

The other issue 'could' be a faulty PSU but the only way to test that is to put a new one in (not really that hard) or know it for sure when it finally breaks and the machine just stops working.

A driver issue is a possibility too, but that's often tricky to track down. Updating the obvious drivers are a good start though.

seismic1 · Post by **seismic1** » Sat Jan 18, 2014 1:14 pm

How old is the machine? Those Inspiron 2305s are all-in-one systems, and as such, hardware mods may be tricky. I note that there is a 3-month gap between two of the crashes. Was the machine left powered down for an extended period?

noizetronic · Post by **noizetronic** » Sat Jan 18, 2014 1:27 pm

Another vote for memtest, followed by a

Code: Select all

chkdsk /f /r

(as administrator, will likely require a lengthy reboot). Looking for new drivers and / or machine BIOS might be a good idea if those two steps don't reveal anything wrong.

Gonga · Post by **Gonga** » Sat Jan 18, 2014 2:46 pm

It never hurts to clean out the dust and re-seat memory sticks and cards, but this looks like a driver issue. What changes have you made to the system? How recently did you update the hardware drivers? Can you do a system restore to a previous state as a troubleshooting method?

If updating your BIOS and drivers doesn't help, try uninstalling the existing drivers first.

IS all your data on a separate drive from your system? Have you made backups of data and system?

seismic1 · Post by **seismic1** » Sat Jan 18, 2014 2:53 pm

Some of those crashes are occurring so frequently, I would be wary of even attempting a driver update. System crashes are no respecter of atomicity. I would try to eliminate basic hardware faults first, and giving the machine a clean shouldn't hurt, as long as you're careful. Beware of static discharge issues when handling memory modules.

Aloysius · Post by **Aloysius** » Sat Jan 18, 2014 3:00 pm

I've often repaired PC Problems simply by starting in Safe Mode (F8) and then restarting my Windows 7 Laptop.

Dire warnings disappear as if by magic. No need to get out the jackhammers or call the plumber.

As an example: Windows 7 and FireFox and YouTube can be a deadly Cocktail. You could easily have frequent problems with same. Etc...

seismic1 · Post by **seismic1** » Sat Jan 18, 2014 3:14 pm

Does the machine ever run for more than a couple of minutes at a time? If it does, you should try to take a look at the system event logs. They might indicate the cause of the problem.

mystran · Post by **mystran** » Sat Jan 18, 2014 4:17 pm

noizetronic wrote:Another vote for memtest, followed by a
Code: Select all
chkdsk /f /r
(as administrator, will likely require a lengthy reboot). Looking for new drivers and / or machine BIOS might be a good idea if those two steps don't reveal anything wrong.

Memtest yes, but careful with anything else. If there's a memory problem then chkdsk could end up trashing the filesystem (which can be solved by reinstalling, but still).

Do NOT attempt a BIOS upgrade when suspecting hardware problems.

If something goes wrong with such an upgrade, in the worst case you could end up with a system that can be fixed only by replacing the BIOS chip with one containing a working version. Some motherboards have fail-safe features (secondary BIOS copy or special restore modes), but make sure to check before you rely on those.

Touch The Universe · Post by **Touch The Universe** » Sat Jan 18, 2014 4:35 pm

Computer freezes about every 5-15 minutes, so far updated all drivers except the usb and one other which I can't recall, already performed two installations of win7 from recovery options a few months ago but never formatted before installation. I just learned the importance of such recently and will try this again if all else fails. I've ran memtest for 12 hours with over 90 errors, I guess this means the memory is fried? Also I remember reading up on this issue a little while ago about dell all in one inspirion 2305 series shipping out with faulty or loose sata cables and this screen freeze issue is quite common?? So thinking of ordering another sata cable, the one dell shipped is apparently extremely cheap/defective? Will post current crash dump data if I can before another crash... Thanks so far

noizetronic · Post by **noizetronic** » Sat Jan 18, 2014 4:48 pm

mystran wrote: Memtest yes, but careful with anything else. If there's a memory problem then chkdsk could end up trashing the filesystem (which can be solved by reinstalling, but still).

Do NOT attempt a BIOS upgrade when suspecting hardware problems.

True; i ment the steps in my last post to be taken in that order.

Touch The Universe · Post by **Touch The Universe** » Sat Jan 18, 2014 4:56 pm

Just finished upgrading wireless driver, also I opened up the event viewer which is new to me and have no idea where to begin and the windows are quite clumsy, small can't read full list and I don't see an option to extend the windows to view everything? What should I look for here?

Anyone knowledgeable with computer repairs? BSOD!!