Windows 7 Frequent BSOsD on hp pavilion, help please!!

gzaf · May 13, 2011

Hello guys,
I'm experiencing troubles with a hp pavilion dv6000 and win 7 32 bit. The laptop was purchased about 4 years ago with win vista and updated to win 7 one year ago; since then, I have frequent but appearently random BSOD, with no information about any file or driver where the problem occurred, in the blue screen. There isn't any obvious correlation with any application or process running at the moment of the crash. I'm sending to you a .zip folder containing all the minidump files since the first problem occurred, plus the RamMon log files, in text format, and the CpuZ printscreens. Can you help me, please??

Thanks to everyone!

Link RemovedLink RemovedLink Removed

msfanboy98 · May 13, 2011

This may be a video drivers issue. I recommend you try to update your video drivers.

kaos · May 13, 2011

ill look for u now

kaos · May 13, 2011

ok first dump file shows the following

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {80000004, 9660d685, 9cbe3c0c, 0}

Probably caused by : win32k.sys ( win32k!DC::erclClip+27 )

Followup: MachineOwner
---------

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 80000004, The exception code that was not handled
Arg2: 9660d685, The address that the exception occurred at
Arg3: 9cbe3c0c, Trap Frame
Arg4: 00000000

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


OVERLAPPED_MODULE: Address regions for 'xaudio' and 'parport.sys' overlap

EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported

FAULTING_IP: 
win32k!DC::erclClip+27
9660d685 c20400          ret     4

TRAP_FRAME:  9cbe3c0c -- (.trap 0xffffffff9cbe3c0c)
ErrCode = 00000000
eax=9cbe3c80 ebx=fe7d9728 ecx=00000001 edx=00000001 esi=ffb8e748 edi=fe7d9920
eip=9660d685 esp=9cbe3c80 ebp=9cbe3c90 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000282
win32k!DC::erclClip+0x27:
9660d685 c20400          ret     4
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  wmplayer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 9660d571 to 9660d685

STACK_TEXT:  
9cbe3c90 9660d571 9cbe3cb8 00000000 00000000 win32k!DC::erclClip+0x27
9cbe3cd4 9660da5c 966125e1 ab011e92 000cdd00 win32k!DC::bSetDefaultRegion+0x125
9cbe3d0c 966125f5 ffbff968 0185000f 00000000 win32k!hbmSelectBitmap+0x2c6
9cbe3d24 8324b44a ab011e92 0185000f 000cdd14 win32k!GreSelectBitmap+0x14
9cbe3d24 76ec64f4 ab011e92 0185000f 000cdd14 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
000cdd14 00000000 00000000 00000000 00000000 0x76ec64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!DC::erclClip+27
9660d685 c20400          ret     4

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!DC::erclClip+27

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdc3f5e

FAILURE_BUCKET_ID:  0x8E_win32k!DC::erclClip+27

BUCKET_ID:  0x8E_win32k!DC::erclClip+27

Followup: MachineOwner

kaos · May 13, 2011

2nd dump file you provided

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 801e0000, 0, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl+1512 )

Followup: MachineOwner
---------

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

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 801e0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8e89e512 to 832dbf3a

STACK_TEXT:  
9b50d010 8e89e512 86105878 9b50fcb8 8e8bb61e nt!ExIsResourceAcquiredSharedLite+0xc
WARNING: Stack unwind information not available. Following frames may be wrong.
9b50d014 86105878 9b50fcb8 8e8bb61e 00000000 dxgkrnl+0x1512
9b50d018 9b50fcb8 8e8bb61e 00000000 00000000 0x86105878
9b50d01c 8e8bb61e 00000000 00000000 00000000 0x9b50fcb8
9b50d020 00000000 00000000 00000000 00000000 dxgkrnl+0x1e61e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl+1512
8e89e512 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl+1512

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac54de1

FAILURE_BUCKET_ID:  0x7f_8_dxgkrnl+1512

BUCKET_ID:  0x7f_8_dxgkrnl+1512

Followup: MachineOwner
---------

msfanboy98 · May 13, 2011

This may be a video drivers issue. I recommend you try to update your video drivers.

kaos · May 13, 2011

3rd dmp file

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {c69bf667, 2, 0, 9021ad2b}

Unable to load image \SystemRoot\system32\DRIVERS\netw5v32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netw5v32.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v32.sys
Probably caused by : netw5v32.sys ( netw5v32+17d2b )

Followup: MachineOwner
---------

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: c69bf667, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 9021ad2b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 833b6718
Unable to read MiSystemVaType memory at 83396160
c69bf667 

CURRENT_IRQL:  2

FAULTING_IP: 
netw5v32+17d2b
9021ad2b 8bcf            mov     ecx,edi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  83374b64 -- (.trap 0xffffffff83374b64)
ErrCode = 00000000
eax=00000000 ebx=8683e068 ecx=86c56b80 edx=86511bd0 esi=8683ce58 edi=8683ce64
eip=9021ad2b esp=83374bd8 ebp=83374bf4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
netw5v32+0x17d2b:
9021ad2b 8bcf            mov     ecx,edi
Resetting default scope

LAST_CONTROL_TRANSFER:  from 9021ad2b to 8329482b

