BSOD, Reboot During Backup ==> System Error, Category (102), Id 1003

In general bugcheck code 4E is related to faulty ram.  Refer the following problem.
http://www.windowsbbs.com/showthread.php?t=53334
https://www.experts-exchange.com/questions/21824286/Random-reboots-on-XP-Sp2.html

Run memtest to strress test the ram.

If you can provide upload the minidumps to EE "Expert Area", I will confirm the culprit. You can find the minidumps at \winnt\minidumps

Upload Minidumps to EE "Expert Area"
. Login http://www.ee-stuff.com using your Experts-Exchange username and password.
. Click on "Expert Area" tab
. Type url link of your Question
. "Browse" your pc to the location of your Minidumps click "Upload"
. Copy the resulting "url" and post it back here.

Hi cpc2004,

Thanks for the links!  I will read them while the RAM tests are in progress...  Before I came to the office, I disabled shadowing on drive E, the system and data volume.  I did a backup and after 5.6GB, the server rebooted, so I don't think that this issue is truly VSS related.  I am running Memtest86+ on the server right now and will let you know the result.  I am very suspicious about the RAM, too, because the system did not BSOD before the upgrade.  The mobo is a Tyan Thunder K8WE, single processor,  with all the latest drivers from late last year.  All of the memory, 4x1GB ECC REGISTERED 128-bit, is from Crucial.  If the RAM passes its tests, then I will pull out the new memory and do a backup.  Usually, when the backup reaches 6GB, the server reboots.  If it succeeds, then there is an issue with one of the new sticks or the mobo.  I will insert one new ram stick and try the backup again...  If that works, then I will pull out that stick and insert the remaining one.  If it fails, we have our culprit.  If it works, then the issue must be mobo related...  How does this sound to you?  I will be happy to post the files that you've requested after I finish these initial tests.  Thanks for your help!
Mike  

BTW...  All of the components in this server are on Microsoft's compatibility list...

Well, Memtest86+ (version 1.70), did not discover any errors with the RAM...  So, it appears that this must be Win2003 related issue.  Still need to get a backup, so I am going to pull out the new RAM, do the backup and then replace it.  I will send the files that you've requested.  Thanks!

Hi cpc2004,

I've placed a zipped version of my minidumps here: https://filedb.experts-exchange.com/incoming/ee-stuff/2446-MiniDumps.zip.

Thanks for the help,

Mike

I removed both sticks of new RAM and reenabled shadowing on drive E:, which I had disabled to determine whether it might be the problem.  Now, the system has the original memory (2x1GB) in it and I am doing the full backup (no exchange) that causes the system to crash with all 4 memory sticks in it.  I have successfully completed the full backup, 17GB.  I am using Win2003's backup utility for backups, and perform two backups each day: (1) Only Exchange; (2) Files, system state, no Exchange.  Any ideas?

Your windows is crashed without pattern and this is the symptom of hardware error. One minidump is crashed with bugcheck code 1A and it is also the symptom of faulty ram.

Conclusion
The culprit is ram.

Debug report
Mini020307-01.dmp BugCheck 1000008E, {c0000005, 80892182, af3aaa58, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+17c )

Mini020807-01.dmp BugCheck C2, {7, 121a, 142000, e6201d38}
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+477 )

Mini020807-02.dmp BugCheck 1000008E, {c0000005, 5e9b0730, aeb76a74, 0}
Probably caused by : amon.sys ( amon+526c )

Mini021007-01.dmp BugCheck 1000008E, {c0000005, 80873437, b0bb439c, 0}
Probably caused by : CpsFsJnl.sys ( CpsFsJnl+1ae3b )

Mini021007-02.dmp BugCheck 1A, {400, c03ffd80, 300, e100a048}
Probably caused by : memory_corruption ( nt!MiDeletePte+441 )

Mini021007-03.dmp BugCheck 4E, {99, 0, 0, 0}
Probably caused by : amon.sys ( amon+46b6 )

Mini021107-01.dmp BugCheck 1000008E, {c0000005, 80857be9, aeae2910, 0}
Probably caused by : amon.sys ( amon+2d42 )

Mini021107-02.dmp BugCheck 1000007E, {c0000005, b9e47231, f78fabd0, f78fa8cc}
Probably caused by : HidBatt.sys ( HidBatt+2231 )

Mini021107-03.dmp BugCheck 50, {bb4eaf10, 8, bb4eaf10, 2}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+dc )

Mini021107-04.dmp BugCheck C2, {7, 121a, 0, e1ef2008}
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+477 )

I have been reviewing online information about ntkrpamp.exe.  Here is what I have found:

"All of the Intel x86 family processors since the Pentium Pro include a memory-mapping mode called Physical Address Extension (PAE). With the proper chipset, the PAE mode allows access to up to 64 GB of physical memory. there is a special version of the core kernel image (Ntoskrnl.exe) with support for PAE called Ntkrnlpa.exe. (The multiprocessor version is called Ntkrpamp.exe.) To select this PAE-enabled kernel, you must boot with the /PAE switch in Boot.ini.  Because the PAE kernel presents 64-bit addresses to device drivers and other system code, booting /PAE even on a small memory system allows a device driver developer to test parts of their drivers with large addresses."

So, if my server is booting with /pae, my system could address 64GB of memory.  I only need to address the normal 32-bit limit of 4GB.  Assuming that my server is booting with this switch, I wonder if I removed it whether ktkrpamp.exe would stop STOPing my computer...  Any opinion?  I have tested the memory several times on different systems and do not encounter errors...

 

Do you have any update?