Code 43 error

[Grenoots]

My pc is a dell Inspiron one 2320 and it’s had the code 43 error before but it was fixed simply but now it’s been having it a lot and I can barely play games without the whole thing force restarting then I get code 43 and now I’ve used every method that I could find and it’s still not working, I’ve even opened up the back of it to check if anything wasn’t connected for some reason. I can’t buy a new gaming pc like I would want to because my mom doesn’t have enough money to buy it so I’m stuck with this for a while and I was wondering if any of you know any fixes

[Bombastinator]

Code 43 error is a general “derp” error which doesn’t explain why something is happening. “Usually hardware “ is the explanation I’m seeing which isn’t very helpful.

 

So hardware debugging:  this could involve more than “looking in the back”.

 

 “Works till it suddenly doesn’t” Is often memory, which is fairly cheap at least.  Maybe we’ll get lucky and a memory test will show something.  Have you run memtest?

[Grenoots]

27 minutes ago, Bombastinator said:

Code 43 error is a general “derp” error which doesn’t explain why something is happening. “Usually hardware “ is the explanation I’m seeing which isn’t very helpful.

 

So hardware debugging:  this could involve more than “looking in the back”.

 

 “Works till it suddenly doesn’t” Is often memory, which is fairly cheap at least.  Maybe we’ll get lucky and a memory test will show something.  Have you run memtest?

No I haven’t 

[Bombastinator]

13 minutes ago, Grenoots said:

No I haven’t 

Try that maybe.  If it spits out that there’s a problem with your memory then there’s a problem with you memory.  Unfortunately if it doesn’t there STILL might be a problem with your memory, though it’s less likely.

[Grenoots]

6 hours ago, Bombastinator said:

Try that maybe.  If it spits out that there’s a problem with your memory then there’s a problem with you memory.  Unfortunately if it doesn’t there STILL might be a problem with your memory, though it’s less likely.

I just did that and it didn’t say there was a problem

[Bombastinator]

24 minutes ago, Grenoots said:

I just did that and it didn’t say there was a problem

Argh.  Well to be fair hopes weren’t super high. If it’s bad memory it’s a subtle problem.  Memtest sometimes misses stuff.

 

Whats next? Drive maybe?  Gawd.  Talking a kid through locking out bad sectors on a hard drive when I’m not totally sure they even work that way any more....

You using windows10? Or something earlier?

[Grenoots]

2 hours ago, Bombastinator said:

Argh.  Well to be fair hopes weren’t super high. If it’s bad memory it’s a subtle problem.  Memtest sometimes misses stuff.

 

Whats next? Drive maybe?  Gawd.  Talking a kid through locking out bad sectors on a hard drive when I’m not totally sure they even work that way any more....

You using windows10? Or something earlier?

I’m on Windows 10 and I’ve tried uninstalling the driver and reinstalling the newest versions and I have installed older versions to try and update those to the latest 

[Bombastinator]

Mmmm... drivers.  There’s this thing called DDU  people really like for driver uninstalls around here.  It’s a free download, but the actual download button is a bit obfusticated.  It’s just a hypertext link iirc amongst a Forrest of big “download” buttons that lead to advertising.  It’s got some pretty hard requirements for using it too if you want it to work right you have to be in safe mode for one thing.  I understand it does the job of correctly removing drivers though which win 10 does not do.

[ReachModifier]

Have you tried using an older version of the driver and not the latest, you could always downgrade a driver or two and see if it works. Because I know a lot of people who stop windows from updating because they don't want to, etc.

[Grenoots]

1 hour ago, ReachModifier said:

Have you tried using an older version of the driver and not the latest, you could always downgrade a driver or two and see if it works. Because I know a lot of people who stop windows from updating because they don't want to, etc.

Yeah I have 

[Grenoots]

On 12/25/2019 at 12:16 AM, Bombastinator said:

