Error code 1000000a, parameter1 00000008, parameter2 00000002, parameter3 00000000, parameter4 804e4a6e.

Running: WinXP SP3

I have been getting random reboots for a while now (several months) and have been unsuccessful in trying to fix it. It has been getting progressively worse until this week. Here's what I've done in that time and the results:

1. Uninstalled my AV at the time (McAfee) and replaced it with a different one (AVG). (McAfee was sucking and managed to let in a virus my first day of owning my brand-new machine. I got that sorted out.) This seemed to help a little bit for a short while, but I think that was a fluke.

2. Run multiple virus and spyware scans (AVG and Spybot S&D). I am clean. I have continued scanning on a regular basis. I do update frequently as well.

3. Checked my BIOS to make sure I was not overclocked.

This week:

4. Tracked down one particular error message I'd received and read that it was a ZoneAlarm error. I subsequently removed it from my system and I have gone from increasingly frequent reboots (reaching a peak of almost once every 45 minutes or so) to rebooting an average of once per 24 hours. This is an IMMENSE  improvement, but obviously still not ideal, particularly as I work from this machine.

5. Adjusted my virtual memory (initial) from its previous setting to the recommended setting. I powered off, powered on, and it seemed to boot fine -- but I had an error as though I'd rebooted randomly, as well as an error message. It did not reboot during startup.

Actions recommended but not yet taken:

1. RAM test. I have downloaded the .iso but have not tracked down my CD-Rs. All of my belongings are packed from a recent move.

2. Booting from CD to see if it's a hardware or software problem. Again, my belongings are packed and I have not tracked my CD-Rs so I cannot burn Ubuntu to disk yet.

3. Adjusted the memory dump from a minidump to a full dump (this seemed questionable?)

Additional Details:

This is a reasonably new machine, built for me just a few months ago. There are some gently used components, including the motherboard, but everything was working fine at the time it was built and should not be anywhere near dead. No overheating here, and it's a new power supply, so those shouldn't be the cause. The guy who built my machine said he experienced no reboots. I am not sure if the reboots could be the result of a sudden hardware failure, as it seems unlikely, or possibly the virus picked up before these problems began. My system is clean and I received professional assistance in removal so it *shouldn't* have had anything to do with it, but I'm including the information just in case because ... let's face it ... I am stumped at this point. Just way out of my league.

It does not seem related to any programs I am running. It does seem to reboot more if I am playing games (Flash and Shockwave are mostly what I'm playing because ... my belongings are still packed so I haven't installed my games on this computer.) It will sometimes reboot DURING a reboot.

 

If you have any questions for me, ask away. I am desperate to get this thing in full working order.

 

Question Info


Last updated August 22, 2019 Views 23,838 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

