|
Russian Federation4235 Posts
Ok, the problem is as following. I have a machine that has been overrun by viruses, I've cured them all, but it started randomly crashing with BSOD after that.
The error code is 0x0000000A (IRQL_NOT_LESS_OR_EQUAL) which basically means some core process tries to access memory it shouldn't be able to access.
I've ruled out the physical damage to operating memory since the address of the called element is random with each instance of BSOD, it's IRQ2 (no devices can be set on that), read, but it always has the same address for the calling instruction (which happens to be 0x804DC25D), so it's mostly clear that some system component or driver is either corrupt or bugged, generating wild pointers.
It would all be cool (reinstall windows and stuff) but it's not - I would really at all costs try to avoid reinstalling since the system contains alot of applications (VPN, VNC and some other tools) that weren't configured by me, recovering their config might take days.
So, I question you, IT experts - is it possible to recover the failing process with the knowledge of the said calling instruction address? If I know what crashes the system, I will reinstall that specific thing and it will hopefully work.
|
You could try Event Viewer, then find the minidump and logs for the system crash Then try going over the minidump to find the culprit.
|
Russian Federation4235 Posts
Well, the event viewer is mostly useless as it holds the same message as the BSOD had.
Is there any specialized software to examine minidumps?
|
Calgary25991 Posts
Sorry I'll just assume you're crying wolf from now on 
|
That problem is almost definitely driver-related. Not sure what a virus could have done to cause that though.
Anyway, the driver should be mentioned in the BSOD. If so, try replacing it (or at least reinstall it, or maybe upgrade it, or downgrade).
For (much) more detail see http://support.microsoft.com/kb/314063/en
That should be the only thing you need to read.
|
Catyoul
France2377 Posts
|
I had that back when I had 4gb of ram and it keeps giving me that error every now and then.
yanked out one stick and it never happened again. How much RAM do you have?
|
Russian Federation4235 Posts
On October 30 2008 01:02 XCetron wrote:
I had that back when I had 4gb of ram and it keeps giving me that error every now and then.
yanked out one stick and it never happened again. How much RAM do you have?
Don't remember exactly, either 32 or 64 mb.
Just so we avoid more inept advice, IT AIN'T a hardware issue.
This machine has been functioning well for the last N moths with no software (and ofc hardware changes). My best guess is that a virus infested and ruined some kind of driver or a system *.dll which is why everything stopped to function.
|
Supposedly this error can be caused by a lot of things. If it's not a problem with your RAM then it's probably caused by bad drivers. Try wiping them and reinstalling?
|
How about a reinstallation/repair of the OS (without the format)? Should try that. In fact, it's most advisable if updating the drivers doesn't work.
|
On October 29 2008 23:21 Chill wrote:Sorry I'll just assume you're crying wolf from now on
chill is a genius.
|
On October 30 2008 01:17 Durak wrote:
Supposedly this error can be caused by a lot of things. If it's not a problem with your RAM then it's probably caused by bad drivers. Try wiping them and reinstalling?
On October 30 2008 01:24 Aerox wrote:
How about a reinstallation/repair of the OS (without the format)? Should try that. In fact, it's most advisable if updating the drivers doesn't work.
Do people really read the op first before replying?
On October 29 2008 23:02 BluzMan wrote:
...
It would all be cool (reinstall windows and stuff) but it's not - I would really at all costs try to avoid reinstalling since the system contains alot of applications (VPN, VNC and some other tools) that weren't configured by me, recovering their config might take days.
...
On topic, you should go with Catyoul's advice. You need to go over the minidump with a debugger.
Googling "crash analyzer" netted some possible good links:
http://oca.microsoft.com/en/Welcome.aspx
http://www.dumpanalysis.org/blog/index.php/2007/08/29/minidump-analysis-part-1/
|
On October 30 2008 02:47 dyodyo wrote:Show nested quote +On October 30 2008 01:17 Durak wrote:
Supposedly this error can be caused by a lot of things. If it's not a problem with your RAM then it's probably caused by bad drivers. Try wiping them and reinstalling? Show nested quote +On October 30 2008 01:24 Aerox wrote:
How about a reinstallation/repair of the OS (without the format)? Should try that. In fact, it's most advisable if updating the drivers doesn't work. Do people really read the op first before replying? Show nested quote +On October 29 2008 23:02 BluzMan wrote:
...
It would all be cool (reinstall windows and stuff) but it's not - I would really at all costs try to avoid reinstalling since the system contains alot of applications (VPN, VNC and some other tools) that weren't configured by me, recovering their config might take days.
... On topic, you should go with Catyoul's advice. You need to go over the minidump with a debugger. Googling "crash analyzer" netted some possible good links: http://oca.microsoft.com/en/Welcome.aspxhttp://www.dumpanalysis.org/blog/index.php/2007/08/29/minidump-analysis-part-1/
Dude, reinstalling your drivers isn't the same as reinstalling your OS. You won't lose any applications or data.
|
On October 30 2008 03:00 Durak wrote:Show nested quote +On October 30 2008 02:47 dyodyo wrote:On October 30 2008 01:17 Durak wrote:
Supposedly this error can be caused by a lot of things. If it's not a problem with your RAM then it's probably caused by bad drivers. Try wiping them and reinstalling? On October 30 2008 01:24 Aerox wrote:
How about a reinstallation/repair of the OS (without the format)? Should try that. In fact, it's most advisable if updating the drivers doesn't work. Do people really read the op first before replying? On October 29 2008 23:02 BluzMan wrote:
...
It would all be cool (reinstall windows and stuff) but it's not - I would really at all costs try to avoid reinstalling since the system contains alot of applications (VPN, VNC and some other tools) that weren't configured by me, recovering their config might take days.
... On topic, you should go with Catyoul's advice. You need to go over the minidump with a debugger. Googling "crash analyzer" netted some possible good links: http://oca.microsoft.com/en/Welcome.aspxhttp://www.dumpanalysis.org/blog/index.php/2007/08/29/minidump-analysis-part-1/ Dude, reinstalling your drivers isn't the same as reinstalling your OS. You won't lose any applications or data.
Also you can reinstall your os right over your current os and all that resets is microsoft stuff all your apps stay. Just gonna have to reupdate ie wmp etc.
There is a diff from a reinstall and a clean reinstall.
|
Russian Federation4235 Posts
On October 30 2008 03:28 IzzyCraft wrote:Show nested quote +On October 30 2008 03:00 Durak wrote:On October 30 2008 02:47 dyodyo wrote:On October 30 2008 01:17 Durak wrote:
Supposedly this error can be caused by a lot of things. If it's not a problem with your RAM then it's probably caused by bad drivers. Try wiping them and reinstalling? On October 30 2008 01:24 Aerox wrote:
How about a reinstallation/repair of the OS (without the format)? Should try that. In fact, it's most advisable if updating the drivers doesn't work. Do people really read the op first before replying? On October 29 2008 23:02 BluzMan wrote:
...
It would all be cool (reinstall windows and stuff) but it's not - I would really at all costs try to avoid reinstalling since the system contains alot of applications (VPN, VNC and some other tools) that weren't configured by me, recovering their config might take days.
... On topic, you should go with Catyoul's advice. You need to go over the minidump with a debugger. Googling "crash analyzer" netted some possible good links: http://oca.microsoft.com/en/Welcome.aspxhttp://www.dumpanalysis.org/blog/index.php/2007/08/29/minidump-analysis-part-1/ Dude, reinstalling your drivers isn't the same as reinstalling your OS. You won't lose any applications or data. Also you can reinstall your os right over your current os and all that resets is microsoft stuff all your apps stay. Just gonna have to reupdate ie wmp etc. There is a diff from a reinstall and a clean reinstall.
Unfortunately it won't work since it's Windows XP Embedded.
|
|
|
|
|
|
EPT