STACK_TEXT:  
83374b64 9021ad2b badb0d00 86511bd0 83377d20 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
83374bf4 9021731c 8683ce58 86c56b80 83374c10 netw5v32+0x17d2b
83374c04 902047a5 86c56b80 83374c50 89274301 netw5v32+0x1431c
83374c10 89274301 86822ec0 00000000 00000000 netw5v32+0x17a5
83374c50 8921f9f4 8683e17c 0083e068 00000000 ndis!ndisMiniportDpc+0xda
83374c78 832b63b5 8683e17c 8683e068 00000000 ndis!ndisInterruptDpc+0xaf
83374cd4 832b6218 83377d20 83381280 00000000 nt!KiExecuteAllDpcs+0xf9
83374d20 832b6038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
83374d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
netw5v32+17d2b
9021ad2b 8bcf            mov     ecx,edi

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  netw5v32+17d2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: netw5v32

IMAGE_NAME:  netw5v32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49cba8f

FAILURE_BUCKET_ID:  0xD1_netw5v32+17d2b

BUCKET_ID:  0xD1_netw5v32+17d2b

Followup: MachineOwner
---------

Code:

Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 8520ec18, Address of the IRP
Arg2: 00001d7b
Arg3: 00000000
Arg4: 00000000

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

*** WARNING: Unable to verify timestamp for avgtdix.sys
*** ERROR: Module load completed but symbols could not be loaded for avgtdix.sys
Unable to load image \SystemRoot\system32\DRIVERS\netw5v32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netw5v32.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v32.sys

IRP_ADDRESS: 8520ec18

FOLLOWUP_IP: 
avgtdix+476b
8e64976b ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x44

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 832cbe11 to 83319d10

STACK_TEXT: 
83362f58 832cbe11 00000044 8520ec18 00001d7b nt!KeBugCheckEx+0x1e
83362f80 8e64976b 8520ec18 8520ecaf 8520ec18 nt!IopFreeIrp+0x22
WARNING: Stack unwind information not available. Following frames may be wrong.
83362f94 832a5b33 00000000 8520ec18 8627c720 avgtdix+0x476b
83362fdc 8e6288f0 8521a410 9fa4b140 83363190 nt!IopfCompleteRequest+0x128
83362ff4 8946a7ee 0220ec58 00000000 000005b4 tdx!TdxReceiveConnectionTlRequestComplete+0xde
8336306c 8945f1da 9fa4b140 00000000 8521a410 tcpip!TcpCompleteClientReceiveRequest+0x1c
83363190 89478c44 8521a410 00000000 8521a508 tcpip!TcpSatisfyReceiveRequests+0x3fe
8336322c 894795c1 8521a410 8521a508 83363268 tcpip!TcpDeliverDataToClient+0x79
83363280 8947e2b9 8521a410 8521a508 8550b0f8 tcpip!TcpDeliverReceive+0x96
833632d0 8947d4f6 8521a410 833632f4 8336332c tcpip!TcpTcbFastDatagram+0x304
83363338 8947d8fc 85e30ca8 8521a410 003633ac tcpip!TcpTcbReceive+0x142
833633a0 8946cab0 85e075e8 85e26000 00000000 tcpip!TcpMatchReceive+0x237
833633f0 8946c812 85e30ca8 85e26000 00005000 tcpip!TcpPreValidatedReceive+0x293
8336340c 894721d3 85e30ca8 85e26000 83363448 tcpip!TcpReceive+0x2d
8336341c 894a448e 83363430 c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
83363448 894a4251 89503f88 8336349c c000023e tcpip!IppDeliverListToProtocol+0x49
83363468 894a3f26 89503d98 00000006 8336349c tcpip!IppProcessDeliverList+0x2a
833634c0 894a1b64 89503d98 00000006 00000000 tcpip!IppReceiveHeaderBatch+0x1f2
83363554 894a0af5 88548640 00000000 00000001 tcpip!IpFlcReceivePackets+0xbe5
833635d0 894a0c66 877fc970 8550b0f8 00000000 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x746
83363604 832ccfaa 8550b0f8 9f3f0cac 85e34798 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x11e
8336366c 894a0cee 894a0b48 83363694 00000000 nt!KeExpandKernelStackAndCalloutEx+0x132
833636a8 8929d18d 877fc902 8550b000 00000000 tcpip!FlReceiveNetBufferListChain+0x7c
833636e0 8928b670 88554aa8 8550b0f8 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0x188
83363708 8928b5e7 00000000 8550b0f8 8859c878 ndis!ndisIndicateSortedNetBufferLists+0x4a
83363884 89236ca5 8651f0e0 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
833638a0 89266a87 8651f0e0 8550b0f8 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2d
833638bc 89266a21 88594c58 8550b0f8 00000000 ndis!ndisFilterIndicateReceiveNetBufferLists+0x46
833638d8 8fd73837 88594c58 8550b0f8 00000000 ndis!NdisFIndicateReceiveNetBufferLists+0x2f
83363900 8fd77497 88594c58 851e7740 8651f0e0 nwifi!Dot11IndicateRecvPackets+0x51
83363920 8928ba2e 88548c08 8550b0f8 00000000 nwifi!Pt6Receive+0x1d3
83363948 89236c1e 8651f0e0 851e7740 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x62
83363970 9020979b 8651f0e0 851e7740 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x52
833639a0 9031eca8 00000001 851e7740 851bb018 netw5v32+0x879b
833639d0 90328236 868176d0 851e7740 85162b00 netw5v32+0x11dca8
833639f0 9020d38e 00000001 85162b00 854a7f00 netw5v32+0x127236
83363a1c 9020d6d3 854a7f00 854a7ff8 85162b00 netw5v32+0xc38e
83363a34 9020cb35 85162b00 854a7fd8 00000000 netw5v32+0xc6d3
83363a50 9031f144 86817710 000000eb 00000000 netw5v32+0xbb35
83363a74 90223ddf 868176d0 854cde90 83363aa8 netw5v32+0x11e144
83363a84 90246cd0 868420b0 854cde90 00000000 netw5v32+0x22ddf
83363aa8 9020d38e 87953000 8522c4c0 854cde90 netw5v32+0x45cd0
83363ad4 9020d6d3 854cdea8 854cdff8 8522c4c0 netw5v32+0xc38e
83363aec 9020cb35 8522c4c0 854cdfd8 868420b0 netw5v32+0xc6d3
83363b08 90224486 868420f0 00000076 00000000 netw5v32+0xbb35
83363b30 9022103b 83363b4c 83363b4c 86845660 netw5v32+0x23486
83363b68 902212a7 86845660 871bea00 87493000 netw5v32+0x2003b
83363bb8 90218e6f 00000001 871bea00 000000ff netw5v32+0x202a7
83363bf4 9021531c 871be801 871bea00 83363c10 netw5v32+0x17e6f
83363c04 902027a5 871bea00 83363c50 8928b301 netw5v32+0x1431c
83363c10 8928b301 867cf5f0 00000000 00000000 netw5v32+0x17a5
83363c50 892369f4 8684717c 00847068 00000000 ndis!ndisMiniportDpc+0xda
83363c78 832a53b5 8684717c 86847068 00000000 ndis!ndisInterruptDpc+0xaf
83363cd4 832a5218 83366d20 83370280 00000000 nt!KiExecuteAllDpcs+0xf9
83363d20 832a5038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
83363d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND: kb

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: avgtdix+476b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: avgtdix

