New
#1
BSOD 1x a day NEW machine HP Touchsmart i7 600q
Hi, I have a one month old HP Touchsmart 600q i7 computer that I purchased with windows 7 home premium and then upgraded to windows 7 pro 64 bit. It has a BSOD relatively often, usually occurring near midnight or when the computer is about to go into idle, but not always.
I have done all the diagnostics the machine has, checked drivers (although the newest nvidia geforce 230 driver is listed on their website, that will not install. I did uninstall it and reinstall it from the HP website, but no change.) Everything seems great and up-t0-date. I just downloaded and burned to DVD windows debugging and after figuring out how to access symbol library analyzed some of the crash dumps, which seem to be of around two different varieties.
from last night:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\051110-21668-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c1e000 PsLoadedModuleList = 0xfffff800`02e5be50
Debug session time: Tue May 11 00:41:41.335 2010 (UTC - 4:00)
System Uptime: 0 days 10:06:09.636
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffb1e0000016c, 0, fffff88000e37242, 7}
Could not read faulting driver name
Probably caused by : circlass.sys ( circlass!IrClassResubmitPingPongIoctlRequest+126 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffb1e0000016c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88000e37242, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec60e0
fffffb1e0000016c
FAULTING_IP:
Wdf01000!FxDevice:ispatch+a6
fffff880`00e37242 ff5040 call qword ptr [rax+40h]
MM_INTERNAL_CODE: 7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880033629d0 -- (.trap 0xfffff880033629d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffb1e0000012c rbx=0000000000000000 rcx=fffffa8007ff7e90
rdx=fffffa8007e71810 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000e37242 rsp=fffff88003362b60 rbp=fffffa8006715370
r8=fffffa8007e889e0 r9=fffffa8007ff0000 r10=fffff880009b2ac0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
Wdf01000!FxDevice:ispatch+0xa6:
fffff880`00e37242 ff5040 call qword ptr [rax+40h] ds:fbc0:fffffb1e`0000016c=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d0d789 to fffff80002c8e600
STACK_TEXT:
fffff880`03362868 fffff800`02d0d789 : 00000000`00000050 fffffb1e`0000016c 00000000`00000000 fffff880`033629d0 : nt!KeBugCheckEx
fffff880`03362870 fffff800`02c8c6ee : 00000000`00000000 00000000`00000000 fffffa80`07e71a00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x40e4b
fffff880`033629d0 fffff880`00e37242 : 00000000`00000000 fffffa80`084dfbb0 fffffa80`07e1c980 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`03362b60 fffff880`00e2378e : 0000057f`f81e34f8 00000000`00000000 fffffa80`06715370 00000000`00000000 : Wdf01000!FxDevice:ispatch+0xa6
fffff880`03362b90 fffff880`0585e846 : fffffa80`08032b50 fffffa80`07e1cb00 fffffa80`084dfbb0 0000057f`f81e34f8 : Wdf01000!imp_WdfRequestSend+0x43a
fffff880`03362be0 fffff880`00e406fb : fffffa80`07e1c9e0 fffff800`02e335f8 00000000`00000000 fffffa80`07e1c9e0 : circlass!IrClassResubmitPingPongIoctlRequest+0x126
fffff880`03362c50 fffff800`02f8b827 : fffffa80`06717910 fffff800`02e93e00 fffffa80`05503680 fffffa80`05503680 : Wdf01000!FxWorkItem::WorkItemThunk+0x113
fffff880`03362c80 fffff800`02c9b861 : fffff800`02f82400 fffff800`02f824a8 fffffa80`05503680 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`03362cb0 fffff800`02f33a86 : 00000000`00000000 fffffa80`05503680 00000000`00000080 fffffa80`0548db30 : nt!ExpWorkerThread+0x111
fffff880`03362d40 fffff800`02c6cb06 : fffff880`0316a180 fffffa80`05503680 fffff880`031750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03362d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
circlass!IrClassResubmitPingPongIoctlRequest+126
fffff880`0585e846 84c0 test al,al
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: circlass!IrClassResubmitPingPongIoctlRequest+126
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: circlass
IMAGE_NAME: circlass.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc0a
FAILURE_BUCKET_ID: X64_0x50_circlass!IrClassResubmitPingPongIoctlRequest+126
BUCKET_ID: X64_0x50_circlass!IrClassResubmitPingPongIoctlRequest+126
Followup: MachineOwner
---------
This is from the day before:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\051010-21808-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02e9be50
Debug session time: Sun May 9 23:35:53.255 2010 (UTC - 4:00)
System Uptime: 0 days 9:22:01.343
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffdda000000c2, 2, 0, fffff80002d29786}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+e14a )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffdda000000c2, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002d29786, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f060e0
fffffdda000000c2
CURRENT_IRQL: 2
FAULTING_IP:
nt! ?? ::FNODOBFM::`string'+e14a
fffff800`02d29786 807b2c00 cmp byte ptr [rbx+2Ch],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff8800335b630 -- (.trap 0xfffff8800335b630)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8005503bb0 rbx=0000000000000000 rcx=fffffa8005503b60
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d29786 rsp=fffff8800335b7c0 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff880009b2180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt! ?? ::FNODOBFM::`string'+0xe14a:
fffff800`02d29786 807b2c00 cmp byte ptr [rbx+2Ch],0 ds:fb60:00000000`0000002c=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ccdb69 to fffff80002cce600
STACK_TEXT:
fffff880`0335b4e8 fffff800`02ccdb69 : 00000000`0000000a fffffdda`000000c2 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0335b4f0 fffff800`02ccc7e0 : 00000000`bd78e000 fffffdda`00000096 ffffffff`ffd00000 00000000`0000096b : nt!KiBugCheckDispatch+0x69
fffff880`0335b630 fffff800`02d29786 : fffffa80`07ad5bf0 fffffa80`05517650 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0335b7c0 fffff800`03077fae : 00000000`00000000 00000000`00000003 00000000`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0xe14a
fffff880`0335b840 fffff800`02f1e26f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PopNotifyCallbacksPreSleep+0x1e
fffff880`0335b870 fffff800`02ccd853 : fffffa80`05503b60 fffff780`00000300 00000000`00000007 fffff800`02cc2000 : nt!NtSetSystemPowerState+0x18f
fffff880`0335b9b0 fffff800`02cc9df0 : fffff800`0313d620 00000000`00000000 fffff800`02e73500 fffff800`02e73500 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0335bb48 fffff800`0313d620 : 00000000`00000000 fffff800`02e73500 fffff800`02e73500 00000000`00000000 : nt!KiServiceLinkage
fffff880`0335bb50 fffff800`0313d7fc : 00000000`00000007 fffff800`02e73500 00000000`00000002 fffff800`00000004 : nt!PopIssueActionRequest+0x280
fffff880`0335bbe0 fffff800`02c8d5bd : 00000000`00000001 fffffa80`05503b00 00000000`00000000 00000000`00000000 : nt!PopPolicyWorkerAction+0x4c
fffff880`0335bc40 fffff800`02cdb861 : fffff800`00000002 fffff800`00000004 fffff800`02c8d4c0 00000000`00000000 : nt!PopPolicyWorkerThread+0xfd
fffff880`0335bcb0 fffff800`02f73a86 : 519485b5`cf51cd54 fffffa80`05503b60 00000000`00000080 fffffa80`0548db30 : nt!ExpWorkerThread+0x111
fffff880`0335bd40 fffff800`02cacb06 : fffff880`0316a180 fffffa80`05503b60 fffff880`031750c0 e87af95c`3486346a : nt!PspSystemThreadStartup+0x5a
fffff880`0335bd80 00000000`00000000 : fffff880`0335c000 fffff880`03356000 fffff880`0335b560 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+e14a
fffff800`02d29786 807b2c00 cmp byte ptr [rbx+2Ch],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+e14a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
FAILURE_BUCKET_ID: X64_0xA_nt!_??_::FNODOBFM::_string_+e14a
BUCKET_ID: X64_0xA_nt!_??_::FNODOBFM::_string_+e14a
Followup: MachineOwner
---------
HELP!! Thanks so much.