BSOD on HP 1285DX Debugging Help Request (DMP Analysis)

[Rhadamanthys]

Hi Guys

I've been trying to get Windows 7 to work on my Notebook HP Model DV7-1285DX for the longest time now to no avail. The install always goes without a hitch, but am plagued with BSODs from the word go
I've installed most every Beta version and every permutation of drivers out there

Always attributed the problem to unstable beta product & lack of official Windows 7 Drivers. My latest OS is the RTM with ALL of the hardware properly configured. HP has the Windows 7 Drivers for my model on their website (including the BIOS update which I installed)

I use the notebook for watching movies on my TV (connecting via HDMI) and I have been dealing with the BSOD as many as 4-5 times during a movie at times. The problem BSOD and reboots dont follow any recognizable pattern (sometimes I can get thru various movies with no BSOD, I dont get the BSOD ONLY while watching movies either - it happens just as much while using the notebook normally as well)

Since yesterday I've had 7 BSODs and I installed WinDBG to have a look at the data for the first time. I'm no expert but its completely random from what I see - the processes involved are different in each DMP

I ran MEMtest86 and got No errors

Can somebody who knows what the files "really" say have a look at the attached dumps and advise what I ought to do to fix this problem??

Any help would be more than welcome - Thanks

 

[zigzag3143]

Hi Guys

I've been trying to get Windows 7 to work on my Notebook HP Model DV7-1285DX for the longest time now to no avail. The install always goes without a hitch, but am plagued with BSODs from the word go
I've installed most every Beta version and every permutation of drivers out there

Always attributed the problem to unstable beta product & lack of official Windows 7 Drivers. My latest OS is the RTM with ALL of the hardware properly configured. HP has the Windows 7 Drivers for my model on their website (including the BIOS update which I installed)

I use the notebook for watching movies on my TV (connecting via HDMI) and I have been dealing with the BSOD as many as 4-5 times during a movie at times. The problem BSOD and reboots dont follow any recognizable pattern (sometimes I can get thru various movies with no BSOD, I dont get the BSOD ONLY while watching movies either - it happens just as much while using the notebook normally as well)

Since yesterday I've had 7 BSODs and I installed WinDBG to have a look at the data for the first time. I'm no expert but its completely random from what I see - the processes involved are different in each DMP

I ran MEMtest86 and got No errors

Can somebody who knows what the files "really" say have a look at the attached dumps and advise what I ought to do to fix this problem??

Any help would be more than welcome - Thanks

These are pretty straight forward. Memory corruption

I would download memtestx86 and run for at least 5 passes.

Let us know if you need help


Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder (3)\032110-16208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c87e50
Debug session time: Sun Mar 21 12:06:56.625 2010 (GMT-4)
System Uptime: 0 days 0:04:17.607
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc000001d, fffff80002ac9c89, fffff88003139628, fffff88003138e80}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002ac9c89, The address that the exception occurred at
Arg3: fffff88003139628, Exception Record Address
Arg4: fffff88003138e80, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nt!KeFlushMultipleRangeTb+e9
fffff800`02ac9c89 fe              ???

EXCEPTION_RECORD:  fffff88003139628 -- (.exr 0xfffff88003139628)
ExceptionAddress: fffff80002ac9c89 (nt!KeFlushMultipleRangeTb+0x00000000000000e9)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff88003138e80 -- (.cxr 0xfffff88003138e80)
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003138fb8
rdx=fffffa80081849d0 rsi=0000000000000001 rdi=fffff80002c34e80
rip=fffff80002ac9c89 rsp=fffff88003139860 rbp=0000000002c30c18
 r8=0000000000000004  r9=0000000000000000 r10=000000000000000d
r11=0000000000000000 r12=000000000000000d r13=0000000000000000
r14=fffff80002c30c10 r15=0000000000000001
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!KeFlushMultipleRangeTb+0xe9:
fffff800`02ac9c89 fe              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x7E

PROCESS_NAME:  CLMLSvc.exe

CURRENT_IRQL:  c

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

LAST_CONTROL_TRANSFER:  from fffff80002acfc8b to fffff80002ac9c89

FAILED_INSTRUCTION_ADDRESS: 
nt!KeFlushMultipleRangeTb+e9
fffff800`02ac9c89 fe              ???

STACK_TEXT:  
fffff880`03139860 fffff800`02acfc8b : 00000000`00000332 00000000`00000001 00000000`00000002 00000000`0000032e : nt!KeFlushMultipleRangeTb+0xe9
fffff880`03139930 fffff800`02b3ca0e : fffffa80`08184cd8 fffff880`00000001 00000000`00000001 fffff880`03139bb0 : nt!MiAgeWorkingSet+0x36b
fffff880`03139ae0 fffff800`02ad06e2 : 00000000`00000102 00000000`00000000 fffffa80`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03139b80 fffff800`02ad096f : 00000000`00000008 fffff880`03139c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03139bd0 fffff800`02d5f166 : fffffa80`05524680 00000000`00000080 fffffa80`05505b30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03139d40 fffff800`02a9a486 : fffff800`02c34e80 fffffa80`05524680 fffff800`02c42c40 ad0cff15`5eadfdf6 : nt!PspSystemThreadStartup+0x5a
fffff880`03139d80 00000000`00000000 : fffff880`0313a000 fffff880`03134000 fffff880`03139710 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
8 errors : !nt (fffff80002ac9c83-fffff80002ac9cbb)
fffff80002ac9c80  00  00  49 *24  e0  03  e8  b5  8f  fe  ff *4c  44  8b  44  24 ..I$.......LD.D$
fffff80002ac9c90  50  8b  47 *41  48  8d  0d  c5  0e  1f  00 *06  8d  54  24  50 P.GAH........T$P
fffff80002ac9ca0  8b  0c  81 *48  0f  b7  c0  8b  d1  c1  ea *74  3b  c2  76  14 ...H.......t;.v.
fffff80002ac9cb0  83  e1  3f *00  d3  e6  48  f7  d6  48  21 *00  d4  58  66  44 ..?...H..H!..XfD

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff88003138e80 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------