IMAGE_NAME: avgtdix.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4cdd1f96

FAILURE_BUCKET_ID: 0x44_avgtdix+476b

BUCKET_ID: 0x44_avgtdix+476b

Followup: MachineOwner
---------

next one

Code:

oading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {4, 2, 0, 87073d14}

Probably caused by : win32k.sys ( win32k!NtUserGetAncestor+3f )

Followup: MachineOwner
---------

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 87073d14, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 83369718
Unable to read MiSystemVaType memory at 83349160
00000004 

CURRENT_IRQL:  2

FAULTING_IP: 
+62aa2faf02bddbb4
87073d14 0218            add     bl,byte ptr [eax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  iexplore.exe

TRAP_FRAME:  a02afc64 -- (.trap 0xffffffffa02afc64)
ErrCode = 00000000
eax=00000004 ebx=8550b4a8 ecx=00000004 edx=00000000 esi=860e3bb0 edi=860e3bc7
eip=87073d14 esp=a02afcd8 ebp=a02afd0c iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
87073d14 0218            add     bl,byte ptr [eax]          ds:0023:00000004=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 87073d14 to 8324782b

STACK_TEXT:  
a02afc64 87073d14 badb0d00 00000000 a02afc84 nt!KiTrap0E+0x2cf
WARNING: Frame IP not in any known module. Following frames may be wrong.
a02afd0c 8326b7b2 8550b4a8 83289d92 9650ffe4 0x87073d14
a02afd14 83289d92 9650ffe4 06f0d174 a02afd34 nt!ExReleaseResourceLite+0xf
a02afd18 9650ffe4 06f0d174 a02afd34 8324444a nt!ExReleaseResourceAndLeavePriorityRegion+0x5
a02afd24 8324444a 00020428 00000002 06f0d190 win32k!NtUserGetAncestor+0x3f
a02afd24 772664f4 00020428 00000002 06f0d190 nt!KiFastCallEntry+0x12a
06f0d190 00000000 00000000 00000000 00000000 0x772664f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!NtUserGetAncestor+3f
9650ffe4 8bc6            mov     eax,esi

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k!NtUserGetAncestor+3f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdc3f5e

FAILURE_BUCKET_ID:  0xD1_win32k!NtUserGetAncestor+3f

BUCKET_ID:  0xD1_win32k!NtUserGetAncestor+3f

Followup: MachineOwner
---------

next one

Code:

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

IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
Arguments:
Arg1: 8348769f, Address of system function (system call routine)
Arg2: 807d0a02, Current IRQL
Arg3: 00000000, 0
Arg4: 00000000, 0

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


PROCESS_NAME:  iexplore.exe

BUGCHECK_STR:  RAISED_IRQL_FAULT

FAULTING_IP: 
nt!NtDelayExecution+0
8348769f 6a18            push    18h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 778364f4 to 832997b9

STACK_TEXT:  
a38efd34 778364f4 badb0d00 117df8e4 00000000 nt!KiServiceExit2+0x160
WARNING: Frame IP not in any known module. Following frames may be wrong.
117df944 00000000 00000000 00000000 00000000 0x778364f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!NtDelayExecution+0
8348769f 6a18            push    18h

SYMBOL_NAME:  nt!NtDelayExecution+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cacf

FAILURE_BUCKET_ID:  RAISED_IRQL_FAULT_iexplore.exe_nt!NtDelayExecution+0

BUCKET_ID:  RAISED_IRQL_FAULT_iexplore.exe_nt!NtDelayExecution+0

Followup: MachineOwner
---------

the last one inf the list

Code:

0: 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: b2602a64, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 830e563f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 831ad718
Unable to read MiSystemVaType memory at 8318d160
b2602a64 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiLockSetPfnPriority+3e
830e563f f00fba2800      lock bts dword ptr [eax],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  dwm.exe

TRAP_FRAME:  8af54a14 -- (.trap 0xffffffff8af54a14)
ErrCode = 00000003
eax=b2602a64 ebx=00000000 ecx=ffffff02 edx=88a02ea0 esi=b2602a5c edi=b2602a64
eip=830e563f esp=8af54a88 ebp=8af54a94 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MiLockSetPfnPriority+0x3e:
830e563f f00fba2800      lock bts dword ptr [eax],0   ds:0023:b2602a64=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 830e563f to 8308b82b

STACK_TEXT:  
8af54a14 830e563f badb0d00 88a02ea0 80000000 nt!KiTrap0E+0x2cf
8af54a94 830b7645 00000005 88a02ea0 8af54c74 nt!MiLockSetPfnPriority+0x3e
8af54c10 830b861b 88a02ea0 00000001 00000001 nt!MiAgeWorkingSet+0x1f9
8af54c5c 830b82e0 00000002 00000001 00000000 nt!MiProcessWorkingSets+0x25b
8af54c88 830ce21f 00000000 850c0020 00000000 nt!MmWorkingSetManager+0xa4
8af54d50 832536bb 00000000 96f7cc28 00000000 nt!KeBalanceSetManager+0x1af
8af54d90 831050f9 830ce070 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiLockSetPfnPriority+3e
830e563f f00fba2800      lock bts dword ptr [eax],0

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiLockSetPfnPriority+3e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cacf

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiLockSetPfnPriority+3e

BUCKET_ID:  0xA_nt!MiLockSetPfnPriority+3e

Followup: MachineOwner

if we need to look at any more we can do

gzaf · May 13, 2011

so so many thanks for your help kaos!!

Should I try a general driver update, hence? could update to service pack 1 improve anything?
Again thanks to all!!

kaos · May 13, 2011

if u have not got any serivce pack then definatly

install service pack 1 , 2 ,3

im not saying this will fix the issue HOWEVER we can then cross this off the list

kaos · May 13, 2011

also ensure you have up to date

sound drivrs
graphics card
all service packs installed

let me no how it goes

Elmer · May 13, 2011

Hi gzaf and Welcome to the Forum.

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

I reckon your ram timings are out. Should be 5-5-5-15 (333mhz), whereas you have 4-4-4-12 (266mhz).

Your latest dump file lists ntkrpamp.exe as the probable cause. This is a Windows System file and for it to be the cause of your crash is highly unlikely.
Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes.

Outdated Drivers. Update:

CHDRT32.sys Mon Mar 03 20:10:37 2008 Link Removed due to 404 Error

cpqbttn.sys Mon Apr 20 15:38:52 2009 HP Tablet PC Key Button HID Driver / HP Quick Launch Buttons

e1e6232.sys Fri Jun 05 20:07:54 2009 Link Removed

HSX_CNXT.sys Wed Jun 20 19:28:20 2007
HSX_DPV.sys Wed Jun 20 19:29:51 2007
HSXHWAZL.sys Wed Jun 20 19:28:32 2007 SoftK56 Modem Driver by Link Removed due to 404 Error

mdmxsdk.sys Mon Jun 19 22:26:59 2006 Link Removed due to 404 Error Modem Diagnostic Interface x86 Driver

rimmptsk.sys Wed Nov 15 08:16:23 2006
rimsptsk.sys Wed Nov 15 03:42:45 2006
rixdptsk.sys Wed Nov 15 01:35:19 2006 Ricoh Memory Card Reader. Check with your PC or Motherboard Mfr.

SynTP.sys Fri Mar 28 01:14:58 2008 Link Removed due to 404 Error

xaudio.sys Tue Jul 10 22:27:55 2007 Link Removed due to 404 Error modem audio driver.

Drivers:

Code:

908ef000 9091b000   1394ohci 1394ohci.sys Tue Jul 14 00:51:59 2009 (4A5BC89F)
8903d000 89085000   ACPI     ACPI.sys     Tue Jul 14 00:11:11 2009 (4A5BBF0F)
8d0e5000 8d13f000   afd      afd.sys      Tue Jul 14 00:12:34 2009 (4A5BBF62)
901bb000 901cd000   AgileVpn AgileVpn.sys Tue Jul 14 00:55:00 2009 (4A5BC954)
891ab000 891b4000   amdxata  amdxata.sys  Tue May 19 18:57:35 2009 (4A12F30F)
89175000 8917e000   atapi    atapi.sys    Tue Jul 14 00:11:15 2009 (4A5BBF13)
8917e000 891a1000   ataport  ataport.SYS  Tue Jul 14 00:11:18 2009 (4A5BBF16)
9bb56000 9bb75300   AVGIDSDriver AVGIDSDriver.Sys Thu Apr 14 18:10:38 2011 (4DA72A8E)
895a5000 895a8f80   AVGIDSEH AVGIDSEH.Sys Tue Feb 22 05:22:33 2011 (4D634819)
9bb02000 9bb06400   AVGIDSFilter AVGIDSFilter.Sys Thu Feb 10 04:59:07 2011 (4D53709B)
99b65000 99b68b80   AVGIDSShim AVGIDSShim.Sys Thu Feb 10 04:59:09 2011 (4D53709D)
8f22d000 8f268100   avgldx86 avgldx86.sys Fri Jan 07 04:35:29 2011 (4D269811)
89400000 8940c000   avgmfx86 avgmfx86.sys Tue Mar 01 12:23:55 2011 (4D6CE55B)
8959e000 895a4500   avgrkx86 avgrkx86.sys Wed Mar 16 14:05:26 2011 (4D80C3A6)
8d06c000 8d0b2e80   avgtdix  avgtdix.sys  Mon Apr 04 22:53:24 2011 (4D9A3DD4)
890e4000 890ef000   BATTC    BATTC.SYS    Tue Jul 14 00:19:15 2009 (4A5BC0F3)
89200000 89207000   Beep     Beep.SYS     Tue Jul 14 00:45:00 2009 (4A5BC6FC)
8d018000 8d026000   blbdrive blbdrive.sys Tue Jul 14 00:23:04 2009 (4A5BC1D8)
83a8a000 83a92000   BOOTVID  BOOTVID.dll  Tue Jul 14 02:04:34 2009 (4A5BD9A2)
99aa9000 99ac2000   bowser   bowser.sys   Tue Jul 14 00:14:21 2009 (4A5BBFCD)
963b0000 963ce000   cdd      cdd.dll      unavailable (00000000)
895dc000 895fb000   cdrom    cdrom.sys    Tue Jul 14 00:11:24 2009 (4A5BBF1C)
8f86a000 8f89b000   CHDRT32  CHDRT32.sys  Mon Mar 03 20:10:37 2008 (47CC5B3D)
83ad4000 83b7f000   CI       CI.dll       Tue Jul 14 02:09:28 2009 (4A5BDAC8)
89579000 8959e000   CLASSPNP CLASSPNP.SYS Tue Jul 14 00:11:20 2009 (4A5BBF18)
83a92000 83ad4000   CLFS     CLFS.SYS     Tue Jul 14 00:11:10 2009 (4A5BBF0E)
8f29c000 8f29f700   CmBatt   CmBatt.sys   Tue Jul 14 00:19:18 2009 (4A5BC0F6)
89389000 893e6000   cng      cng.sys      Tue Jul 14 00:32:55 2009 (4A5BC427)
890dc000 890e4000   compbatt compbatt.sys Tue Jul 14 00:19:18 2009 (4A5BC0F6)
909ef000 909fc000   CompositeBus CompositeBus.sys Tue Jul 14 00:45:26 2009 (4A5BC716)
909a7000 909a9480   cpqbttn  cpqbttn.sys  Mon Apr 20 15:38:52 2009 (49EC88FC)
90dd6000 90de3000   crashdmp crashdmp.sys Tue Jul 14 00:45:50 2009 (4A5BC72E)
8d000000 8d018000   dfsc     dfsc.sys     Tue Jul 14 00:14:16 2009 (4A5BBFC8)
8d1eb000 8d1f7000   discache discache.sys Tue Jul 14 00:24:04 2009 (4A5BC214)
89568000 89579000   disk     disk.sys     Tue Jul 14 00:11:28 2009 (4A5BBF20)
8f8ca000 8f8e3000   drmk     drmk.sys     Tue Jul 14 01:36:05 2009 (4A5BD2F5)
90de3000 90dee000   dump_dumpata dump_dumpata.sys Tue Jul 14 00:11:16 2009 (4A5BBF14)
90c00000 90c11000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:12:47 2009 (4A5BBF6F)
90dee000 90df8000   dump_msahci dump_msahci.sys Tue Jul 14 00:45:50 2009 (4A5BC72E)
8f921000 8f92b000   Dxapi    Dxapi.sys    Tue Jul 14 00:25:25 2009 (4A5BC265)
8f2a9000 8f360000   dxgkrnl  dxgkrnl.sys  Fri Oct 02 01:48:33 2009 (4AC54DE1)
90163000 9019c000   dxgmms1  dxgmms1.sys  Tue Jul 14 00:25:25 2009 (4A5BC265)
90852000 9088a000   e1e6232  e1e6232.sys  Fri Jun 05 20:07:54 2009 (4A296D0A)
891e8000 891f9000   fileinfo fileinfo.sys Tue Jul 14 00:21:51 2009 (4A5BC18F)
891b4000 891e8000   fltmgr   fltmgr.sys   Tue Jul 14 00:11:13 2009 (4A5BBF11)
893f4000 893fd000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 00:11:14 2009 (4A5BBF12)
89536000 89568000   fvevol   fvevol.sys   Sat Sep 26 03:24:21 2009 (4ABD7B55)
89778000 897a9000   fwpkclnt fwpkclnt.sys Tue Jul 14 00:12:03 2009 (4A5BBF43)
909e9000 909ee280   GEARAspiWDM GEARAspiWDM.sys Mon May 18 13:16:53 2009 (4A1151B5)
8382c000 83863000   hal      halmacpi.dll Tue Jul 14 00:11:03 2009 (4A5BBF07)
9019c000 901bb000   HDAudBus HDAudBus.sys Tue Jul 14 00:50:55 2009 (4A5BC85F)
909aa000 909bd000   HIDCLASS HIDCLASS.SYS Tue Jul 14 00:51:01 2009 (4A5BC865)
909bd000 909c3480   HIDPARSE HIDPARSE.SYS Tue Jul 14 00:50:59 2009 (4A5BC863)
90d14000 90dc9000   HSX_CNXT HSX_CNXT.sys Wed Jun 20 19:28:20 2007 (467971C4)
90c11000 90d14000   HSX_DPV  HSX_DPV.sys  Wed Jun 20 19:29:51 2007 (4679721F)
8f8e3000 8f921000   HSXHWAZL HSXHWAZL.sys Wed Jun 20 19:28:32 2007 (467971D0)
99a24000 99aa9000   HTTP     HTTP.sys     Tue Jul 14 00:12:53 2009 (4A5BBF75)
8952e000 89536000   hwpolicy hwpolicy.sys Tue Jul 14 00:11:01 2009 (4A5BBF05)
909c4000 909dc000   i8042prt i8042prt.sys Tue Jul 14 00:11:23 2009 (4A5BBF1B)
8914a000 89151000   intelide intelide.sys Tue Jul 14 00:11:19 2009 (4A5BBF17)
8f28a000 8f29c000   intelppm intelppm.sys Tue Jul 14 00:11:03 2009 (4A5BBF07)
909dc000 909e9000   kbdclass kbdclass.sys Tue Jul 14 00:11:15 2009 (4A5BBF13)
8f84d000 8f859000   kbdhid   kbdhid.sys   Tue Jul 14 00:45:09 2009 (4A5BC705)
80bbc000 80bc4000   kdcom    kdcom.dll    Tue Jul 14 02:08:58 2009 (4A5BDAAA)
8f3a6000 8f3da000   ks       ks.sys       Tue Jul 14 00:45:13 2009 (4A5BC709)
89376000 89389000   ksecdd   ksecdd.sys   Tue Jul 14 00:11:56 2009 (4A5BBF3C)
89509000 8952e000   ksecpkg  ksecpkg.sys  Fri Dec 11 04:04:22 2009 (4B21C4C6)
8f96b000 8f97b000   lltdio   lltdio.sys   Tue Jul 14 00:53:18 2009 (4A5BC8EE)
8f936000 8f951000   luafv    luafv.sys    Tue Jul 14 00:15:44 2009 (4A5BC020)
9bbc7000 9bbcba80   LVPr2Mon LVPr2Mon.sys Sat May 08 02:36:25 2010 (4BE4C019)
83a01000 83a79000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 02:06:41 2009 (4A5BDA21)
99b69000 99b6c180   mdmxsdk  mdmxsdk.sys  Mon Jun 19 22:26:59 2006 (449716A3)
90dc9000 90dd6000   modem    modem.sys    Tue Jul 14 00:55:24 2009 (4A5BC96C)
8f92b000 8f936000   monitor  monitor.sys  Tue Jul 14 00:25:58 2009 (4A5BC286)
90432000 9043f000   mouclass mouclass.sys Tue Jul 14 00:11:15 2009 (4A5BBF13)
8915f000 89175000   mountmgr mountmgr.sys Tue Jul 14 00:11:27 2009 (4A5BBF1F)
99ac2000 99ad4000   mpsdrv   mpsdrv.sys   Tue Jul 14 00:52:52 2009 (4A5BC8D4)
99ad4000 99af7000   mrxsmb   mrxsmb.sys   Sat Feb 27 07:32:02 2010 (4B88CA72)
99af7000 99b32000   mrxsmb10 mrxsmb10.sys Sat Feb 27 07:32:21 2010 (4B88CA85)
99b32000 99b4d000   mrxsmb20 mrxsmb20.sys Sat Feb 27 07:32:11 2010 (4B88CA7B)
891a1000 891ab000   msahci   msahci.sys   Tue Jul 14 00:45:50 2009 (4A5BC72E)
8d031000 8d03c000   Msfs     Msfs.SYS     Tue Jul 14 00:11:26 2009 (4A5BBF1E)
8908e000 89096000   msisadrv msisadrv.sys Tue Jul 14 00:11:09 2009 (4A5BBF0D)
8934b000 89376000   msrpc    msrpc.sys    Tue Jul 14 00:11:59 2009 (4A5BBF3F)
8d1e1000 8d1eb000   mssmbios mssmbios.sys Tue Jul 14 00:19:25 2009 (4A5BC0FD)
897f0000 89800000   mup      mup.sys      Tue Jul 14 00:14:14 2009 (4A5BBFC6)
89414000 894cb000   ndis     ndis.sys     Tue Jul 14 00:12:24 2009 (4A5BBF58)
901e5000 901f0000   ndistapi ndistapi.sys Tue Jul 14 00:54:24 2009 (4A5BC930)
8f9c1000 8f9d1000   ndisuio  ndisuio.sys  Tue Jul 14 00:53:51 2009 (4A5BC90F)
8fa00000 8fa22000   ndiswan  ndiswan.sys  Tue Jul 14 00:54:34 2009 (4A5BC93A)
8f859000 8f86a000   NDProxy  NDProxy.SYS  Tue Jul 14 00:54:27 2009 (4A5BC933)
8d165000 8d173000   netbios  netbios.sys  Tue Jul 14 00:53:54 2009 (4A5BC912)
8d0b3000 8d0e5000   netbt    netbt.sys    Tue Jul 14 00:12:18 2009 (4A5BBF52)
894cb000 89509000   NETIO    NETIO.SYS    Tue Jul 14 00:12:35 2009 (4A5BBF63)
9043f000 90852000   netw5v32 netw5v32.sys Thu Mar 26 16:10:37 2009 (49CBA8FD)
8d03c000 8d04a000   Npfs     Npfs.SYS     Tue Jul 14 00:11:31 2009 (4A5BBF23)
8d1d7000 8d1e1000   nsiproxy nsiproxy.sys Tue Jul 14 00:12:08 2009 (4A5BBF48)
8341c000 8382c000   nt       ntkrpamp.exe Sat Feb 27 07:33:35 2010 (4B88CACF)
8921c000 8934b000   Ntfs     Ntfs.sys     Tue Jul 14 00:12:05 2009 (4A5BBF45)
8940c000 89413000   Null     Null.SYS     Tue Jul 14 00:11:12 2009 (4A5BBF10)
8fa30000 90162100   nvlddmkm nvlddmkm.sys Fri Mar 06 12:47:34 2009 (49B11B66)
8f97b000 8f9c1000   nwifi    nwifi.sys    Tue Jul 14 00:51:59 2009 (4A5BC89F)
8d146000 8d165000   pacer    pacer.sys    Tue Jul 14 00:53:58 2009 (4A5BC916)
890cb000 890dc000   partmgr  partmgr.sys  Tue Jul 14 00:11:35 2009 (4A5BBF27)
89096000 890c0000   pci      pci.sys      Tue Jul 14 00:11:16 2009 (4A5BBF14)
89151000 8915f000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 00:11:15 2009 (4A5BBF13)
893e6000 893f4000   pcw      pcw.sys      Tue Jul 14 00:11:10 2009 (4A5BBF0E)
9ba2b000 9bac2000   peauth   peauth.sys   Tue Jul 14 01:35:44 2009 (4A5BD2E0)
8f89b000 8f8ca000   portcls  portcls.sys  Tue Jul 14 00:51:00 2009 (4A5BC864)
83a79000 83a8a000   PSHED    PSHED.dll    Tue Jul 14 02:09:36 2009 (4A5BDAD0)
901cd000 901e5000   rasl2tp  rasl2tp.sys  Tue Jul 14 00:54:33 2009 (4A5BC939)
8f360000 8f378000   raspppoe raspppoe.sys Tue Jul 14 00:54:53 2009 (4A5BC94D)
8f378000 8f38f000   raspptp  raspptp.sys  Tue Jul 14 00:54:47 2009 (4A5BC947)
8f38f000 8f3a6000   rassstp  rassstp.sys  Tue Jul 14 00:54:57 2009 (4A5BC951)
8d196000 8d1d7000   rdbss    rdbss.sys    Tue Jul 14 00:14:26 2009 (4A5BBFD2)
89213000 8921b000   RDPCDD   RDPCDD.sys   Tue Jul 14 01:01:40 2009 (4A5BCAE4)
8902e000 89036000   rdpencdd rdpencdd.sys Tue Jul 14 01:01:39 2009 (4A5BCAE3)
8d029000 8d031000   rdprefmp rdprefmp.sys Tue Jul 14 01:01:41 2009 (4A5BCAE5)
89600000 8962d000   rdyboost rdyboost.sys Tue Jul 14 00:22:02 2009 (4A5BC19A)
90934000 90942000   rimmptsk rimmptsk.sys Wed Nov 15 08:16:23 2006 (455ACCD7)
90942000 90956000   rimsptsk rimsptsk.sys Wed Nov 15 03:42:45 2006 (455A8CB5)
90956000 909a7000   rixdptsk rixdptsk.sys Wed Nov 15 01:35:19 2006 (455A6ED7)
8f9d1000 8f9e4000   rspndr   rspndr.sys   Tue Jul 14 00:53:20 2009 (4A5BC8F0)
9091b000 90934000   sdbus    sdbus.sys    Sat Oct 10 03:31:24 2009 (4ACFF1FC)
9bac2000 9bacc000   secdrv   secdrv.SYS   Wed Sep 13 14:18:32 2006 (45080528)
897e8000 897f0000   spldr    spldr.sys    Mon May 11 17:13:47 2009 (4A084EBB)
9bb76000 9bbc7000   srv      srv.sys      Tue Dec 08 08:05:37 2009 (4B1E08D1)
9bb07000 9bb56000   srv2     srv2.sys     Tue Jul 14 00:14:52 2009 (4A5BBFEC)
9bacc000 9baed000   srvnet   srvnet.sys   Tue Dec 08 08:05:06 2009 (4B1E08B2)
909fc000 909fd380   swenum   swenum.sys   Tue Jul 14 00:45:08 2009 (4A5BC704)
90400000 9042f100   SynTP    SynTP.sys    Fri Mar 28 01:14:58 2008 (47EC4692)
8962f000 89778000   tcpip    tcpip.sys    Tue Jul 14 00:13:18 2009 (4A5BBF8E)
9baed000 9bafa000   tcpipreg tcpipreg.sys Tue Jul 14 00:54:14 2009 (4A5BC926)
8d061000 8d06c000   TDI      TDI.SYS      Tue Jul 14 00:12:12 2009 (4A5BBF4C)
8d04a000 8d061000   tdx      tdx.sys      Tue Jul 14 00:12:10 2009 (4A5BBF4A)
8d186000 8d196000   termdd   termdd.sys   Tue Jul 14 01:01:35 2009 (4A5BCADF)
96380000 96389000   TSDDD    TSDDD.dll    unavailable (00000000)
8f269000 8f28a000   tunnel   tunnel.sys   Tue Jul 14 00:54:03 2009 (4A5BC91B)
8fa22000 8fa30000   umbus    umbus.sys    Tue Jul 14 00:51:38 2009 (4A5BC88A)
90430000 90431700   USBD     USBD.SYS     Tue Jul 14 00:51:05 2009 (4A5BC869)
908e0000 908ef000   usbehci  usbehci.sys  Tue Jul 14 00:51:14 2009 (4A5BC872)
8f809000 8f84d000   usbhub   usbhub.sys   Tue Jul 14 00:52:06 2009 (4A5BC8A6)
90895000 908e0000   USBPORT  USBPORT.SYS  Tue Jul 14 00:51:13 2009 (4A5BC871)
9088a000 90895000   usbuhci  usbuhci.sys  Tue Jul 14 00:51:10 2009 (4A5BC86E)
890c0000 890cb000   vdrvroot vdrvroot.sys Tue Jul 14 00:46:19 2009 (4A5BC74B)
89207000 89213000   vga      vga.sys      Tue Jul 14 00:25:50 2009 (4A5BC27E)
89000000 89021000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 00:25:49 2009 (4A5BC27D)
890ef000 890ff000   volmgr   volmgr.sys   Tue Jul 14 00:11:25 2009 (4A5BBF1D)
890ff000 8914a000   volmgrx  volmgrx.sys  unavailable (00000000)
897a9000 897e8000   volsnap  volsnap.sys  Tue Jul 14 00:11:34 2009 (4A5BBF26)
8d173000 8d186000   wanarp   wanarp.sys   Tue Jul 14 00:55:02 2009 (4A5BC956)
89021000 8902e000   watchdog watchdog.sys Tue Jul 14 00:24:10 2009 (4A5BC21A)
83b7f000 83bf0000   Wdf01000 Wdf01000.sys Tue Jul 14 00:11:36 2009 (4A5BBF28)
83bf0000 83bfe000   WDFLDR   WDFLDR.SYS   Tue Jul 14 00:11:25 2009 (4A5BBF1D)
8d13f000 8d146000   wfplwf   wfplwf.sys   Tue Jul 14 00:53:51 2009 (4A5BC90F)
96120000 9636a000   win32k   win32k.sys   unavailable (00000000)
8f2a0000 8f2a9000   wmiacpi  wmiacpi.sys  Tue Jul 14 00:19:16 2009 (4A5BC0F4)
89085000 8908e000   WMILIB   WMILIB.SYS   Tue Jul 14 00:11:22 2009 (4A5BBF1A)
8f951000 8f96b000   WudfPf   WudfPf.sys   Tue Jul 14 00:50:13 2009 (4A5BC835)
9bafa000 9bb02000   xaudio   xaudio.sys   Tue Jul 10 22:27:55 2007 (4693F9DB)

Unloaded modules:
9bbcc000 9bbd4000   ALSysIO.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00008000
99b4d000 99b65000   parport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00018000
895a9000 895b6000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
895b6000 895c1000   dump_pciidex
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
895c1000 895cb000   dump_msahci.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000A000
895cb000 895dc000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000

If bluescreens continue:
AVG is known to be a cause of BSOD's on Windows 7 systems. Suggest that you uninstall it. Download the correct Link Removed for your system (32 or 64 bit).
If you have AVG ID protection installed, download the AVGID Protection Remover from the above link as well (it wouldn't hurt to download and run it anyway). Download Link Removed due to 404 Error as AVG's replacement. Re-boot to Safe Mode. In Safe Mode run the AVG Removal tools. Re-boot to normal mode and install MSE. Make sure your Windows firewall is enabled!

Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.

HTH.

Windows 7 Frequent BSOsD on hp pavilion, help please!!

gzaf

New Member

Attachments

msfanboy98

kaos

Senior Member

kaos

Senior Member

kaos

Senior Member

msfanboy98

New Member

kaos

Senior Member

gzaf

New Member

kaos

Senior Member

kaos

Senior Member

Elmer

Extraordinary Member

Similar threads