Windows XP Crashing BSOD

T

TeknomanIce2000

Posts: 9   +0

• Apr 8, 2008

• #1

Keeps crashing, different stop codes 0x1000000a, 0x10000050, 0x1000000a, 0x100000d1, 0x1000000a, 0x100000d1and the same a few times over. I'm adding an rar file with all the minidumps in it. I've updated my video driver, I've reset my page file. I haven't ran memtest86 in 3 months or so but it checked out last time. I dont have a day and a half to run a full memtest since I use this computer for school, so any ideas?

 

Attachments

• Mini040808-01.dmp

  96 KB · Views: 5
• Mini040508-01.dmp

  96 KB · Views: 5

T

TeknomanIce2000

Posts: 9   +0

• Apr 8, 2008

• #2

Also my system specs are

AMD Athlon XP 2400+ 2GHZ
1GB RAM
GeForce 6600 256MB Driver Version 6.14.11.6921 (nVIDIA Detonator 69.21)
Asus A7N8X Motherboard

old system, I figure it might just be its time but I really dont want to lose it, it still runs fast just has a few problems. Any help would be appreciated

 

T

TeknomanIce2000

Posts: 9   +0

• Apr 8, 2008

• #3

And one more round of dmp files lol -_-

 

Route44

Posts: 12,015   +82

• Apr 8, 2008

• #4

I read all but one of your minidumps and between the codes and Windows core drivers being listed you either have a hardware issue or a corrupted file system. I am more inclined to the former. So...

1. Run a full harddrive diagnostics using your HD diagnostics free utility from your HD manufacturer.

2. Run MemTest for a minimum of 7 passes. Start it after you are finished your homework and leave it run all night as you sleep; check the next morning.

3. Run ChkDsk /f

 

T

TeknomanIce2000

Posts: 9   +0

• Apr 8, 2008

• #5

Also the CPU Diode is at 70C and my CPU is at 63C, I also have about 3GB's free out of 80GB's

 

Route44

Posts: 12,015   +82

• Apr 8, 2008

• #6

How is your airflow? Also, it is time to buy an external harddrive and transfer some of the things you want stored to another place, or at least burn the information to a CD.

You need to free up your harddrive!

 

T

TeknomanIce2000

Posts: 9   +0

• Apr 8, 2008

• #7

airflow isn't too terrible, theres a fan inside there in the back thats broken, been meaning to get it fixed but so far haven't had the time. I applied thermal paste to the heatsink about 6 months ago or so.

 

Route44

Posts: 12,015   +82

• Apr 8, 2008

• #8

As for your cpu temperature check this out: http://www.computerhope.com/issues/ch000687.htm

I'd get your fan fixed. Let us know how the hd diagnostics, MemTest, and chkdsk turned out.

 

T

TeknomanIce2000

Posts: 9   +0

• Apr 13, 2008

• #9

ok ran the HD diagnostics, quick test past, extended test passed. CPU is in nominal temp. I tried to run chkdsk /f but it kept saying its in use by another process says if I want to run on reboot I hit yes, restart, it doesnt run.

Also I cant get into memtest86 when I reboot. Now matter how fast I slam F8 it wont go into advanced windows options. I tried holding F8, I tried pressin F8 as quickly as humanly possible and no dice. Any advice that doesn't involve chucking this thing into oncoming traffic

 

Matthew DeCarlo

Posts: 5,271   +104

Staff

• Apr 13, 2008

• #10

Minidump 032808-01:

BugCheck 100000D1, {1e839007, 2, 1, 300059e0}
Probably caused by : Unknown_Image ( INVALID_CONTEXT )
--------------------------------------------------------------------------
Minidump 033008-01:

BugCheck 1000000A, {fffff981, ff, 0, 804db881}
Probably caused by : ntoskrnl.exe ( nt!KiDispatchInterrupt+d )
--------------------------------------------------------------------------
Minidump 033008-02:

BugCheck 1000000A, {fffff5c4, 1c, 1, 804e3330}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
--------------------------------------------------------------------------
Minidump 033008-03:

