Blue Screens XP - System Error - 1003

[moxy]

Hello ,


I am getting random blue screens in my XP SP2 machine with the following Event viewer info :

Source - System Error
Category - (102)
Event id - 1003



I have already :

1. Reseated RAM + Video card + cleaned inside case.
2. Reinstalled XP.
3. Updated MB Bios.
4. Updated all the system drivers.
5. Moved RAM stick to another slot.

But I still have the reboots and the blue screens.

Any help would be greatly appreciated.

I´ve attached 3 minidumps and you can see my system details in my profile.



Thanks ,

 

[howard_hopkinso]

Hello and welcome to Techspot.

I can`t see any minidumps.

Before you attach them. Go HERE and follow the instructions.

If that doesn`t help. Zip 5 or 6 of your latest minidumps together, and attach them here.

Regards Howard :wave: :wave:

 

[moxy]

Mini Dumps now attached

Hello again ,


There should be 2 minidumps be attached now and I will attach more if needed.

Also after the latest crash the Event Viewer is now saying the "event log file is corrupt".

Thanks again ,

 

[howard_hopkinso]

Both minidumps crash at ntkrnlpa.exe. Windows NT & kernel system file. They both have a bugcheck of 8E.

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

Your minidumps are inconclusive.

Go to the link I gave you, and follow the instructions.

Please let us know the results.

Regards Howard

 

[moxy]

Hi again ,

Thanks for your help so far .

I have tried everything on the link but I still got another BSOD.

I had some trouble updating the system board drivers because Windows XP seemed to want to take over the installations all the time.

Even in safe mode XP causes hassle, is there any way to disable the add/remove hardware wizard form starting with Windows ?

But the device manager says all is devices are ok.


I have the attached the latest minidump.


Thanks ,

 

[howard_hopkinso]

Your latest minidump crashes at win32k.sys. Windows Multi-User Win32 Driver. It also has a bugcheck of 8E.

The wizard can just be cancelled, then install your chipset drivers.

Did you run the memory tests?

Maybe you should backup your important data, and do a full format and reinstall of your OS. This would rule out OS corruption.

Regards Howard

 

[moxy]

Hi ,


Yes I ran memtest it gave no errors.

I have also reinstalled the OS twice this month.

I´m going to try again to reinstall the chipset drivers.

I´ll get back to you .

Cheers again

 

[moxy]

Hello again ,

I ran Memtest 4 more times and it gave me one error in 4 runs.

This is hardly conclusive , what do you think ?

All the system drivers are now absolutley up to date too.

I am waiting to see if it stops again.

I will post the minidump if the system fails again.

Regards ,

Moxy

 

[howard_hopkinso]

I agree that Memtest isn`t conclusive.

However, the fact that you did get some errors is perhaps cause for concern.

Just see how it goes.

Regards Howard

 

[moxy]

System crashed again without a minidump

Hello again ,

The system crashed again here´s some info :

1. The BSOD did not create a minidump.
2. The event viewer does not show any system error.
3. The BSOD mentioned win32k.sys again.



I had not changed any Windows settings since the last blue screen.

As I said earlier I have already reformatted and reinstalled twice .

I have backed up my data now just to be sure.

Any advice welcome,

Thanks

 

[howard_hopkinso]

The only real clue so far is the errors from Memtest.

While we both agree that these are inconclusive. It`s the best clue we`ve got so far.

Can you try a different stick of ram?

Also what psu do you have? Make/wattage.

Regards Howard

 

[moxy]

Hi Howard ,

The PSU is "Antec TruePower2.0 380Watt ATX12V power supply" it came with the sonata tower.

I only have one stick of RAM butI will buy another if necessary.

Thanks again ,

 

[howard_hopkinso]

In that case I doubt it`s a psu problem, but you never know.

Once you try another stick of ram, see if the problem goes away.

I guess I`m not helping much really, but I can`t think what the problem may be, other than what I`ve already suggested.

Regards Howard

 

[moxy]

Hello Howard ,


I´m going buy some RAM tommorow and test it out.


Thanks a lot for your help so far, it´s much appreciated.


Moxy

 

[moxy]

Hello ,


I have had this PC for more than a year and the problem only surfaced when I moved to a new flat.

I am thinking it could be the wall socket in my new flat which is causing my problem.

I also have a laptop which has never crashed using this wall socket but its power requirements aren´t as high.

Do you think this is a possibility or am I clutching at straws ?

At the moment the PC hasn´t crashed in 4 hours it seems to crash when I exert it in some way (i.e. burning DVD´s while surfing the net )

I ran Memtest again looking for an error but nothing.

Regards,

 

[howard_hopkinso]

At the moment I think anything`s possible.

However, as you say it only crashes when your push the computer under load. This could be a psu/ram problem, or possibly an overheating problem.

Regards Howard

 

[moxy]

Hello again ,

I´ve ordered some new ram online hopefully I will get it soon.
It´s always useful to have more anyway.

In the meantime the PC has been crashing with various BSODs.

I´ve attached the latest minidumps, hopefully they will indicate something specific.

All the best ,

Moxy,

 

[howard_hopkinso]

Your latest minidumps crash with the following errors.

1 crashes at symidsco.sys. Symantec Corporation IDS Core Driver. It has a bugcheck of D1.

1 crashes at ntkrnlpa.exe. Windows nt system file. It has a bugcheck of FC.

1 crashes with hardware. It has a bugcheck of 8E.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY. I haven`t the faintest idea what this bugcheck means.

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

Regards Howard

 

[moxy]

It was th RAM

It was the RAM , I replaced it with a new stick and all is well now.

Thanks for all your help Howard .

 

[howard_hopkinso]

Glad your problem is now solved.

Thanks for letting us know.

Regards Howard