Solved BSOD occurs only during runescape

[SsGComMandO]

I have windows 7 ultimate 64 bit. BSOD mostly occurs when I am busy in runescape. this problem is not so new. I had BSOD, but mostly during runescape whether I am playing game through any browser or using runescape client. But today BSOD occurred 3 times during that game.
I am giving some additional information that I don't have any service pack installed as i cant install sp1 ( during installation error occurs)
I will provide more information if i am missing something

 

[SsGComMandO]

Here is my SF attachment that i just run after reboot from BSOD

 

[z3r010]

The dumps are blaming zone alarm - vsdatant.sys Driver Reference Table - vsdatant.sys

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 0, fffff88004180b72}

*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : vsdatant.sys ( vsdatant+16b72 )

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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004180b72, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fa0e0
GetUlongFromAddress: unable to read from fffff800032fa198
 0000000000000008 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
vsdatant+16b72
fffff880`04180b72 488b5908        mov     rbx,qword ptr [rcx+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880031cab00 -- (.trap 0xfffff880031cab00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880031cad28 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004180b72 rsp=fffff880031cac90 rbp=fffff880041ce110
 r8=fffff880031cae48  r9=0000000000000008 r10=000000000000ff00
r11=fffff880031cad78 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
vsdatant+0x16b72:
fffff880`04180b72 488b5908        mov     rbx,qword ptr [rcx+8] ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030c2b29 to fffff800030c35c0

STACK_TEXT:  
fffff880`031ca9b8 fffff800`030c2b29 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031ca9c0 fffff800`030c17a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031cab00 fffff880`04180b72 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`031cac90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vsdatant+0x16b72


STACK_COMMAND:  kb

FOLLOWUP_IP: 
vsdatant+16b72
fffff880`04180b72 488b5908        mov     rbx,qword ptr [rcx+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  vsdatant+16b72

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vsdatant

IMAGE_NAME:  vsdatant.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dc387a2

FAILURE_BUCKET_ID:  X64_0xD1_vsdatant+16b72

BUCKET_ID:  X64_0xD1_vsdatant+16b72

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

 

[SsGComMandO]

OK now i am uninstalling my zone alarm and will post here that what happens next.

 

[SsGComMandO]

after uninstallation I have not face BSOD yet.
@z3r010 how can I select your post as an answer?

 

[z3r010]

You can just click the green solved button if all is good

 

[SsGComMandO]

@z3r010 Thanks very much man. You did a great hob. Can you tell me how did u retrieve that specific information from my attachment?
Thanks very much again

 

[z3r010]

All the info you need to do it yourself is here - http://www.sevenforums.com/crash-lockup-debug-how/221485-bsod-analysis-getting-started.html