Prime95 24.14 & NORTON360

Daffy · 2007-10-18, 06:13

I have been running 2 copies of prime95 version 24.14 on a new PC (Abit IP35 Pro, intel 6750, eVGA 8600 GT, 2GB DDR2-666). I noticed from the beginning that there were random BSOD with code 0xD1, on SYMNDIS.SYS (Norton360) and the process name is shown as Prime95. I have no idea if these 2 are linked or not.

I ran hours of memory tests, no issue. I have all the latest BIOS / drivers, etc... Both copies of Prime95 are running in 2 different directories, no error reported there. The PC is running at 60C for each core, no overclocking at this time, all the power supplies are slightly higher than default to be sure.

The PC could be stable for 2 days without crashing. It could also crash after a couple of hours. Always the same error code, the same driver and Prime95 in the background.

Has anyone noticed anything similar to this ? The norton support is helpless at this point and I am considering dropping Norton to McAfee, hoping it would behave better.

This is the memory dump, if this talks to anyone. I've been using Prime95 + Norton Security on a previous PC with no issue for years so I wonder what's going on here. New PC problem or norton360 problem / related to prime95 ?

Thanks...

1: 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: 00000010, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: babb8588, address which referenced memory

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

WRITE_ADDRESS: 00000010

CURRENT_IRQL: 2

FAULTING_IP:
SYMNDIS+588
babb8588 834010ff add dword ptr [eax+10h],0FFFFFFFFh

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Prime95.exe

LAST_CONTROL_TRANSFER: from babb895d to babb8588

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacdf230 babb895d 00000000 00000002 00000000 SYMNDIS+0x588
bacdf248 b43cdc67 89824b68 00000000 bacdf6c4 SYMNDIS+0x95d
bacdf260 b43ce502 bacdf6c4 bacdf744 bacdf75c SYMFW+0xec67
bacdf45c b43c3910 000000c8 bacdf744 88392990 SYMFW+0xf502
bacdf638 babb87bf bacdf7dc bacdf789 00000001 SYMFW+0x4910
bacdf668 babb8cf0 bacdf7dc bacdf744 bacdf6c4 SYMNDIS+0x7bf
bacdf724 babba87d bacdf73c 890ca2e0 00000000 SYMNDIS+0xcf0
bacdf808 b4bd0a8d bacdf878 00000003 bacdf84c SYMNDIS+0x287d
bacdf87c b4bd0836 890d6a18 890ca2e0 8963f5fe tcpip!DeliverToUserEx+0x7e6
bacdf934 b4bcf922 890ca2e0 8963f612 00000124 tcpip!IPRcvPacket+0x6cb
bacdf974 b4bcf84d 00000001 882ce058 8963f5f0 tcpip!ARPRcvIndicationNew+0x149
bacdf9b0 b20419eb 899f7ab8 00000000 897a2130 tcpip!ARPRcvPacket+0x68
bacdfa1c b959601d 002c2cf8 89ad3ba0 00000001 vsdatant+0x119eb
bacdfa30 b95961b4 897a2130 89ad3ba0 00000001 psched!PsFlushReceiveQueue+0x15
bacdfa54 b95965f9 8983ac58 00000000 897a2130 psched!PsEnqueueReceivePacket+0xda
bacdfa6c ba612d40 8983ac50 882ce0ac 8972a868 psched!ClReceiveComplete+0x13
bacdfabc b960aa26 002c2cf8 bacdfafc 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
bacdfaf4 b20419eb 882ce058 88307c18 89bc4130 dne2000+0x7a26
bacdfb60 b9646809 0088fa88 bacdfd80 00000001 vsdatant+0x119eb
bacdff9c b964939e 8970e000 89bc4130 00000000 Rtnicxp+0x5809
bacdffb4 ba608f09 8970e000 89848e18 bab389c0 Rtnicxp+0x839e
bacdffcc 805450bf 8970e244 8970e230 00000000 NDIS!ndisMDpcX+0x21
bacdfff4 80544c2b b2ad6d44 00000000 00000000 nt!KiRetireDpcList+0x61
bacdfff8 b2ad6d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
80544c2b 00000000 00000009 0081850f bb830000 0xb2ad6d44

STACK_COMMAND: kb

FOLLOWUP_IP:
SYMNDIS+588
babb8588 834010ff add dword ptr [eax+10h],0FFFFFFFFh

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: SYMNDIS

