Eric, I went and read through some of the archive and it looks like other people are getting the dreaded BSOD on POP3 as well. Upgrading the NIC fixed it. They even mention problems with the NIC that is in the server now (Network Everywhere err no where, late night and wal-mart was the only thing open that sold NICs) In the dump file it mentioned afd.sys (part of the IP stack). I also think its hardware because when I check the same folder from the server using outlook it does fine, ie no data over the nic. Any way, I'll post my results, and then prob beg my colo to swap out the nic for me...I really dont want to drive the 9 hours to Dallas from New Orleans. Scott
---------- Original Message ---------------------------------- From: "Eric Shanbrom \(Ipswitch\)" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Wed, 31 Dec 2003 08:48:37 -0500 >I'll probably get disagreed with but I have has this same problem. I >upgraded my NIC and drivers and all went away....BSOD on Win2K is typically >a hardware/driver issue. Rarely something from an application > >Eric S >----- Original Message ----- >From: "Scott Heath " <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Monday, December 29, 2003 3:48 PM >Subject: RE: [IMail Forum] imap4 causing reboot > > >> Attached is what I've pulled from the dmp file, hope this helps... This is >really making me pull my hair out. I'm just glad I was able to move imail to >a different box easily (thank you ipswitch!) >> >> ---------- Original Message ---------------------------------- >> From: "John Tolmachoff \(Lists\)" <[EMAIL PROTECTED]> >> Reply-To: [EMAIL PROTECTED] >> Date: Mon, 29 Dec 2003 11:23:16 -0800 >> >> >No such thing as SP6 for Windows 2000, at least not yet. (We have to get >to >> >SP5 first.) >> > >> >Please revise your post. >> > >> >John Tolmachoff >> >Engineer/Consultant/Owner >> >eServices For You >> > >> > >> >> -----Original Message----- >> >> From: [EMAIL PROTECTED] [mailto:IMail_Forum- >> >> [EMAIL PROTECTED] On Behalf Of Scott Heath >> >> Sent: Monday, December 29, 2003 11:08 AM >> >> To: [EMAIL PROTECTED] >> >> Subject: [IMail Forum] imap4 causing reboot >> >> >> >> Ok, this is very odd. I have two servers both windows 2000 at same >Service >> >> Pack (SP6). On one server things run perfect, a bit slow since its >doing >> >> other things as well. On the other server (the newer and faster one) >> >> things run great until I go to check mail using the IMAP4 protocol and >> >> folders with large amounts of mail (150+ messages) the server blue >screens >> >> and reboots. It does create a memory.dmp file which I've gone through >> >> using the debug tools in 2000 (I can provide the dmp file to anyone who >> >> cares to take a look at it). I'm not in a position to upgrade to >version >> >> 8 (I'm at 7.15 with all the hotfixes now). I did install the eval copy >of >> >> 8 and things work fine. I've uninstalled 7.15 and put a new install >back >> >> on...same problem. >> >> Any ideas anyone? >> >> Thanks! >> >> Scott >> >> >> >> >> >> To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html >> >> List Archive: >http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ >> >> Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ >> > >> > >> >To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html >> >List Archive: >http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ >> >Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ >> > >> > > >---------------------------------------------------------------------------- >---- > > >> >> Microsoft (R) Windows Debugger Version 6.2.0013.1 >> Copyright (c) Microsoft Corporation. All rights reserved. >> >> >> Loading Dump File [C:\WINNT\MEMORY.DMP] >> Kernel Dump File: Full address space is available >> >> Symbol search path is: f:\;F:\symbols >> Executable search path is: >> Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible >> Product: Server, suite: TerminalServer SingleUserTS >> Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e1b8 >> Debug session time: Sun Dec 28 20:25:13 2003 >> System Uptime: 0 days 0:15:07.625 >> Loading Kernel Symbols >> >............................................................................ >...... >> Loading unloaded module list >> .... >> Loading User Symbols >> ............................................ >> >**************************************************************************** >*** >> * >* >> * Bugcheck Analysis >* >> * >* >> >**************************************************************************** >*** >> >> Use !analyze -v to get detailed debugging information. >> >> BugCheck D1, {d, 2, 0, d} >> >> Probably caused by : afd.sys ( afd!ZeroIP6Address+58 ) >> >> Followup: MachineOwner >> --------- >> >> 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: 0000000d, memory referenced >> Arg2: 00000002, IRQL >> Arg3: 00000000, value 0 = read operation, 1 = write operation >> Arg4: 0000000d, address which referenced memory >> >> Debugging Details: >> ------------------ >> >> >> READ_ADDRESS: 0000000d >> >> CURRENT_IRQL: 2 >> >> FAULTING_IP: >> +d >> 0000000d ?? ??? >> >> DEFAULT_BUCKET_ID: DRIVER_FAULT >> >> BUGCHECK_STR: 0xD1 >> >> TRAP_FRAME: f67af714 -- (.trap fffffffff67af714) >> ErrCode = 00000000 >> eax=00000000 ebx=f67af7b8 ecx=0000ec08 edx=0000ec08 esi=843dbb48 >edi=843d115c >> eip=0000000d esp=f67af788 ebp=843dbc6c iopl=0 nv up ei ng nz na pe >nc >> cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 >efl=00010282 >> 0000000d ?? ??? >> Resetting default scope >> >> LAST_CONTROL_TRANSFER: from 03ddaf70 to 0000000d >> >> STACK_TEXT: >> WARNING: Frame IP not in any known module. Following frames may be wrong. >> f67af784 03ddaf70 0000001a 03ddad70 00000001 0xd >> 00010282 00720067 006d0061 00460020 006c0069 0x3ddaf70 >> 843dbc6c 00000002 00000000 00000002 00000000 0x720067 >> >> >> FAILED_INSTRUCTION_ADDRESS: >> +d >> 0000000d ?? ??? >> >> FOLLOWUP_IP: >> afd!ZeroIP6Address+58 >> f68f64c0 ffff ??? >> >> FOLLOWUP_NAME: MachineOwner >> >> SYMBOL_NAME: afd!ZeroIP6Address+58 >> >> MODULE_NAME: afd >> >> IMAGE_NAME: afd.sys >> >> DEBUG_FLR_IMAGE_TIMESTAMP: 3eaf8d29 >> >> STACK_COMMAND: .trap fffffffff67af714 ; kb >> >> BUCKET_ID: 0xD1_CODE_AV_BAD_IP_afd!ZeroIP6Address+58 >> >> Followup: MachineOwner >> --------- >> >> >> > > > >To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html >List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ >Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ > To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
