XP SP3 crashing with Event Category: (102), Event ID: 1003

Status
Not open for further replies.
So even after uninstalling AVG, there's a crash. And yes I updated the video driver and made sure it was for the specific monitor. Now Windows Explorer is crashing with:
Faulting application explorer.exe, version 6.0.2900.5512, faulting module duser.dll, version 5.1.2600.5512, fault address 0x00036e8d.

And another BSOD:
Error code 00000050, parameter1 f805a030, parameter2 00000000, parameter3 804ed4ee, parameter4 00000000.

Minidump attached.

Has the be a motherboard. The memtest passed 19 times in a row!
 

Attachments

  • Mini041910-01.zip
    17.9 KB · Views: 1
This is going to be hard to believe but your error is 0x50 and it specifically cites corrupted memory as your issue.

Refresh my memory (no pun intended) please: You already accessed the BIOS and the memory voltage was set at the manufacture's correct voltage specs, correct?
 
I went back through the posts and re-read them. I could be mistaken but have you run a harddrive diagnostics yet?
 
rkudyba said:
Yes a few times, always clean, no errors.
Click to expand...

The problem with HP and Dell, etc. is that they prevent the customer from accessing the BIOS and this is a hinderance because two things I really want to know is a) how the BIOS recognizes your RAM and b) at what voltage it has it set at. I am not saying the voltage is your issue but for information sake it would settle a few things.

In most computers the way you access the BIOS is at boot-up you keep hitting the Delete key (in some cases the Escape key). Have you tried either key?
 
rkudyba said:
Delete not Escape do nothing; F10 brings me in to Setup but again I could not find voltage setting.
Click to expand...

That is what I was afraid of. Okay, sorry to be repeating myself but what is your present memory configuration and what RAM is installed? What slots?

I went back and looked at your Kingston. How many sticks of 512 did your purchase?

* Also, just for you to know I went back through your PC manual to check memory information.
 
You can see in the thread where I switched back to the original HP sticks, 256 MB each in all 4 slots. Refer to the pic I took of them. The BSODS occur with the old and new sticks. The Kingston's are 512 MB each and I had 4.

Since I keep getting all kinds of different BSOD's wouldn't that indicate there is probably a deeper issue, e.g., something on the motherboard?
 
rkudyba said:
Since I keep getting all kinds of different BSOD's wouldn't that indicate there is probably a deeper issue, e.g., something on the motherboard?
Click to expand...

I was thinking this very thing last night and early this morning. I don't know what else to do with the memory issue because other than being able to access the BIOS there is nothing left. So, yes, I think that it could very well be your motherboard.

One other thing you could try is contacting DELL tech support and in a clear and concise way give a list of your error codes and the definitive memory corruption cause and every step yuo have taken. Believe it or not I have email works better than phone.

If they can't/won't help have you considered building one?
 
I took your advice and contacted HP support and lo & behold, got this reply:

Rob do not worry I will do my best to try and resolve the issues with the unit. Issues like these normally happen whenever there are multiple driver conflicts on the unit. In this scenario I would suggest you to try these below set of steps and check for the results:

Step A: Download and install the latest BIOS microcode update and check for the results. You can download the update from this link.

After the installation of the update restart the unit and check for the results. Also I would request you to check in the device manager of the unit and see if you can locate any driver conflicts on the unit and update us with the same. Try these above set of steps and check if your issue is resolved or not and update us with the results.

Please feel free to email us back. Once again, thank you for contacting HP e-Solutions; have a great day.

I was at version 1.07. So far so good.

I never would've thought of the microode and there wasn't any download for it on the unit's support page.

If this works, hope this thread helps someone else!
 
Gah! First, they actually responded to you (oops I said Dell in my previous post), b) in record time and understandable and, c) it seems they have resolved your issue. We're talking a modern day miracle here. Amazing! :D

So it was the motherboard all along but in nothing in the physical sense per se even though the symptoms pointed especially towards your memory and even drivers.

This is the first time I have come across here of a BIOS update option from HP (or DELL, Gateway, etc.).

I really hope this fixes your issue. Please, rkudyba, keep us updated and thanks for the valuable information. Good stuff.
 
Arrghhhhhhhhh!

Started installing Symantec. Crashed twice!

2nd time with:

Error code 00000050, parameter1 fb6bc480, parameter2 00000000, parameter3 00000000, parameter4 00000000.

memdumps attached. Hopefully HP Support will reply.
 

Attachments

  • manifest1.zip
    35.7 KB · Views: 1
0xD1 error which are usually caused by faulty drivers attempting to address an IRQ Level they shouldn't (and can be caused by faulty or mismatched RAM). The driver is atapi.sys which I believe is listed and defined in an earlier post is a Windows driver.

I would certainly call HP back and tell them of your issue, the error code, and the driver cited as the cause.
 
reformatted/reinstalled and more BSOD's

Based on recommendations from HP support, I formatted and reinstalled and during Automatic Updates, it just crashes and keep crashing with different BSODs.

The last error was:

BCCode : d1 BCP1 : 7A1F49EA BCP2 : 00000005 BCP3 : 00000000

BCP4 : 7A1F49EA OSVer : 5_1_2600 SP : 2_0 Product : 256_1

Error code 000000d1, parameter1 7a1f49ea, parameter2 00000005, parameter3 00000000, parameter4 7a1f49ea.

2 minidumps attached and 1 kernel dump downloadable below:

https://www.yousendit.com/download/OHo0eUNEQzdiV3hFQlE9PQ
 

Attachments

  • manifest.zip
    42.8 KB · Views: 1
I have been away for over a week. The 0xD1 error specifically cited the cause of your crashes are due to the smwdm.sys driver which is a SoundMAX Digital Audio Driver.

By the, the minidump file has your XP at Service Pack 2. I'm assuming you haven't had the chance to upgrade to Service Pack 3?
 
I wiped the HD and formatted/reinstalled and that's what happened. Again, the different BSOD's seem to be implying mother board.
 
try updating your audio drivers one more time. You may be very correct about the motherboard.
 
More crashes! 1 during the driver install, which was the latest version anyways.

BCCode : d1 BCP1 : 00000128 BCP2 : 00000005 BCP3 : 00000000
BCP4 : F751E5F8 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

Error code 000000d1, parameter1 000069f8, parameter2 00000002, parameter3 00000000, parameter4 f72191fd.

Error code 000000d1, parameter1 00000128, parameter2 00000005, parameter3 00000000, parameter4 f751e5f8.

3 minidumps attached full kernel dump at:
https://www.yousendit.com/download/dXFVYlJmYWJUWUJjR0E9PQ
 

Attachments

  • Mini051810-01.zip
    23.1 KB · Views: 1
The one 0xD1 minidump that gave a definitive cause points to the driver b57xp32.sys which is your Broadcom NetXtreme Ethernet/NIC driver.
 
Update: processor was bad

I brought it into a PC service company, they noticed the heatsink was running hot, changed out the processor and voila...
 
Status
Not open for further replies.

Similar threads

wiyosaya
Getting errors today
Replies
15
Views
1K
wiyosaya
wiyosaya
N
Official Intel Arc A730 and A770M benchmarks suggest RTX 3050 Ti, RTX 3060-like performance
Replies
16
Views
1K
kmo911
kmo911
W
Solved HackTool:Wind32/Mailpassview found
Replies
10
Views
5K
Broni
Broni

Latest posts

Back