IMAGE_NAME: SYMNDIS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 45a2fea3

SYMBOL_NAME: SYMNDIS+588

FAILURE_BUCKET_ID: 0xD1_W_SYMNDIS+588

BUCKET_ID: 0xD1_W_SYMNDIS+588

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

Cruelty · 2007-10-18, 08:53

Go for Kaspersky rather than Norton / McAfee

I have made such a switch ~3 years ago and I can recommend KIS.
Anyways I have seen similar behaviour after updating Windows XP with some patches that were supposed to increase system stability...

Daffy · 2007-10-18, 20:10

I am not really considering switching to Kaspersky (no trust). I'll try McAfee first, since we use it at work reliably.

This issue has been there from day 1 (about a month), as soon as I installed Norton360. It's always the same message and seeing in the debug file Prime95 as the process name, I was wondering if it had anything to do with the issue.

I have 2 directories for prime95 and I run them both from each directory. Is there any issue with that ? Each core is running one instance and it looks OK. No error from Prime95 itself. Just this random BSOD with SYMNDIS. And I searched the WEB and I can't find anything related to it.

If I can't get an answer, I will uninstall it and run this PC out of the network for a while to see what happens. Then, McAfee.

PS: Forgot to mention: I am trying now to run a single instance of prime95 and see what happens, in case this is related to 2 instances running.

typo_pl · 2007-10-18, 20:35

From my rusty kernel debugging skills, just looking at the callstack, it looks like Norton crashed while looking at a network packet the machine got.

Try running without the net hooked up (after you got exponents assigned to your Prime95 instances) to see if that is the problem.

Daffy · 2007-10-19, 02:25

It crashed again, with 1 instance of prime95 and this time, it says that the process name is Idle. So, prime95 has nothing to do with this. I will try running the PC out of the network with norton and then, without it, if it happens again. Norton, you are about to lose a customer...

Thanks for the help!

paulunderwood · 2007-10-19, 06:02

Try Norton500

2007-10-18, 06:13	#1
Daffy Aug 2002 1F₁₆ Posts	Prime95 24.14 & NORTON360 I have been running 2 copies of prime95 version 24.14 on a new PC (Abit IP35 Pro, intel 6750, eVGA 8600 GT, 2GB DDR2-666). I noticed from the beginning that there were random BSOD with code 0xD1, on SYMNDIS.SYS (Norton360) and the process name is shown as Prime95. I have no idea if these 2 are linked or not. I ran hours of memory tests, no issue. I have all the latest BIOS / drivers, etc... Both copies of Prime95 are running in 2 different directories, no error reported there. The PC is running at 60C for each core, no overclocking at this time, all the power supplies are slightly higher than default to be sure. The PC could be stable for 2 days without crashing. It could also crash after a couple of hours. Always the same error code, the same driver and Prime95 in the background. Has anyone noticed anything similar to this ? The norton support is helpless at this point and I am considering dropping Norton to McAfee, hoping it would behave better. This is the memory dump, if this talks to anyone. I've been using Prime95 + Norton Security on a previous PC with no issue for years so I wonder what's going on here. New PC problem or norton360 problem / related to prime95 ? Thanks... 1: 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: 00000010, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: babb8588, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: 00000010 CURRENT_IRQL: 2 FAULTING_IP: SYMNDIS+588 babb8588 834010ff add dword ptr [eax+10h],0FFFFFFFFh CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: Prime95.exe LAST_CONTROL_TRANSFER: from babb895d to babb8588 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. bacdf230 babb895d 00000000 00000002 00000000 SYMNDIS+0x588 bacdf248 b43cdc67 89824b68 00000000 bacdf6c4 SYMNDIS+0x95d bacdf260 b43ce502 bacdf6c4 bacdf744 bacdf75c SYMFW+0xec67 bacdf45c b43c3910 000000c8 bacdf744 88392990 SYMFW+0xf502 bacdf638 babb87bf bacdf7dc bacdf789 00000001 SYMFW+0x4910 bacdf668 babb8cf0 bacdf7dc bacdf744 bacdf6c4 SYMNDIS+0x7bf bacdf724 babba87d bacdf73c 890ca2e0 00000000 SYMNDIS+0xcf0 bacdf808 b4bd0a8d bacdf878 00000003 bacdf84c SYMNDIS+0x287d bacdf87c b4bd0836 890d6a18 890ca2e0 8963f5fe tcpip!DeliverToUserEx+0x7e6 bacdf934 b4bcf922 890ca2e0 8963f612 00000124 tcpip!IPRcvPacket+0x6cb bacdf974 b4bcf84d 00000001 882ce058 8963f5f0 tcpip!ARPRcvIndicationNew+0x149 bacdf9b0 b20419eb 899f7ab8 00000000 897a2130 tcpip!ARPRcvPacket+0x68 bacdfa1c b959601d 002c2cf8 89ad3ba0 00000001 vsdatant+0x119eb bacdfa30 b95961b4 897a2130 89ad3ba0 00000001 psched!PsFlushReceiveQueue+0x15 bacdfa54 b95965f9 8983ac58 00000000 897a2130 psched!PsEnqueueReceivePacket+0xda bacdfa6c ba612d40 8983ac50 882ce0ac 8972a868 psched!ClReceiveComplete+0x13 bacdfabc b960aa26 002c2cf8 bacdfafc 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4 bacdfaf4 b20419eb 882ce058 88307c18 89bc4130 dne2000+0x7a26 bacdfb60 b9646809 0088fa88 bacdfd80 00000001 vsdatant+0x119eb bacdff9c b964939e 8970e000 89bc4130 00000000 Rtnicxp+0x5809 bacdffb4 ba608f09 8970e000 89848e18 bab389c0 Rtnicxp+0x839e bacdffcc 805450bf 8970e244 8970e230 00000000 NDIS!ndisMDpcX+0x21 bacdfff4 80544c2b b2ad6d44 00000000 00000000 nt!KiRetireDpcList+0x61 bacdfff8 b2ad6d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b 80544c2b 00000000 00000009 0081850f bb830000 0xb2ad6d44 STACK_COMMAND: kb FOLLOWUP_IP: SYMNDIS+588 babb8588 834010ff add dword ptr [eax+10h],0FFFFFFFFh SYMBOL_STACK_INDEX: 0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: SYMNDIS IMAGE_NAME: SYMNDIS.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 45a2fea3 SYMBOL_NAME: SYMNDIS+588 FAILURE_BUCKET_ID: 0xD1_W_SYMNDIS+588 BUCKET_ID: 0xD1_W_SYMNDIS+588 Followup: MachineOwner ---------

