Member Avatar for bowlboy

Hi,

I ocassionally got blue screen when I using my HP destop (Pavilion Elite e9270t). My system is Win7 64-bit. It can happen when I was surfing, watching movie or other circumstances.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.
Locale ID: 2052

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000096
BCP2: FFFFF8800100549F
BCP3: FFFFF8800748A9C0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050910-16754-01.dmp
C:\Users\ame\AppData\Local\Temp\WER-40326-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt

If anyone knows anything about this, please let me know.

Thank you!

Edited by bowlboy because: n/a
  • 3 Contributors
  • 5 Replies
  • 238 Views
  • 4 Months Discussion Span
  • Latest Post Latest Post by tinum

Dani AI

Generated

Pattern summary and next steps based on the dumps and replies from , and :

The variety of stop codes and modules reported (SYSTEM_SERVICE_EXCEPTION pointing at fltmgr.sys, MEMORY_MANAGEMENT and IRQL faults, THREAD_STUCK_IN_DEVICE_DRIVER from dxgkrnl, plus a later WHEA 0x124) argues against a single user‑mode app being guilty. 0x3B (SYSTEM_SERVICE_EXCEPTION) often records where the kernel blew up but not the true root cause, so treat both drivers and hardware as possible sources. (learn.microsoft.com)

What fltmgr.sys means and what to check next: fltmgr is the Windows File System Filter Manager — third‑party minifilter drivers (antivirus on‑access scanners, backup/overlay tools, encryption or cloud sync clients) attach through it and can cause crashes that surface in fltmgr. Temporarily isolate or remove any such filter drivers (test in Safe Mode, disable/uninstall one at a time) and check Event Viewer for correlated driver/service errors before wholesale fixes. (learn.microsoft.com)

Hardware angle you should treat seriously: the WHEA_UNCORRECTABLE_ERROR (0x124) explicitly signals a hardware machine‑check and, together with MEMORY_MANAGEMENT dumps, makes RAM/CPU/thermal/PSU or storage problems plausible. Run a full, bootable memory stress test (MemTest86) for many passes and try single‑DIMM swaps; run the vendor HDD/SSD SMART tests and keep backups before deeper work. (learn.microsoft.com)

Graphics/driver items and quick checks: THREAD_STUCK errors tied to dxgkrnl point to GPU driver or hardware problems — perform a clean GPU driver reinstall (use vendor clean‑uninstall tools), disable any overclocking and watch temperatures. Run a system file check as a lightweight extra check (for example sfc /scannow) and only after isolating filters and bad RAM consider component swaps (spare stick/GPU/PSU) or contacting HP with the minidumps. (learn.microsoft.com)

Short checklist to apply in order (do not repeat the WhoCrashed / chkdsk steps already tried here): isolate file‑system filters, run overnight MemTest86, run vendor disk SMART tools, clean GPU driver install, check temps/PSU, then escalate to hardware swap or OEM support if failures continue.

Recommended Answers

All 5 Replies

Member Avatar for happyrock

download and install WhoCrashed from here..
This program checks for any drivers which may have been causing your computer to crash....

click on it...then run...then next...put a tick in accept...then next..put a tick in the don't create a start menu folder..then next...put a tick in create a desktop icon..then install.. then make sure there is a tick in launch whocrashed...then finish...then click Analyze ...

if you get a message
This software requires the right version of Windows Debugging Tools for your type of computer. Because this is not normally installed and is not redistributable, we suggest you select the download option from below. Then the right package will be downloaded to a temporary folder and the required files will be extracted from the package automatically. You only need to do this once
click on download then try running it again

WhoCrashed will create report...you have to scroll down to see it
Copy and paste it into your next reply...

Member Avatar for bowlboy

Thank you happyrock.

There are 23 crash dumps found and analyzed. I list the most recent ones below:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 2010/5/9 1:52:32 your computer crashed
This was likely caused by the following module: fltmgr.sys
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF8800100549F, 0xFFFFF8800748A9C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\050910-16754-01.dmp
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Wed 2010/4/28 23:22:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002A7D450)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\042810-16099-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 2010/4/25 15:28:28 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002AFDADD)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\042510-19936-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Mon 2010/4/19 2:03:05 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x5002, 0xFFFFF70001080000, 0x17B0, 0xD8000C15FFFFFFFE)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\041910-17269-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 2010/3/28 1:29:24 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41287, 0x6C61023, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\032810-15834-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 2010/3/7 23:08:00 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x7F8B, 0x2, 0x1, 0xFFFFF80002ACC45B)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\030710-17050-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Thu 2010/3/4 17:41:40 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002A81D50)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\030410-18408-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

Conclusion:
23 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.

Thanks again for your help!

Member Avatar for bowlboy

There are some more crash dumps here:

On Fri 2010/2/19 2:57:02 your computer crashed
This was likely caused by the following module: fileinfo.sys
Bugcheck code: 0x50 (0xFFFFF89F94FE103C, 0x0, 0xFFFFF8800138B1DF, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\021910-20124-01.dmp
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Thu 2010/2/11 1:40:42 your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x100000EA (0xFFFFFA800913CB60, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\Windows\Minidump\021110-16910-01.dmp
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Wed 2010/1/27 16:34:36 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x1E (0xFFFFFFFF80000004, 0xFFFFF880014A5CD1, 0x0, 0x177)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\012710-16723-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Thu 2010/1/7 5:25:15 your computer crashed
This was likely caused by the following module: ndis.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800167C657, 0xFFFFF880075BEB00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\010710-16988-01.dmp
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

Member Avatar for happyrock

lets start with chkdsk /r...
the how to is

Edited by happyrock because: n/a
Member Avatar for tinum

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 9/29/2010 7:55:22 AM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x124 (0x0, 0x86193024, 0xB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
Dump file: C:\Windows\Minidump\092910-25724-01.dmp

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.