Mmmm... drivers.  There’s this thing called DDU  people really like for driver uninstalls around here.  It’s a free download, but the actual download button is a bit obfusticated.  It’s just a hypertext link iirc amongst a Forrest of big “download” buttons that lead to advertising.  It’s got some pretty hard requirements for using it too if you want it to work right you have to be in safe mode for one thing.  I understand it does the job of correctly removing drivers though which win 10 does not do.

I just did that and it still shows code 43

[Bombastinator]

13 minutes ago, Grenoots said:

I just did that and it still shows code 43

Next easiest hope is some kind of hard drive malarkey.   There used to be good ways to test these things when there was stuff still on them. There are probably better ways now.  I kinda want to run the machine not on that hard drive.

...couldn’t be that simple... how is the hard drive connected?  This thing is old enough to be either IDE or SATA.  Is it connected via sata?  Are there other data ports?

[Grenoots]

6 minutes ago, Bombastinator said:

Next easiest hope is some kind of hard drive malarkey.   There used to be good ways to test these things when there was stuff still on them. There are probably better ways now.  I kinda want to run the machine not on that hard drive.

...couldn’t be that simple... how is the hard drive connected?  This thing is old enough to be either IDE or SATA.  Is it connected via sata?  Are there other data ports?

Yeah when I looked it was connected by Sata, the problems started happening when I updated it last so right now I’m remove the last update I made to see if it was caused by the latest update

[Bombastinator]

1 minute ago, Grenoots said:

Yeah when I looked it was connected by Sata, the problems started happening when I updated it last so right now I’m remove the last update I made to see if it was caused by the latest update

A failure point?!  Woohoo!  I was gonna try changing to a different sata port or better yet booting off basically anything else, which wouldn’t actually fix anything but might (maybe kinda for a while) get it going again anyway.  Actually fixing a problem is better though.

[Grenoots]

1 hour ago, Bombastinator said:

A failure point?!  Woohoo!  I was gonna try changing to a different sata port or better yet booting off basically anything else, which wouldn’t actually fix anything but might (maybe kinda for a while) get it going again anyway.  Actually fixing a problem is better though.

It didn’t work

[Bombastinator]

2 minutes ago, Grenoots said:

It didn’t work

Doesn’t mean that wasn’t what caused it.  Win10 has a really obnoxious auto updater and someone isn’t paying enough attention to what it updates.  Or they are, which is more evil.   If it’s win10 that bricked the machine it means there may be nothing at all wrong with the hardware.  Have you tried booting in safe mode?  All drivers disabled?  If that works it’s not a hardware problem.

[Grenoots]

43 minutes ago, Bombastinator said:

Doesn’t mean that wasn’t what caused it.  Win10 has a really obnoxious auto updater and someone isn’t paying enough attention to what it updates.  Or they are, which is more evil.   If it’s win10 that bricked the machine it means there may be nothing at all wrong with the hardware.  Have you tried booting in safe mode?  All drivers disabled?  If that works it’s not a hardware problem.

Yeah I booted in safe mode and used ddu also

[Bombastinator]

52 minutes ago, Grenoots said:

Yeah I booted in safe mode and used ddu also

DDU removes drivers. Next they gotta go back on and hopefully install right.
 

 Seeing stuff online claiming windows10 will throw code 43 errors for driver incompatibility.  That’s really obnoxious of microsoft.  It will apparently do it for ANY piece of hardware.  What doesn’t make sense is that the machine works THEN throws an error in the middle of everything.  If it was a driver incompatibility it wouldn’t work at all from the beginning.  Or at least that’s how it used to be.  Reinstall the drivers removed with DDU and hope stuff works.

 

 I got a nasty feeling this is all microsoft, there’s no hardware fault at all, and that means I’m of very little help.  I saw hardware error codes happening in the middle of a running app on old hardware which should, or at least used to mean hardware failure.  Old hardware failures I can sometimes be of use with. Not even all that often, but sometimes. Windows10 I am not much help with.  It could be microsoft or some driver manufacturer has just decided to stop supporting parts of your system with its latest update.  The machine is apparently just too old.  Like me apparently.  You might be able to find out which parts by pulling up the properties of different drivers and see if there are errors listed.  I dunno if that will work in safe mode or not though.

 