2007-10-18, 20:10	#3
Daffy Aug 2002 31 Posts	I am not really considering switching to Kaspersky (no trust). I'll try McAfee first, since we use it at work reliably. This issue has been there from day 1 (about a month), as soon as I installed Norton360. It's always the same message and seeing in the debug file Prime95 as the process name, I was wondering if it had anything to do with the issue. I have 2 directories for prime95 and I run them both from each directory. Is there any issue with that ? Each core is running one instance and it looks OK. No error from Prime95 itself. Just this random BSOD with SYMNDIS. And I searched the WEB and I can't find anything related to it. If I can't get an answer, I will uninstall it and run this PC out of the network for a while to see what happens. Then, McAfee. PS: Forgot to mention: I am trying now to run a single instance of prime95 and see what happens, in case this is related to 2 instances running. Last fiddled with by Daffy on 2007-10-18 at 20:13

2007-10-19, 06:02	#6
paulunderwood Sep 2002 Database er0rr 5·937 Posts	Try Norton500 Last fiddled with by paulunderwood on 2007-10-19 at 06:02

2007-10-18, 08:53	#2
Cruelty May 2005 2²×11×37 Posts	Go for Kaspersky rather than Norton / McAfee I have made such a switch ~3 years ago and I can recommend KIS. Anyways I have seen similar behaviour after updating Windows XP with some patches that were supposed to increase system stability...

2007-10-18, 20:35	#4
typo_pl Apr 2005 2² Posts	From my rusty kernel debugging skills, just looking at the callstack, it looks like Norton crashed while looking at a network packet the machine got. Try running without the net hooked up (after you got exponents assigned to your Prime95 instances) to see if that is the problem.

2007-10-19, 02:25	#5
Daffy Aug 2002 31 Posts	It crashed again, with 1 instance of prime95 and this time, it says that the process name is Idle. So, prime95 has nothing to do with this. I will try running the PC out of the network with norton and then, without it, if it happens again. Norton, you are about to lose a customer... Thanks for the help!