"mbif" wrote in message news:edbad169-7480-4b0a-8d54-236f772a7053...
> Running: WinXP SP3
>
> I have been getting random reboots for a while now (several months) and
> have been unsuccessful in trying to fix it. It has been getting
> progressively worse until this week. Here's what I've done in that time
> and the results:
>
> 1. Uninstalled my AV at the time (McAfee) and replaced it with a different
> one (AVG). (McAfee was sucking and managed to let in a virus my first day
> of owning my brand-new machine. I got that sorted out.) This seemed to
> help a little bit for a short while, but I think that was a fluke.
>
> 2. Run multiple virus and spyware scans (AVG and Spybot S&D). I am clean.
> I have continued scanning on a regular basis. I do update frequently as
> well.
>
> 3. Checked my BIOS to make sure I was not overclocked.
>
> This week:
>
> 4. Tracked down one particular error message I'd received and read that it
> was a ZoneAlarm error. I subsequently removed it from my system and I have
> gone from increasingly frequent reboots (reaching a peak of almost once
> every 45 minutes or so) to rebooting an average of once per 24 hours. This
> is an IMMENSE improvement, but obviously still not ideal, particularly as
> I work from this machine.
>
> 5. Adjusted my virtual memory (initial) from its previous setting to the
> recommended setting. I powered off, powered on, and it seemed to boot
> fine -- but I had an error as though I'd rebooted randomly, as well as an
> error message. It did not reboot during startup.
>
> Actions recommended but not yet taken:
>
> 1. RAM test. I have downloaded the .iso but have not tracked down my
> CD-Rs. All of my belongings are packed from a recent move.
>
> 2. Booting from CD to see if it's a hardware or software problem. Again,
> my belongings are packed and I have not tracked my CD-Rs so I cannot burn
> Ubuntu to disk yet.
>
> 3. Adjusted the memory dump from a minidump to a full dump (this seemed
> questionable?)
>
> Additional Details:
>
> This is a reasonably new machine, built for me just a few months ago.
> There are some gently used components, including the motherboard, but
> everything was working fine at the time it was built and should not be
> anywhere near dead. No overheating here, and it's a new power supply, so
> those shouldn't be the cause. The guy who built my machine said he
> experienced no reboots. I am not sure if the reboots could be the result
> of a sudden hardware failure, as it seems unlikely, or possibly the virus
> picked up before these problems began. My system is clean and I received
> professional assistance in removal so it *shouldn't* have had anything to
> do with it, but I'm including the information just in case because ...
> let's face it ... I am stumped at this point. Just way out of my league.
>
> It does not seem related to any programs I am running. It does seem to
> reboot more if I am playing games (Flash and Shockwave are mostly what I'm
> playing because ... my belongings are still packed so I haven't installed
> my games on this computer.) It will sometimes reboot DURING a reboot.
>
>
>
> If you have any questions for me, ask away. I am desperate to get this
> thing in full working order.
>
 
 
Have you run the specialist cleaner tools to remove the last traces of
McAfee and ZA?
http://service.mcafee.com/FAQDocument.aspx?id=TS100507
http://download.zonealarm.com/bin/free/support/cpes_clean.exe
 
There's often rubbish left behind by major apps such as these.
 
I'd set your VM to be between 1000MB and 2500MB - or fix it at 1500MB. (you
didn't say how much physical RAM you have). Since you say you have a Ubuntu
disk - it may be worth booting to that, and deleting the pagefile.sys to
force a rebuild of the page file.
 
 
Random Reboots are a b***r to isolate and fix, unless there's an entry in
Event Viewer - you didn't mention anything. Is this because there's north
there, or have you not looked?
 
--
Noel Paton
CrashFixPC
 
Nil Carborundum Illegitemi
www.crashfixpc.co.uk
 
 
Noel Paton
Nil Carborundum Illegitemi -
No, I don't work for Microsoft!
http://www.crashfixpc.co.uk

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Have not used the specialty cleanup tools -- will give those a shot next. Don't have Ubuntu to disk yet, but will as soon as I unpack my stuff.

 

Event Viewer info is what's in the title, but I'll give the complete deal here:

Category: (102)

Event ID: 1003

 

Error code 1000000a, parameter1 00000008, parameter2 00000002, parameter3 00000000, parameter4 804e4a6e.

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 30    1000000
0020: 61 20 20 50 61 72 61 6d   a  Param
0028: 65 74 65 72 73 20 30 30   eters 00
0030: 30 30 30 30 30 38 2c 20   000008, 
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 38 30 34 65   00, 804e
0050: 34 61 36 65               4a6e    

EDIT: Ran the McAfee removal tool and it was successful. If I try to run the ZA removal tool, though, it doesn't do anything (or at least that's how it looks.)

 

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

"mbif" wrote in message news:fad4b2ec-a787-4851-b20a-c6a6e75f619e...
> Event Viewer info is what's in the title, but I'll give the complete deal
> here:
>
 
Event ID 1003 - that's what I wanted :)
 
Coupled with the code 1000000a - we get an "IRQL_NOT_LESS_OR_EQUAL" error
This sort of error is usually from device drivers (don't forget that
software can also be a 'device').
First thing is to check Device Manager in Normal Mode - make sure that
Hidden Devices are enabled
Is there anything that shows with a yellow or red 'bang'??
 
--
Noel Paton
CrashFixPC
 
Nil Carborundum Illegitemi
www.crashfixpc.co.uk
 
 
Noel Paton
Nil Carborundum Illegitemi -
No, I don't work for Microsoft!
http://www.crashfixpc.co.uk

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Can you please upload the contents of c:\windows\minidump to your SkyDrive and provide a link.


