System Crashes

[pcpd425]

I have had countless crashes and have search all over the net for solutions. This is the only site I've found that someone will actually look at the minidumps or actual error codes/parameters. My crashes have been occurring for over a year and I have over 125 minidumps. I have an HP Pavilion a250y with a 3Ghz Pentium 4 HT processor. I have one GB of ram. The system is as it was when the factory shipped it in the summer of 2003. On the advice of HP support, I performed a DESTRUCTIVE system restore, which reset everything back to the settings as they were when the computer shipped. The system crashes slowed down, but never ceased. Recently, I downloaded all of the Windows patches/fixes, including the SP2 release. After doing the SP2 download, it seems that the crashes are much more frequent. I have used PC Doctor to scan all of my hardware , which hasn't revealed any problems. I tried using memtest and the windows memory diagnostic software, but I can't get either to work. I do not have a floppy drive and burnt the "iso" to a CD, but I cannot get it to boot. I changed the boot sequence in the BIOS and even disabled all boot drives except the CD drive, but still could not. I have removed both 512 MB sticks of RAM, replacing them one at a time, but I still experience crashes. There is no pattern (that I know of) to these crashes. Any help is GREATLY appreciated.
I will post the most recent system errors...

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/20/2006
Time: 7:35:47 AM
User: N/A
Computer: YOUR-O0KWKW9JWC
Description:
Error code 100000d1, parameter1 00000800, parameter2 00000002, parameter3 00000000, parameter4 00000800.

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


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/20/2006
Time: 2:15:44 AM
User: N/A
Computer: YOUR-O0KWKW9JWC
Description:
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.
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 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

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/20/2006
Time: 1:45:07 AM
User: N/A
Computer: YOUR-O0KWKW9JWC
Description:
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.
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 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

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/19/2006
Time: 11:58:07 PM
User: N/A
Computer: YOUR-O0KWKW9JWC
Description:
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.
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 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

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/19/2006
Time: 9:07:00 PM
User: N/A
Computer: YOUR-O0KWKW9JWC
Description:
Error code 1000007f, parameter1 00000008, parameter2 f772fd70, parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
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 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: 66 37 37 32 66 64 37 30 f772fd70
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

Please tell me if you want recent minidumps attached or if you have any other questions. Thanks!!!

 

[OpTiMuSpRiMe]

have you done a complete reinstall of the os and drivers on the system since the day you purchased the machine... if not then it is time to do so... memtest has to burned to a bootable cdrom to work right.. what software did you use to burn the memtest iso??? i would use alcohol 120% with the imag burning wizard.. i have done that with my copy and works fine... if you have that many mini dumps then you have had this issue for some time now and it seems to be getting worse.. your best bet would be to backup and reinstall for saftey reasons... but first run all the hardware diags that you can to make sure that it is not hardware or driver related then reinstall to make sure that it is not software that is the issue... i am sure you will get someone who can look at the mini dumps more thuroughly but i am at work right now and do not have time to read them all..try pming howard hopinsko he is realy good at the mini dumps.. good luck mate

 

[pcpd425]

Yes, I have performed a complete DESTRUCTIVE restore, which reformatted the harddrive and then reinstalled the OS. I then went to the HP site and downloaded all of the hardware updates recommended by their site and finally went to Windows Update and downloaded all updates there. I have used PC Doctor to check all hardware and everything is fine (so it says). I burnt the CD first using the software built into XP and then used "Record Now" the second time around. I will look for Alcohol 120% to see if I have better results with that.

 

[OpTiMuSpRiMe]

don't use roxio or any other burning software like that i have never had good luck on those for making bootable cds... they always leave their own little footprints on it so they tend not to work well for me.. i am not saying they don't work i just have not had good luck on them.. alcohol should work just fine if you doing it right and you don't have any underlying hardware issue that just is not showing up.. try using the memtest86 cdrom the u burnt from 120% in another system if one is available and see what it does!! let me know

 

[pcpd425]

I don't have another system to check it on....

 

[pcpd425]

Here are the minidumps for 01/18/2006 if anyone can look at them...

 

[pcpd425]

Here are the minidumps for 01/19/2006 if anyone can look at them...

 

[pcpd425]

Here are the minidumps for 01/20/2006 if anyone can look at them...

 

[howard_hopkinso]

Hello and welcome to Techspot.

1 minidump crashes with an unknown image.

1 minidump crashes at ntkrnlmp.exe. This is a Windows nt kernel file.

1 minidump crashes at USBPORT.SYS. This is the Windows USB 1.1 & 2.0 Port Driver.

They all have a bugcheck of 7F.

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 (many dozen KB articles exist for this error referencing specific hardware failures) and, of these, memory hardware failures are the most common.

It would seem that you have some kind of hardware problem. Ram is the most likely culprit, but it could also be caused by faulty video card/psu/cpu/mobo etc.

Go HERE and follow the instructions.

 

[howard_hopkinso]

I have now looked at the rest your minidumps, which you attached while I was posting my first. reply to you.

The bugcheck of 7F is predominant. I therefore conclude that it is indeed a hardware error.

Regards Howard

 

