ErrorCode1003

[moopitz]

hi, i have windows server 2003 r2 sp1 and i recently received 2 bsod's on my server, 1 around 430 pm and the 2nd around 8 the next morning. the eventlog reported both times:

Error code 00000022, parameter1 001400f9, parameter2 f78f69b8, parameter3 f78f66b4, parameter4 8081df7c.

I referred to a previous thread about this and am wondering if anyone may have more information on this error 1003. the server was working fine until now. recent changes were increasing disk allocations, revdrive for back up (now uninstalled), acronis backup s/w for servers. i looked into the minidump file and saw that symantec was a frequent word used in there. i hope this is enough information to use. any help would be appreciated.

 

[Bobbye]

I'm going to refer you here due to the lack of information:
http://www.google.com/search?q=Erro...ent-ff&ie=UTF-8&rls=GGGL,GGGL:2006-27,GGGL:en

Find what most applies to your system.

If you want to pin it down further, find the Error in the Event Log that corresponds to this and copy/paste it here. Event Error have 3 pieces of information which can be used to find cause and resolution:
Start> Run> type in eventvwr

Do this on each the System and the Applications logs:
1. Click to open the log>
2. Look for the Error>
3 .Right click on the Error> Properties>
4. Click on Copy button, top right, below the down arrow
5. Paste here (Ctrl V)

Ignore Warnings. You do not have to include the lines of code-if any- in the box below the Description.
The Error will resemble this:
Event Type: Error
Event Source: ?????
Event Category:?
Event ID: 1003
Date: 1/6/2009
Time: 4:50:06 PM
User: N/A
Computer: Yours
Description:
Error code 00000022, parameter1 001400f9, parameter2 f78f69b8, parameter3 f78f66b4, parameter4 8081df7c.

The Source is very important. it is also important to know what you were doing the 4:30pm and 8am when the errors came up.

Another avenue of information is the minidump logs. I don't read those, but other members do and they can be helpful in identifying a cause: Please see this:
https://www.techspot.com/vb/topic51365.html

 

[CCT]

For 2000 BUT I believe the codes are basically still the same;

http://msdn.microsoft.com/en-us/library/ms818901.aspx

 

[Route44]

0x22 errors are rare. From what I have gathered they are caused by faulty drivers. Since Symantec has come up so often try disabling it and see if you regain stability.

 

[moopitz]

minidump file is now added

here is the entire log from event viewer. hope this pins it down even more. i disabled the restart on error feature in case i get this bsod again.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/8/2009
Time: 8:03:23 AM
User: N/A
Computer: PINTO
Description:
Error code 00000022, parameter1 001400f9, parameter2 f78f69b8, parameter3 f78f66b4, parameter4 8081df7c.


Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 32 0000002
0020: 32 20 20 50 61 72 61 6d 2 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 31 34 30 30 66 39 2c 20 1400f9,
0038: 66 37 38 66 36 39 62 38 f78f69b8
0040: 2c 20 66 37 38 66 36 36 , f78f66
0048: 62 34 2c 20 38 30 38 31 b4, 8081
0050: 64 66 37 63 df7c

 

[CCT]

You should post some dump files:

http://support.microsoft.com/kb/254649

 

[Bobbye]

What were you doing at the two times you got the BSOD and the Error 1003?

Please see this Windows 2003 Server page- as you can see, it does matter what you were doing at the time the error came up: Starting up? Shutdown? Using a particular program or app? Accessing a particuar site?

Troubleshooting Windows Server 2003
http://labmice.techtarget.com/windows2003/Troubleshooting/default.htm

And here is a Microsoft reference for the Windows Server:
http://support.microsoft.com/default.aspx?scid=kb;en-us;323358

 

[moopitz]

My apologies to bobbye for not including this. routines were actually normal. users were surfing the internet the first event and the second there were 2 users logged in. perhaps there were other services starting or stopping at the time of the event? i.e. an MrxSMB warning occured before each event. also have wlbs popping up as error. just some thoughts there...

 

[Route44]

Your minidump is an 0x22 error and it cited the driver revfs.sys which belongs to the Iomega REV File System Software. Check out the following link:

http://www.tech-archive.net/Archive...blic.windows.server.sbs/2006-10/msg02857.html

 

[moopitz]

Thanks Route44! I guess that explains why things have been normal since i uninstalled it this morning under suspicion of a device driver. That would confirm what i was thinking but needed more brain power. thanks again to all who posted.

 

[Bobbye]

Thank you. Did you see the Windows server site I referenced? So we can eliminate troubleshooting for the problem at either Startup or Shutdown. This put us in the 'random' area.

And regarding 'wlbs', Is it safe to "assume" you mean the MS Windows NT Load Balancing Service (WLBS)? What is the Error?

And MrxSMb is the Windows NT SMB Minirdr (Mini Redirector)? You can't give 'shortcuts' for Error messages! It would help if you copied the specific Errors. Warnings, for the most part, can be ignored. ?If they don't resolve, an Error will come up.

Since you mentioned seeing 'Symantec' displayed often, this might be appropriate:

Symantec Backup Exec 11D for Windows Servers, rev. 6235, hotfix 6 & hotfix 9 installed.
Windows Server 2003 SP1.
Iomega REV ATAPI 35GB, Firmware: 74B (April, 2004 = latest, as for feb,2007)
Iomega REV System Software v.4.11.39
https://forums.symantec.com/syment/board/print?board.id=115&message.id=2743&page=1&format=page

This would link the Error and the information in the minidumps.

When I worked in a lab, we often used either acronyms or initials rather than words to describe a procedure or process. The problem was though, that others might say "huh?" and/or the chance of performing the wrong test or procedure was great because of this 'shorthand' talk.

Bottom line is: we have to work with what we're given. The more accurate and complete, the better to find an appropriate resolution!