big bad errors, the bunny needs help.

[psychonaut13]

ok, i have a client site to finish, a client site to start, a benefit event to finish planning and i have to design all the promotional materials for the event. i have a lot of shit to do and my machine can't be fucking up on me so i need to get this figured asap.

workin my arse off last night and boom, crash, no warning, nothing. won't restart for shit....tried many times! finally get it to restart this morning and these are the errors in the event viewer from the administrative tools.

if any of you guys know what these errors are and how to fix them, please let me know as i have an ass of work to get done today and tomorrow and a machine that isn't working isn't goin to get me any where near done.

Error code 1000000a, parameter1 00000000, parameter2 00000002, parameter3 00000001, parameter4 804da3d2.

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 30 2c 20 000000,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 31 2c 20 38 30 34 64 01, 804d
0050: 61 33 64 32 a3d2

 

[imported_SuXoR]

:?:

if it wouldn't restart for a day, i am guessing an overheating problem. open her up and give a good blast of canned air

as far as your hex memory dump, i dunno

 

[imported_Godfather]

what is the event ID? Plug it into this website..
http://www.eventid.net/

 

[Puppet]

Forget the event id. This is a bugcheck where a driver made a call that it shouldn't. The last parameter is the offender but in your case it is 804da3d2 which I would bet big bucks is the kernel so that is no help. The hex dump means nothing. It is just the hex equivalent of the text that goes into that event. Since you said this has occurred multiple times, what I would do is check event viewer for every one of these bugchecks and see if the parameters are always the same. If the parameters are always the same then that would indicate to me that it is a driver issue instead of a hardware issue. If it does continue, and the 4 parameters are always the same then a dump analysis needs to be done to determine which driver caused it.

 

[psychonaut13]

ty mr. puppet. how does one perform a "dump analysis"?

 

[(ITI) True Grunt]

Hopefully you wipe yourself first and than check your toilet by feeling through your shit :lol: :lol:

TG

 

[psychonaut13]

just happened again. rebooted fine though.

the category and event id are the same... 102 and 1003 respectively. but parameter 4 has changed to 821273dc

 

[Puppet]

You need to make certain you have full dump selected, and you probably don't. Right click "My Computer" and select properties and then choose Advanced and then Startup and Recovery Settings. Verify that "Complete memory dump" is chosen in the "Write debugging Information" box. Then the next time it happens the dump will be created here:

c:\windows\memory.dmp (Windows could be Winnt)

Zip the dmp file and send it to me.

 

[psychonaut13]

will do, ty sir

 

[psychonaut13]

when i go to set those settings it says... "if the pagefile on valume C: has an intial size of less than 511 megs, then the system maybe not be able to creat a debgging information filie if a STOP error occurs. Continue anyway?"

i'm going to click yes. and check back here later.

 

[Puppet]

It has to have enough room to dump the page file to disk. Just make sure your page file is on C:\pagefile.sys and that you have enough free space to accomodate a c:\windows\memory.dmp that is 511mb. That dump is small enough to zip down to like 50mb or less. Don't forget that the important thing is to check all of the events that have a 1000000A bug check to see if they have the same parameters or close, which would indicate a driver problem.

 

[Fiero]

ok i tired to follow you guys... wow I"M LOST you guys are smart!!!

 

[psychonaut13]

it's mr. puppet that knows what he's doing. i'm just learning.

 

[CuRRyINaHuRRy]

I would say reformat your system after you are done with your work so it won't happen again.

 

[Puppet]

I looked at your memory dump. Do you have something set up as an alternate to the standard Windows Xp startup screen? It looks like bootvid.sys tried to call memory that it shouldn't. As the computer is loading up press F8 and you should get a menu. Try using "last known good" first to see if it solves it. If it doesn't then reload again with F8 and this time choose safe mode. If it comes up then I want logs. When you get to that spot IM me and I will help you get them.