[pcpd425]

I have already followed the instructions in the page you referenced, with the exception of the memory test. I tried "memtest" and "windiag", but I have had some difficulty since I only have a CD-ROM drive and no floppy. I followed the instructions for the CD version, but once I burn the ISO to the floppy and re-sequence the boot drives, it tries to read the CD drive and then skips over to the C: drive. I cannot initiate the testing sequence.

 

[howard_hopkinso]

You did burn the iso file as an image didn`t you?

If you try to burn it any other way it won`t work.

What burning software do you use?

Regards Howard

 

[pcpd425]

Originally, I burnt it using the Windows XP software, which I think is a version of Roxio. However, I then used Alcohol 120% at the suggestion of Optimusprime. I'm pretty sure I burnt it as an image using the alcohol software, but I'll have to double check to be sure.

 

[pcpd425]

Yes, the ISO was burnt as an image, but I still can't boot from it for the memory test to work.

 

[howard_hopkinso]

Strange. I can`t think what the problem might be.

See if you have better luck with this memory tester HERE

Regards Howard

 

[pcpd425]

I had already tried the "windiag" ISO, but I tried it again using the Alcohol 120% software, also with no luck. When I try to boot using either the memtest or the windiag, a massage appears stating "Reboot and Select Proper Boot Device or Insert Boot Media in Selected Boot Device and Press a Key. I just can't get it to boot from the CD. Also, memtest has a USB option, but when I try to boot from that it says something about needing an OS. I don't remember exactly what it said, I just know I can't do anything to get it to boot. Also, I have attached the most recent minidumps...I get anywhere from 4 to 6 a day and maybe more...

 

[howard_hopkinso]

2 minidumps crash at swmidi.sys. this is your Microsoft GS Wavetable Synthesizer. They have a bugcheck of D3.

1 minidump crashes at ntkrnlmp.exe. This is a Windows nt kernel file. It has a bugcheck of 7F.

1 minidump crashes at Vax347b.sys. Alcohol 120% driver. It has a bugcheck of 7F.

Hardware problem.

I don`t know why you can`t run the memtest programmes. Personally I use Nero to burn iso images. I`m not that familiar with Alcohol 120%.


Regards Howard

 

[xero]

question

Do you have a BROADCOM network card????

 

[pcpd425]

I'm not sure, it came with the computer. Do you think I should just take the computer to the service center and let them diagnose and fix it? I'm not implying you guys haven't been helpful, because you have been, but since I can't test my memory, maybe I should just bite the bullet and take it somewhere to have it fixed. I really wanted to be able to idenify the problem so that some computer tech at the shop couldn't tell me that I needed to replace stuff that didn't need replaced.

 

[howard_hopkinso]

Maybe when you`re trying to burn an iso file. You`re doing something wrong.

Take a look HERE for instructions on how to burn an iso file with Alcohol 120%

Regards Howard

 

[xero]

you can always....

You can always bring it to the shop, but it will make you a better computer genie when you try to resolve it yourself c it as a learning bug.

So far as i can tell, 99% of all crashes and bsod's are related to drivers.
In rare cases the bsod's are caused by spyware (better: malware)
And in even fewer cases related to hardware (in special, memory)

Disabling/removing devices will automatically shut down device drivers (in most cases they wont be loaded). Try swapping in an other video card, like an old s3 virge (o what were they stable back then *lol*). When the problem isnt resolved you should disable audio... next you disable or swap out the network card etc etc etc

This way you are minimizing to the possible cause.

If the problem does not occur anymore than the drivers of the last removed/disabled peripheral are faulty, search for upgrades.

I am sure you will find it.

 

[xero]

ps

try a bios update!!!!!!!!!!

 

[pcpd425]

Xero, I appreciate your position and I am always willing to learn. I am not trying to take the easy way out, if I was I would not have come to this site. However, I don't have 50 old computers laying around to swap different components in and out until the problem is corrected and I am certainly not going to go and buy a bunch of different components hoping to fix it. If our car mechanic took this approach, we would all be forced to ride bicycles, because it would be impossible to afford to have your car fixed. Luckily, technology and smart people exist, making diagnosing and fixing these problems, fairly easy, quick and less expensive than replacing parts one at a time until the problem has resolved itself. Now having said that, is there a way to accurately diagnose my problem based on the minidumps I have attached or this kind of a hit and miss approach as well? I have seen some very informative posts regarding various minidump "inspections", but since I am not able to test my memory, I'm not sure where to go from here. Why were these crashes so minimal, before I installed all of the updates to the original XP SP1 installation and now after SP2, they are so prevelant? I have never owned or used a computer that crashed with any degree of regularity...Once or twice a year was all. This computer has been crashing 4 to 7 times daily, which is obviously very frustrating.

 

[pcpd425]

Also, I have the most recent BIOS update as provided by the HP website....

 

[xero]

Allright, i did some investigation on your minidump files.

What i can c is that the driver REGSPY.SYS! is causing you BSOD.

Typing this regspy.sys filename in google along with bsod comes to the following solution:

uninstall bitdefender or bullguard antivirus.

Thats it i think.

Good luck.