We may be witnessing the end of the life of this computer as a windows machine.  I don’t know.

[Grenoots]

28 minutes ago, Bombastinator said:

DDU removes drivers. Next they gotta go back on and hopefully install right.
 

 Seeing stuff online claiming windows10 will throw code 43 errors for driver incompatibility.  That’s really obnoxious of microsoft.  It will apparently do it for ANY piece of hardware.  What doesn’t make sense is that the machine works THEN throws an error in the middle of everything.  If it was a driver incompatibility it wouldn’t work at all from the beginning.  Or at least that’s how it used to be.  Reinstall the drivers removed with DDU and hope stuff works.

 

 I got a nasty feeling this is all microsoft, there’s no hardware fault at all, and that means I’m of very little help.  I saw hardware error codes happening in the middle of a running app on old hardware which should, or at least used to mean hardware failure.  Old hardware failures I can sometimes be of use with. Not even all that often, but sometimes. Windows10 I am not much help with.  It could be microsoft or some driver manufacturer has just decided to stop supporting parts of your system with its latest update.  The machine is apparently just too old.  Like me apparently.  You might be able to find out which parts by pulling up the properties of different drivers and see if there are errors listed.  I dunno if that will work in safe mode or not though.

 

We may be witnessing the end of the life of this computer as a windows machine.  I don’t know.

I reinstalled the driver but it still showed it, yeah this computer is most likely dying but my friend had offered to sell his pc that he bought last year to me because he bought a new better gaming laptop so I’m probably gonna make some money from work then buy it off him.

[Bombastinator]

Just now, Grenoots said:

I reinstalled the driver but it still showed it, yeah this computer is most likely dying but my friend had offered to sell his pc that he bought last year to me because he bought a new better gaming laptop so I’m probably gonna make some money from work then buy it off him.

The irony is it may work again later.  I was looking up this machine on the dell site and apparently it was ready for death when win7 went down, but they updated some stuff at the very end of win8.1 and it worked fine again.  Apparently they may have broken it recently with the new update.  It may get unbroken again.  It’s 2011-2015 vintage apparently.  Maybe their cutoff is 8 year old stuff.  Means very bad things for my machine.  I got a 2012 motherboard.

[Grenoots]

1 hour ago, Bombastinator said:

The irony is it may work again later.  I was looking up this machine on the dell site and apparently it was ready for death when win7 went down, but they updated some stuff at the very end of win8.1 and it worked fine again.  Apparently they may have broken it recently with the new update.  It may get unbroken again.  It’s 2011-2015 vintage apparently.  Maybe their cutoff is 8 year old stuff.  Means very bad things for my machine.  I got a 2012 motherboard.

Lmao my pc is gonna die in a year then

[Bombastinator]

54 minutes ago, Grenoots said:

Lmao my pc is gonna die in a year then

The one you are looking at buying or the one you got now?  I was wrong about my timing.  My CPU is haswell, but my motherboard I updated and is 2014.  So 2011-2014 parts in my machine.  My machine is probably going to shortly die in fits and starts just like yours is right now.  Really irritating.  The thing is still faster than some newly released CPUs.  I can blow a +5k fire strike.

 

  Not by much and they’re low end CPUs instead of high end ones, but faster.

 

what is the machine you’re looking at buying?

[Grenoots]

4 hours ago, Bombastinator said:

The one you are looking at buying or the one you got now?  I was wrong about my timing.  My CPU is haswell, but my motherboard I updated and is 2014.  So 2011-2014 parts in my machine.  My machine is probably going to shortly die in fits and starts just like yours is right now.  Really irritating.  The thing is still faster than some newly released CPUs.  I can blow a +5k fire strike.

 

  Not by much and they’re low end CPUs instead of high end ones, but faster.

 

what is the machine you’re looking at buying?

The one I have now is going to die most likely because it’s having a lot of problems