XP SP3 System Error Category (102) Event ID 1003 Code 1000007f

Not open for further replies.
Hello there,

I desperately need help. I am working on my honours thesis and my computer keeps crashing.

I have checked the event viewer. I have a system error with Category (102) Event ID 1003 Code 1000007f. I tried attaching Minidumps <100kb but I received an error.

Any advice would be greatly appreciated!

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 13/07/2008
Time: 10:46:58 AM
User: N/A
Error code 1000007f, parameter1 00000008, parameter2 80042000, parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
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 31 30 30 30 30 30 37 1000007
0020: 66 20 20 50 61 72 61 6d f Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 38 2c 20 000008,
0038: 38 30 30 34 32 30 30 30 80042000
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000


Posts: 12,015   +82
As per auhma.org: 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause and, of these, memory hardware failures are the most common.

So, 0x7F errors can be due to several things and corrupted memory is the most common. You will need to run MemTest on your RAM www.memtest.org Any errors and you have RAM that needs to be replaced.

How much RAM do you currently have, i.e., sticks? Since Memtest takes a long time and you are with time constraints try this: Take out one stick of RAM and see if that brings stability. If not switch out your RAM sticks.

* When you say you have errors with the minidumps what do you mean? You can zip up to 5 together in compressed format and attach to your posting.

* I strongly suggest you back up all of your hard work just in case.
Hello and thank you for your response. I only have one stick of RAM, I don't know how much there is but I know it isn't much. It is an old computer.

I tried uploading my zip file and it worked this time. So please disregard the error re: the attachment.

I will try the memtest. I suppose it is possible the applications I am using: MS Word, Endnote reference manager and online databases, are putting too great a load on the avail. RAM. How long does Memtest take to run approx.?

Thanks again!


  • bdrMiniDump.zip
    95.3 KB · Views: 6


Posts: 12,015   +82
For some reason when I go to open your Zip File my zip software reads it as an invalid file. You can post your minidumps individually as an attachment without zipping.

Most people run Memtest overnight and check it the next day. It is quite safe to do so.
Unzipped minidump

Thanks again for your response. I have attached one of my minidumps. If you could take a look it would be much appreciated.



Posts: 12,015   +82

These are generally caused by hardware issues (which often means driver issues). As a rule, be sure you have the latest Service Pack edition of your Windows operating system and are using the best device drivers and software versions. After that, do normal hardware troubleshooting for the device inplicated.

Honestly, this is the first time I have ever seen someone with this particular error code. As for the driver the minidump cited a core Windows driver which isn't much help. So after you've run MemTest and you have no errors do the following...

1. Run ChkDsk

2. Run a full harddrive diagnostics. Your harddrive manufacturer supplies the utility to do this.

3. Attach more minidumps if you have them.


Posts: 16,314   +36
I only have one stick of RAM, I don't know how much there is
To find this: Control Panel> system> System Properties tab. RAM will be toward the bottom.
I don't read mini dumps, but the Event Error suggest either a memory problem OR an problem with a Windows Update. did this problem begin after you installed SP3. Or did you get additional updates before it began?
Not open for further replies.