Another dump, this time with a 0X00000007F and it's crashing in Safe Mode whenever I copy files either to a USB or via the network. Any hope?
XP SP3 crashing with Event Category: (102), Event ID: 1003
- Thread starter rkudyba
- Start date
- Status
Route44
Posts: 12,015 +82
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.
Nothing definitive as way of drivers, etc. However, within both dumps EXCETION_GP_FAILURE was noted and one possibility is that this can be due to faulty memory.
I went back and reread this thread. You ran memtest once for 3 Passes and then again for 4 Passes for a total of 7 Passes. I missed this earlier and that is not how it needs to work.
Memtest needs to run a mininimum of 7 Passes in one testing. Many people think that after running the minimum of 8 individual tests that constitute one Pass that the test is only repeating itself. Nothing could be further from the truth because the test throws at the memory differeing patterns all the time that is why a minimum of 7 Passes is essential.
I have run this test myself and my RAM together failed in the first Pass but running individually per stick I didn't get errors until the 7th or even 8th Pass. I know those who didn't get fails until the 10th, 15th, 19th, and one person until the 26th.
I strongly suggest you start this test again 2 hours before going to bed and check the next morning. In your case I would not stop this test until at least 10 Passes have occured.
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.
Nothing definitive as way of drivers, etc. However, within both dumps EXCETION_GP_FAILURE was noted and one possibility is that this can be due to faulty memory.
I went back and reread this thread. You ran memtest once for 3 Passes and then again for 4 Passes for a total of 7 Passes. I missed this earlier and that is not how it needs to work.
Memtest needs to run a mininimum of 7 Passes in one testing. Many people think that after running the minimum of 8 individual tests that constitute one Pass that the test is only repeating itself. Nothing could be further from the truth because the test throws at the memory differeing patterns all the time that is why a minimum of 7 Passes is essential.
I have run this test myself and my RAM together failed in the first Pass but running individually per stick I didn't get errors until the 7th or even 8th Pass. I know those who didn't get fails until the 10th, 15th, 19th, and one person until the 26th.
I strongly suggest you start this test again 2 hours before going to bed and check the next morning. In your case I would not stop this test until at least 10 Passes have occured.
I have run the MEMTEST overnight twice and never did an error show. Not sure how many times it ran but it was for over 12 hours.
I went back to the original memory and right away got this even in Safe Mode:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0x80f19dc1, 0x00000001, 0xf73fcac1, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. And here it is.
I went back to the original memory and right away got this even in Safe Mode:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0x80f19dc1, 0x00000001, 0xf73fcac1, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. And here it is.
Route44
Posts: 12,015 +82
You are going to find this hard to believe but the 0x50 error specifically cited corrupted memory are the cause of your system crashes. On the rare occasions bad RAM has been known to pass Memtest.
The other 0x50 error cited Mup.sys which is a Windows driver. See this link to gain more information: http://www.file.net/process/mup.sys.html
In my research the advice was to run a Repair but one person mentioned he got this this error and Mup.sys and came to be a bad memory slot on his motherboard and once he switched the memory to another slot all was well.
How many memory slots does your motherboard have?
The other 0x50 error cited Mup.sys which is a Windows driver. See this link to gain more information: http://www.file.net/process/mup.sys.html
In my research the advice was to run a Repair but one person mentioned he got this this error and Mup.sys and came to be a bad memory slot on his motherboard and once he switched the memory to another slot all was well.
How many memory slots does your motherboard have?
Route44
Posts: 12,015 +82
I think this is going to be the "switch around and see what works" diagnostic step. Not very sleek but it works. 
I wish I could see how the manual designates the memory configuration for your board. I take it the Kingston is in a 2x1gig set, correct?
If so where are they placed in the motherboard, both blue or both black?
Can you link me to your system on HP's website?
I wish I could see how the manual designates the memory configuration for your board. I take it the Kingston is in a 2x1gig set, correct?
If so where are they placed in the motherboard, both blue or both black?
Can you link me to your system on HP's website?
HP D530 CMT drivers link.
Yes they come in pairs and need to be installed in the corresponding blue & black slots respectively, but it doesn't much matter since the 4 are all the same.
See attached pic of the slots w old mem installed.
I have MEMTEST running now on the old memory, and I'll run it all night.
Yes they come in pairs and need to be installed in the corresponding blue & black slots respectively, but it doesn't much matter since the 4 are all the same.
See attached pic of the slots w old mem installed.
I have MEMTEST running now on the old memory, and I'll run it all night.
Attachments
KTH-D530/512
but on Kingston's site they have KTH-D530/512S but my chips do not have the last "S" on them.
Note MEMTEST ran 39 times over night and passed with no errors no the OLD HP memory.
but on Kingston's site they have KTH-D530/512S but my chips do not have the last "S" on them.
Note MEMTEST ran 39 times over night and passed with no errors no the OLD HP memory.
Yes already 2 today after running MEMTEST 39 (!) times with NO errors.
Download the mini and memory dumps here.
Download the mini and memory dumps here.
Route44
Posts: 12,015 +82
Your larger dump was corrupted and thus unreadable.
Your second minidump is 0xD1 and these are usually caused by faulty drivers. In this case the Windows driver ndis.sys was cited as the cause of your issues. usually OS drivers are too general to be of much help but in your case it might be helpful.
The NDIS library (Network Driver Interface Specification) is contained in ndis.sys. It is a collection of routines that applications can invoke to perform network-related operations. Ndis.sys is an integral part of the kernel and it must match other kernel components to work properly.
Further research shows that one way to rectify ndis.sys BSODs is to either update NIC card drivers or in some cases replace a defective NIC card.
Update your NIC card drivers.
Your second minidump is 0xD1 and these are usually caused by faulty drivers. In this case the Windows driver ndis.sys was cited as the cause of your issues. usually OS drivers are too general to be of much help but in your case it might be helpful.
The NDIS library (Network Driver Interface Specification) is contained in ndis.sys. It is a collection of routines that applications can invoke to perform network-related operations. Ndis.sys is an integral part of the kernel and it must match other kernel components to work properly.
Further research shows that one way to rectify ndis.sys BSODs is to either update NIC card drivers or in some cases replace a defective NIC card.
Update your NIC card drivers.
Blast. Another IRQL_NOT_LESS_OR_EQUAL, again referencing ATAPI.sys. Note I did disable the installed NIC card. Dump file download link.
Route44
Posts: 12,015 +82
Both errors are 0xD1 which are usually caused by faulty drivers. Both cite the Windows OS driver atapi.sys which IDE/AEPI Port Driver - Standard Harddisk controller. It can also be used for CD-ROM drives.
In my research it cited possible memory issues, harddrive issues, or CD-ROM.
Also, there was a lot about rootkits and this driver being corrupted but I am not saying this is your issue.
Have you done any system scans with your security software?
In my research it cited possible memory issues, harddrive issues, or CD-ROM.
Also, there was a lot about rootkits and this driver being corrupted but I am not saying this is your issue.
Have you done any system scans with your security software?
Route44
Posts: 12,015 +82
Download the free versions of Malwarebytes and Superantispyware and run both.
Sorry, but I can't remember if you did or stated the following:
1. Run a harddrive diagnostics.
2. Check your cables to your harddrive and ROM drives. Make sure they are securly attached to both components and the motherboard.
3. When do the BSODs occur, i.e. what are you doing?
Sorry, but I can't remember if you did or stated the following:
1. Run a harddrive diagnostics.
2. Check your cables to your harddrive and ROM drives. Make sure they are securly attached to both components and the motherboard.
3. When do the BSODs occur, i.e. what are you doing?
Route44
Posts: 12,015 +82
Lets back up a step. When you updated your onboard NIC drivers from where did you update?
Update: Are you running Avira? The reason for my asking is because in one of your latest minidumps the avipbb.sys driver was cited as not being able to load because it was being blocked. This is an Avira driver that I had written down to research but I forgot to. What security software besides Avira do you have installed running as real time protection, i.e. firewall, anitspyware/malware, etc.? Which ones, if any, are installed but not in real time protection?
Update: Are you running Avira? The reason for my asking is because in one of your latest minidumps the avipbb.sys driver was cited as not being able to load because it was being blocked. This is an Avira driver that I had written down to research but I forgot to. What security software besides Avira do you have installed running as real time protection, i.e. firewall, anitspyware/malware, etc.? Which ones, if any, are installed but not in real time protection?
Well I disabled the NIC card and put in an old one, but for the installed, hard wired NIC I used the HP support page.
Yes only AVG Free 9.0 is installed. I uninstalled SAV a whilst back. No other real time running. Should I uninstall AVG? MalwareBytes is installed but not real time.
Another minidump attached.
Yes only AVG Free 9.0 is installed. I uninstalled SAV a whilst back. No other real time running. Should I uninstall AVG? MalwareBytes is installed but not real time.
Another minidump attached.
Route44
Posts: 12,015 +82
First, since you uninstalled Avira the avipbb.sys driver should not be present. Different antivirus drivers will conflict causing system crashes. it appears there is at least one old Avira driver still present in your system.
Second, I read your minidump file and it is error 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues.
It simply cited hardware as the problem. However, within the minidump this information was cited: IP_MISALIGNED and this is often due to memory. In my research I came across the following from a 2005 TechSpot post by cpc2004 who, in my estimation, was the best I have ever come across to read minidumps. He now only checks in on the rare occasion. Here is what he wrote to someone else concerning IP_MISALIGNED:
This is hardware problem. IP_Misaligned (Instruction Misaligned) is usually caused by faulty memory.
Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram
Second, I read your minidump file and it is error 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues.
It simply cited hardware as the problem. However, within the minidump this information was cited: IP_MISALIGNED and this is often due to memory. In my research I came across the following from a 2005 TechSpot post by cpc2004 who, in my estimation, was the best I have ever come across to read minidumps. He now only checks in on the rare occasion. Here is what he wrote to someone else concerning IP_MISALIGNED:
This is hardware problem. IP_Misaligned (Instruction Misaligned) is usually caused by faulty memory.
Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram
I've done 1-5 already. Note that I still had AVG installed; I just UNinstalled it now. Just before uninstalling yet another crash of:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0xc0000005, 0xbff6a931, 0xee346830, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.
And a link to download the dumps..
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0xc0000005, 0xbff6a931, 0xee346830, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.
And a link to download the dumps..
Route44
Posts: 12,015 +82
Both errors are 0x8E and both pointed to the Windows driver rdpdd.dll as the cause of your crashes. This driver is for video display. keep in mind that OS drivers generally are not the issue but point to the fact that there is an issue. From research the latest video card drivers correct this issue. However, you already did this if I am not mistaking, correct?
Another interesting thing in your dump is the following: PEB is paged out. This can be due to memory leakage and here is one definition that, honestly, I can't fully explain but perhaps it might help you:
"PEB is paged out." This error indicates that the process environment block (PEB) is not accessible.
To load symbols, the debugger looks at the list of modules loaded by the operating system. The pointer to the user-mode module list is one of the items stored in the PEB.
In order to reclaim memory, the Memory Manager may page out user-mode data to make space for other process or kernel mode components.
When this error occurs, it means that the debugger has detected that the PEB data structure for this process is no longer readable. Most likely, is has been paged out to disk.
Without this data structure, the debugger cannot determine what images the symbols should be loaded for.
* I'll take a guess but a module or two could not be loaded for your video card.
Another interesting thing in your dump is the following: PEB is paged out. This can be due to memory leakage and here is one definition that, honestly, I can't fully explain but perhaps it might help you:
"PEB is paged out." This error indicates that the process environment block (PEB) is not accessible.
To load symbols, the debugger looks at the list of modules loaded by the operating system. The pointer to the user-mode module list is one of the items stored in the PEB.
In order to reclaim memory, the Memory Manager may page out user-mode data to make space for other process or kernel mode components.
When this error occurs, it means that the debugger has detected that the PEB data structure for this process is no longer readable. Most likely, is has been paged out to disk.
Without this data structure, the debugger cannot determine what images the symbols should be loaded for.
* I'll take a guess but a module or two could not be loaded for your video card.
- Status
Latest posts
-
Logitech thinks the computer mouse needs an AI upgrade- Anton Longshot replied
-
Russia-backed hacking group suspected of attack on US water system- JESUSxISxLORD replied
