Hi there...
My system is Windows Seven Ultimate 32Bit OEM on an Acer Aspire 6935G laptop a year and half old (the OS is 6 months)
BSOD occured throughout this week almost on a daily basis with multiple times today..I feel it has something to do with me downloading using internet work after using hotspotshield as a proxy but anyhow..the files are attached ,plz take a look and help me out..thnx
Virtually all of these were caused by your HsDrv.sys (part of hotspot shield. I would remove it if I were you.
Also you have drivers from as far back as 2002. They need updating.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\111310-26301-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8323e000 PsLoadedModuleList = 0x83386810
Debug session time: Sat Nov 13 11:54:48.310 2010 (GMT-5)
System Uptime: 0 days 0:50:33.980
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {5b7aa8a7, 2, 1, 9234e585}
Unable to load image \SystemRoot\system32\DRIVERS\HssDrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for HssDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for HssDrv.sys
Probably caused by : HssDrv.sys ( HssDrv+4585 )
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: 5b7aa8a7, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 9234e585, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 833a6718
Unable to read MiSystemVaType memory at 83386160
5b7aa8a7
CURRENT_IRQL: 2
FAULTING_IP:
HssDrv+4585
9234e585 897804 mov dword ptr [eax+4],edi
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: 8336451c -- (.trap 0xffffffff8336451c)
ErrCode = 00000002
eax=5b7aa8a3 ebx=00000780 ecx=00000000 edx=878651c0 esi=92356200 edi=92356200
eip=9234e585 esp=83364590 ebp=8336459c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
HssDrv+0x4585:
9234e585 897804 mov dword ptr [eax+4],edi ds:0023:5b7aa8a7=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 9234e585 to 832847eb
STACK_TEXT:
8336451c 9234e585 badb0d00 878651c0 8a1731f8 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
8336459c 9234dddd 878651d4 85cd43e4 85cd43e4 HssDrv+0x4585
833645cc 9234b22b 00000042 8750af4c 00000000 HssDrv+0x3ddd
833645f8 9234b482 8750af4c 85cd43e4 00000082 HssDrv+0x122b
83364618 8bca84e5 87d991e0 83364660 00000001 HssDrv+0x1482
83364640 8bca830a 83364664 83364660 00000001 ndis!ndisMSendPacketsXToMiniport+0x142
833646a8 8bc4059d 878660e0 8612a8f0 00000000 ndis!ndisMSendNetBufferListsToPackets+0x84
833646c8 8bc40623 8612a8f0 8612a8f0 00000000 ndis!ndisFilterSendNetBufferLists+0x87
833646e0 904f9c20 88213058 8612a8f0 00000000 ndis!NdisFSendNetBufferLists+0x38
8336475c 8bc40474 859d5410 8612a8f0 00000000 pacer!PcFilterSendNetBufferLists+0x256
83364788 8bca4d8c 878660e0 8612a8f0 00000000 ndis!ndisSendNBLToFilter+0xf2
833647b8 8be9a03e 88fddaa8 8612a8f0 00000000 ndis!NdisSendNetBufferLists+0x162
83364804 8be9a7c1 88fdb278 00000000 00000000 tcpip!FlSendPackets+0x416
83364858 8be9a4d3 8bf1ad98 00000000 00000000 tcpip!IppFragmentPackets+0x2e2
83364890 8bea2273 8bf1ad98 87149d5c 87149df8 tcpip!IppDispatchSendPacketHelper+0x266
83364930 8bea830e 00149d5c 00000000 859815b0 tcpip!IppPacketizeDatagrams+0x8d6
833649b0 8bea8595 00000000 00000007 8bf1ad98 tcpip!IppSendDatagramsCommon+0x652
833649d0 8be891a0 8714fed8 833649ec 00000000 tcpip!IpNlpSendDatagrams+0x4b
83364aa0 8beb5151 891f9190 00000000 00000002 tcpip!TcpTcbHeaderSend+0x53a
83364aec 8beb4c42 00000000 83364bac 00000000 tcpip!TcpFlushDelay+0x257
83364b38 832a804d 8713ed38 00000000 7b39ecb1 tcpip!TcpPeriodicTimeoutHandler+0x389
83364b7c 832a7ff1 83367d20 83364ca8 00000001 nt!KiProcessTimerDpcTable+0x50
83364c68 832a7eae 83367d20 83364ca8 00000000 nt!KiProcessExpiredTimerList+0x101
83364cdc 832a620e 0002f7b4 861674c0 83371280 nt!KiTimerExpiration+0x25c
83364d20 832a6038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
83364d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
HssDrv+4585
9234e585 897804 mov dword ptr [eax+4],edi
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: HssDrv+4585
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HssDrv
IMAGE_NAME: HssDrv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 498b603e
FAILURE_BUCKET_ID: 0xD1_HssDrv+4585
BUCKET_ID: 0xD1_HssDrv+4585
Followup: MachineOwner
---------
Old Drivers
Code:
int15.sys 0x963fa000 0x00011000 10/1/2003 00:29:49 0x3f7a664d 0x963e9000
DPortIO.sys 0x91f1d380 0x00003380 12/23/2005 03:13:04 0x43abb190 0x91f1a000
lirsgt.sys 0x963fe680 0x00004680 1/29/2006 06:06:18 0x43dca1aa 0x963fa000
snapman.sys 0x8be22260 0x0001a260 10/6/2006 08:44:30 0x45265dbe 0x8be08000
DKbFltr.sys 0x93067000 0x0000a000 10/19/2006 03:24:28 0x4537363c 0x9305d000
tapvpn.sys 0x92c22000 0x0000b000 10/26/2006 03:42:32 0x454074f8 0x92c17000
dsNcAdpt.sys 0x9315a000 0x0000a000 2/1/2007 15:00:43 0x45c246eb 0x93150000
itecir.sys 0x9310a000 0x00058000 12/18/2007 04:12:11 0x47678eeb 0x930b2000
SynTP.sys 0x930a2680 0x0002e680 4/4/2008 18:44:51 0x47f6bd73 0x93074000
iaStor.sys 0x8b96a000 0x000d9000 7/20/2008 19:15:55 0x4883d53b 0x8b891000
dump_iaStor.sys 0x916d9000 0x000d9000 7/20/2008 19:15:55 0x4883d53b 0x91600000
AGRSM.sys 0x927dc000 0x00106000 11/10/2008 09:56:37 0x49184ba5 0x926d6000
HssDrv.sys HssDrv.sys+4585 0x9317c000 0x00010000 2/5/2009 16:55:10 0x498b603e 0x9316c000
hamachi.sys 0x92c2dc00 0x00004c00 2/19/2009 05:36:27 0x499d362b 0x92c29000
netw5v32.sys 0x93045000 0x00413000 3/26/2009 11:10:37 0x49cba8fd 0x92c32000
spldr.sys 0x8be08000 0x00008000 5/11/2009 11:13:47 0x4a084ebb 0x8be00000
amdxata.sys 0x8b973000 0x00009000 5/19/2009 12:57:35 0x4a12f30f 0x8b96a000
L1E62x86.sys 0xa6980000 0x0000f000 6/11/2009 01:39:12 0x4a30a690 0xa6971000
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
Quote