Jump to content
danci1973

Blue Screen Of Death (Bsod) While Installing Immunet Plus

Recommended Posts

Hi,

 

after using AVG Free and Avira for a while I decided to try Immunet Plus.

 

However the installation failed with a BSOD. After rebooting the machine the BSOD re-appeared while XP was loading (actually - it was a Green-ish Screen Of Death):

 

post-13963-050513100 1335558925_thumb.jpg

 

I was able to boot into safe mode, but Immunet has not yet been completely installed, so I started the installation again (while in safe mode) and it completed. However, booting in normal mode still didn't work (same BSOD), so it was back to safe mode to uninstall.

 

Now the machine works (without AV).

 

Running Windows XP Professional Version 2002 Service Pack 3 (32bit, English) on an Intel Core2 Quad Q6600 with 2GB of memory.

 

If you need more info I'd be happy to help.

 

D.

Share this post


Link to post
Share on other sites

Could you please follow these instructions and send the support dump to us for analysis:

 

1. Go to Start Menu at the bottom left of your screen - and All Programs -> Immunet 3.0 -> Support Diagnostics Tool.

2. This will create a new file on your desktop with a name like Immunet_Support_Tool_[date and timestamp].7z

3. Email the support dump to support@immunet.com.

 

We will investigate this problem for you.

 

Thank you danci1973 for reporting this issue.

Share this post


Link to post
Share on other sites

Good morning,

 

here's what I did:

 

1. installed Immunet Plus (trial) in 'Safe Mode with Networking'

2. rebooted into 'normal mode' resulting in BSOD

3. rebooted back into 'Safe Mode with Networking'

4. ran the 'Support Diagnostics Tool'

5. sent the resulting ZIP file to support@immunet.com

 

Hopefully this will do.

 

Danilo

Share this post


Link to post
Share on other sites

Getting a blue screen also with 3.0.8. Here is the dump file analysis. Hope this helps:

 

 

 

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [i:\__Common\0000\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is available

 

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp_sp3_gdr.120504-1619

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Sun Sep 23 15:41:50.510 2012 (UTC - 4:00)

System Uptime: 0 days 12:28:13.598

Loading Kernel Symbols

...............................................................

................................................................

............

Loading User Symbols

 

Loading unloaded module list

..........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

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

 

*** ERROR: Module load completed but symbols could not be loaded for ImmunetNetworkMonitor.sys

Probably caused by : ImmunetNetworkMonitor.sys ( ImmunetNetworkMonitor+3592 )

 

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: 00000000, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000008, value 0 = read operation, 1 = write operation

Arg4: 00000000, address which referenced memory

 

Debugging Details:

------------------

 

 

READ_ADDRESS: 00000000

 

CURRENT_IRQL: 2

 

FAULTING_IP:

+6330346262616161

00000000 ?? ???

 

PROCESS_NAME: System

 

DEFAULT_BUCKET_ID: DRIVER_FAULT

 

BUGCHECK_STR: 0xD1

 

TRAP_FRAME: ba4f7950 -- (.trap 0xffffffffba4f7950)

ErrCode = 00000010

eax=00000041 ebx=00000000 ecx=00000041 edx=88d53502 esi=89000184 edi=89000068

eip=00000000 esp=ba4f79c4 ebp=ba4f7a2c iopl=0 nv up ei pl zr na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

00000000 ?? ???

Resetting default scope

 

LAST_CONTROL_TRANSFER: from 00000000 to 80544768

 

FAILED_INSTRUCTION_ADDRESS:

+6330346262616161

00000000 ?? ???

 

STACK_TEXT:

ba4f7950 00000000 badb0d00 88d53502 000a1221 nt!KiTrap0E+0x238

WARNING: Frame IP not in any known module. Following frames may be wrong.

ba4f79c0 b43eb592 00000000 00000016 ba4f7aac 0x0

ba4f7a2c b6fac86c 89000068 00000016 ba4f7aac ImmunetNetworkMonitor+0x3592

ba4f7ac8 b6fb6d35 89ee8d08 0100007f 00008806 tcpip!UDPDeliver+0x1be

ba4f7b20 b6fabef5 8a22b2e0 0100007f 0100007f tcpip!UDPRcv+0x164

ba4f7b80 b6fabb19 00000020 8a22b2e0 b6fac592 tcpip!DeliverToUser+0x18e

ba4f7bfc b6fab836 b6feb8f0 8a22b2e0 ba4f7d18 tcpip!DeliverToUserEx+0x95e

ba4f7cb4 b6fb7ce6 8a22b2e0 ba4f7d2c 00000009 tcpip!IPRcvPacket+0x6cb

ba4f7d60 ba4303e4 b6feb680 8a22b2e0 b6feb690 tcpip!LoopXmitRtn+0x195

ba4f7d7c 805387d9 8a22b2e0 00000000 8a584b20 TDI!CTEpEventHandler+0x32

ba4f7dac 805cffbe b6feb680 00000000 00000000 nt!ExpWorkerThread+0xef

ba4f7ddc 8054616e 805386ea 00000001 00000000 nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

ImmunetNetworkMonitor+3592

b43eb592 eb23 jmp ImmunetNetworkMonitor+0x35b7 (b43eb5b7)

 

SYMBOL_STACK_INDEX: 2

 

SYMBOL_NAME: ImmunetNetworkMonitor+3592

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: ImmunetNetworkMonitor

 

IMAGE_NAME: ImmunetNetworkMonitor.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 50468332

 

FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_ImmunetNetworkMonitor+3592

 

BUCKET_ID: 0xD1_CODE_AV_NULL_IP_ImmunetNetworkMonitor+3592

 

Followup: MachineOwner

---------

Share this post


Link to post
Share on other sites

I installed an update of the free version last week on an XP SP3 machine I normally use remotely (via Remote Desktop) and made the mistake of leaving before the reboot had finished. It got a blue screen with "no more IRP stack locations". An on-site user was able to boot the machine into safe mode. Googling reveals that this error has happened with other AV products such as Norton. I'll be going by today to uninstall from safe mode and re-attempt the installation.

 

Some interesting info here on what the error message means:

 

http://answers.microsoft.com/en-us/windows/forum/windows_vista-system/how-to-fix-error-0x00000035-no-more-irp-stack/9367bcca-8a4f-e011-8dfc-68b599b31bf5?msgId=a9afa4db-5906-4eb3-8db4-414dcafd2081

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...