For dealing with Blue Screens, general guidance follows (you may already have seen some of it):

Consider running chkdsk on all partitions.  Let chkdsk complete on each partition and see if that helps.

Also consider running SFC /SCANNOW.

Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're  using the latest BIOS.

Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily  good memory - it just hasn't failed a test.  Consider systematically eliminating RAM from the system - run with a couple of  modules for a while, and see how things go. Then try the other modules.

If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?

It can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out  of the dialog.

Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot  completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

Wait for a bugcheck to occur after enabling verifier as described, and then upload it to your SkyDrive, and provide a link.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Noel -

Device Manager shows everything normal, but a red X over 1394 Net Adapter. It's disabled.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

No.Compromise -

c:\windows\minidump is full of a TON of files. If I need to upload all of them, it will have to wait until tonight as I have ridiculously strict data transfer limits (I'm on satellite internet due to living in a rural area -- we don't even have a phone.) If I reboot before then I will upload the newest dump file and link you.

Ran chkdsk in read-only mode and when it was done there were no results and I was unable to find any correlating event viewer events for it. Is there a file saved somewhere?

Do not have a SP3 disk onhand. Will need to borrow one if I want to run SFC /SCANNOW

I read that I need to have a boot disk if I want to use Driver Verifier -- true? False?

With regards to whether I get bugchecks in safe mode, I have not checked yet. I am not constantly rebooting anymore after the removal of ZA so it could take a full day of just waiting around in Safe Mode and I just plain don't have the time to do that at this point. I work online. I will try testing that tomorrow if all else fails -- I can leave it running in Safe Mode while we go do the Mother's Day thing. It can and does reboot when absolutely nothing is going on so it should be a reasonably effective test.

Sorry for the inexperience on my end. This is a level of technicality I'm just not used to.

 

EDIT: I seem to be running a 32-bit Windows on a 64-bit processor. Could that be a problem? AMD's website says to make sure all drivers installed on a 64-bit processor machine are 64-bit.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

"mbif" wrote in message news:e817daa9-27b9-4f38-a499-635a8d336777...
> Noel -
>
> Device Manager shows everything normal, but a red X over 1394 Net Adapter.
> It's disabled.
>
 
That makes sense - I usually disable that one as well :)
OK - we'll wait for No.Compromise to have a look at the dump (not my
speciality, so I may learn stuff here as well !)
 
--
Noel Paton
CrashFixPC
 
Nil Carborundum Illegitemi
www.crashfixpc.co.uk
 
 
Noel Paton
Nil Carborundum Illegitemi -
No, I don't work for Microsoft!
http://www.crashfixpc.co.uk

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

You can ZIP the minidump folder so the files are compressed, and you have less work to do, at your convenience of course.

No boot disk is needed for verifier.  It would be goot to test that you can successfully boot into safe mode before enabling verifier, but if you can't it would seem that there may be larger problems with the system... 

There should be no problem running a 32-bit (x86) version of windows on a 64-bit processor.  On a 64-bit OS, all kernel mode drivers are required to be 64-bit - that is likely what the website was making reference to.

Chkdsk (when run with /f or /r) records interesting details to the Application event log with a source of winlogon, event id 1001.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

http://cid-61002a907bc07516.skydrive.live.com/self.aspx/Minidumps/minidumps.zip

 

Hopefully that's the right URL. All of them bundled into one .zip

 

Went all that time without another reboot, too. So close, but another one happened this evening. Haven't yet had a chance to test in safe mode.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Have you turned verifier on? The dumps indicate memory corruption is occurring and verifier can help with that - it can cause a bugcheck when the corruption takes place (catching the corruptor) rather than when the corruption is detected (at which point the corruptor may be long gone).

You have the problems with McAfee as well as AVG? It would be interesting to note the behavior with yet a different AV / security product installed in place of AVG - e.g. Microsoft Security Essentials.

Checking in safe mode and with a clean boot would be good to do as well - may help determine if the behavior is related to faulty hardware, or software...

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.