Dell Inspiron 1520 Motherboard issue?

Hello,

I have been trying to fix a Dell Inspiron 1520, but it seems that this machine has a defect motherboard:

Symptoms:
- frequently freezing, no error in event viewer or minidump
- sometimes when clicking via touchpad, the click keeps on repeating clicking endlessly
- sometimes the machine gives the warning sound (constant beeeeeeeeeeeeeeeeeeeeeeeeeeeeeep)
- sometimes a IRQL_NOT_LESS_OR_EQUAL BSD
- doesn't matter if machine was just started or has been running for eight hrs.

The rare minidumps (2 in 12 days) point to ntoskrnl.exe

Attempts to resolve so far:

All Dell Hardware Diagnosis tests have been completed successfully without error several times.
New drivers for touchpad etc installed (anyway, no sofware error was indicated).
Endless error checkings, sfc/scannow etc.
CPUCool shows max temp of 48
Fan is working well, sensor too (doesn't matter if machine was just started or has been running for eight hrs)
Ram has been tested, even exchanged

I am afraid that there is nothing else left than the mobo. Or?
SumukhaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dbruntonQuid, Me Anxius Sum?Commented:
>> CPUCool shows max temp of 48

If that's under load that is OK.

>> Ram has been tested, even exchanged

Remove RAM, blow out memory slots.  Try memory one stick at a time and see if error still occurs using only one stick.

Download a Live Linux CD such as Knoppix http://www.knoppix.org/  Make the CD and boot from it and run Knoppix for a while and see if errors still occur.  If they do it is hardware.  If they don't it is software.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SumukhaAuthor Commented:
Hi dbrunton,
thanks for posting.
Looked up the beep- one long one relates to systemboard. Done that w the RAM.
Great idea with the Linux. Will do that.
0
dbruntonQuid, Me Anxius Sum?Commented:
Also try disconnecting the touchpad (if possible) and use an external mouse.

But it is starting to seem very much like the board.
0
Introduction to Web Design

Develop a strong foundation and understanding of web design by learning HTML, CSS, and additional tools to help you develop your own website.

greg_vanderCommented:
Hi

I thought it could be an OS error, so the dbrunton idea for live cd should tell you if it's that. if there's no error with linux I recommend you to do a low level format before reinstalling the OS.
regards.
0
SumukhaAuthor Commented:
What do you mean by low level format?
0
dbruntonQuid, Me Anxius Sum?Commented:
A low level format is a format applied to a hard disk.

This isn't required in this case.  If the hard disk is suspected of being faulty then the disk manufacturer's utils can be used to determine it.  A combination of these utils can be found on the UBCD  http://www.ultimatebootcd.com/  Again most manufacturer's utils can map out faulty sectors making the use of a low level format unnecessary.

It probably wouldn't hurt to run a hard disk check.  But I'd suspect the motherboard more than the hard disk.
0
SumukhaAuthor Commented:
Me too. And I have run countless disc check already.
0
greg_vanderCommented:
Hi

did you do the test with knoppix ? if it's the same you could change motherboard, if not you 'll have to reinstall the OS.
0
SumukhaAuthor Commented:
Started checking with Ubuntu, but due to missing driver support for the wireless adapter, didn't test for hours and hours actively.

However, we are getting another mobo. I'll split points with more for dbrunton.
0
SumukhaAuthor Commented:
Final Solution:

It was NOT the Mobo!
When switching off one core, trouble stopped. Same with a different CPU. Different MOBO same.
Finally a complete factory reset made the errors disappear.

Meaning: cause was the part of the Win installation that takes care of the 2nd core.
All that although sfc was run more than once!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Laptops Notebooks

From novice to tech pro — start learning today.