Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD and screen freezes frequently - help Decoding crash dump analysis

06 Jan 2014   #1
TJGOA

Windows 7 Home Premium 64-bit SP1
 
 
BSOD and screen freezes frequently - help Decoding crash dump analysis

I have frequent crashes and freezes so I decided to get whocrashed software to analyze the crash dump files and now have no idea what to do next. I would greatly appreciate help in decoding the analysts so I can investigate this further to hopefully fix this problem.

I have a Dell Inspiron One 2305 and I read awhile back that this is a frequent problem that may reside in a faulty SATA cable and needs to be replace but am as yet unsure how to confirm this. I installed windows 7 over one that couldn't boot and also installed another instance on the recovery partition which is still there I keep just in case. All but two drivers are up to date : The ATI I/O Communications Processor SMBus Controller, usb controller.

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: 1915531264




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

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 Mon 1/6/2014 6:17:52 PM GMT your computer crashed
crash dump file: C:\Windows\memory.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



On Sun 8/18/2013 6:22:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081813-12074-01.dmp
uptime: 00:00:53
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CBFEE3, 0x0, 0x14)
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

20 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has 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:

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.


My System SpecsSystem Spec
.
06 Jan 2014   #2
TJGOA

Windows 7 Home Premium 64-bit SP1
 
 

I am also a little hesitant to install an update to a driver because it might freeze mid way and I heard that is really bad and I might permanently loose access to computer, is this true?
My System SpecsSystem Spec
07 Jan 2014   #3
TJGOA

Windows 7 Home Premium 64-bit SP1
 
 

bump
My System SpecsSystem Spec
.

10 Jan 2014   #4
TJGOA

Windows 7 Home Premium 64-bit SP1
 
 

still unsolved
My System SpecsSystem Spec
13 Jan 2014   #5
TJGOA

Windows 7 Home Premium 64-bit SP1
 
 

bump
My System SpecsSystem Spec
Reply

 BSOD and screen freezes frequently - help Decoding crash dump analysis




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
No BSOD/memory dump, Random Freezes, Event Log Analysis, Desperate
My kingdom for a resolution! I've troubleshooted everything I can think of. My computer just randomly freezes. I receive no BSOD either. It just stops responding, the monitor goes dead since it loses signal, yet the computer fans and HD lights continue to run. There is no response from it...
BSOD Help and Support
Crash Dump Analysis e-si Juli@
Hi all ,everyday's my pc make me a gift! is a Blue screen. the problem it seems to be; the new drivers of my professional sound card Juli@.I have signalled the problem many times... but anybody answered by the firm Someone of you has had the same problem? Thanks. The rapport of Blue screen...
BSOD Help and Support
Crash dump analysis
Hi all, can anyone give me an output of this dump file i havent got windbg on this machine at home and havent got time to set it up at the moment because of http://www.sevenforums.com/chillout-room/268870-new-addition-family.html i think its likely gfx card related as ive had it in and out lately...
BSOD Help and Support
BSOD crash usbport.sys suspected, please help with dump file analysis
I have an Asus G53JW notebook that has BSOD failures. Tried updating all drivers with Driver Reviver, run memtest86+ to check ram and checked disk with SeaTools for Windows but no faults so far. The notebook has no USB devices connected externally when the BSOD occurs, on most occasions the BSOD...
BSOD Help and Support
BSOD, Crash Dump Analysis
Hello, For some time now, I have been having a lot of BSODs. Like up to 5 times a day. Sometimes it happens after a long time idling, sometimes when I stress the CPU. It can happen when I close my session, try to close the computer or restart it. I had an overclock on everything, but for the...
BSOD Help and Support
Win7 X64 blue screen ID 124, need help decoding dump
Hi all, Extremely frustrated with my media center PC. After installing Win7 Home Premium 64, I now periodically get blue screens, several times per day. Same MO, just watching video usually. Added RAM, replaced video card, replaced tuner card, did memtest, cleaned and reseated CPU. Temps...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 12:53.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App