BugCheck 10000050, {a750e3e1, 0, bf8011a3, 0}
Probably caused by : win32k.sys ( win32k!TimersProc+45 )
--------------------------------------------------------------------------
Minidump 040108-01:

BugCheck 1000000A, {fffff985, ff, 0, 804db881}
Probably caused by : ntoskrnl.exe ( nt!KiDispatchInterrupt+d )
--------------------------------------------------------------------------
Minidump 040108-02:

BugCheck 100000D1, {17e3e01c, 2, 1, 3021d2f4}
Probably caused by : Unknown_Image ( INVALID_CONTEXT )
--------------------------------------------------------------------------
Minidump 040208-01:

BugCheck 1000000A, {ae, 2, 1, 804f6d50}
Probably caused by : SYMEVENT.SYS ( SYMEVENT+b119 )
--------------------------------------------------------------------------
Minidump 040508-01:

BugCheck 100000D1, {5ba9005, 2, 1, 7c918154}
Probably caused by : Unknown_Image ( INVALID_CONTEXT )
--------------------------------------------------------------------------
Minidump 040608-01:

BugCheck 1000000A, {41694354, 2, 0, 804dbc95}
Probably caused by : ntoskrnl.exe ( nt!KiUnlinkThread+7 )
--------------------------------------------------------------------------
Minidump 040608-02:

BugCheck 10000050, {ffffffdc, 0, 80568717, 0}
Probably caused by : ntoskrnl.exe ( nt!NtSetEvent+9e )
--------------------------------------------------------------------------
Minidump 040808-01:

BugCheck 1000000A, {fffff980, ff, 0, 804db881}
Probably caused by : ntoskrnl.exe ( nt!KiDispatchInterrupt+d )
--------------------------------------------------------------------------

Try tapping delete repeatedly upon starting your PC. This should get you into the BIOS where you can alter the boot sequence (set your optical drive ahead of your HDD) instead of playing with F8 and that pop up menu.

Test your HDD with one of the utilities here.

 

T

TeknomanIce2000

Posts: 9   +0

• Apr 13, 2008

• #11

I used the Western Digital HDD diagnostic tool, it passed. I'm going to do that BIOS thing later tonight when I can. Still no solution to the ChkDsk /f problem, keeps saying The volume is in use by another process.

 

Matthew DeCarlo

Posts: 5,271   +104

Staff

• Apr 13, 2008

• #12

You can't run chkdsk while accessing Windows on that HDD, however, in my opinion there isn't much point in running it if you've tested your HDD with the WD utility.

Next on the list is testing your RAM, as Route44 has made you aware of .

 

C

cpc2004

Posts: 1,994   +0

• Apr 15, 2008

• #13

Your problem may have 2 culprits.

Your windows install Norton AV and NOB32 AV.
nod32drv.sys Fri Feb 09 17:39:19 2007 (45CC4147)
SYMEVENT.SYS Tue Jan 17 03:39:30 2006 (43CBF672)

Two AVs running at the same time may cause unpredicatable problem.


Minidump 033008-02 is crashed at IRQL x'1c' and it is the symptom of hardware error.

BugCheck 1000000A, {fffff5c4, 1c, 1, 804e3330}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

 

T

TeknomanIce2000

Posts: 9   +0

• Apr 16, 2008

• #14

I've had notrton AV uninstalled for quite some time, I only have NOD32

 

K

kimsland

Posts: 13,806   +3

• Apr 16, 2008

• #15

BugCheck 1000000A, {ae, 2, 1, 804f6d50}
Probably caused by : SYMEVENT.SYS

Click to expand...

is to do with Norton, here's the uninstall tool

 

Route44

Posts: 12,015   +82

• Apr 16, 2008

• #16

Norton is notorious on leaving remnants behind even after uninstalling. Even remnants of an antivirus will cause issues when you are running another anti-virus. It takes the tool that kimsland linked you to in order for a complete removal of all things Norton.