right i have had a look at tysonp's problem here
http://www.d-a-l.com/help/showthread.php?t=19191
and i am experiencing the exact same problems as he is. so i followed all of jephrees steps and found:

9 .dmp files. all in the same format as said miniDATE (eg mini040405-01.dmp) where 04/04/05 was when file created.

now then. event viewer i have exported all the error entries into a text document and saved only the error version of them as there was so many errors. (there should be 2 text documents attatched called error application and error system. which is self explanitory what they are.

i also have un-checked automatically restart.

1) Download and install the
Debugging Tools from Microsoft
2) Download and install this
debugwiz
3) Open the Wiz & Browse to, or paste in the path to, your MEMORY.DMP or latest .dmp file.
4) After the Wiz creates a Text document post it back to this thread.

I will go over your Event Viewer errors this evening.

sorry about posting it as an attatchment but the text is too long for the board (22635 characters long but the board only accepts 20000 characters)

plus my cousin is experiencing similar problems to me. but he cannot access the internet for help. so he asked if you could help him out?

Code:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f89ddf7b, The address that the exception occurred at
Arg3: f8a3871c, Exception Record Address
Arg4: f8a38418, Context Record Address

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
tfsnboio+f7b
f89ddf7b 8b839c010000     mov     eax,[ebx+0x19c]

EXCEPTION_PARAMETER1:  f8a3871c

CONTEXT:  f8a38418 -- (.cxr fffffffff8a38418)
.cxr fffffffff8a38418
eax=00000001 ebx=00000000 ecx=00000000 edx=7eff4048 esi=f89df96c edi=82104b00
eip=f89ddf7b esp=f8a387e4 ebp=f8a38804 iopl=0         nv up ei pl zr na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210246
tfsnboio+0xf7b:
f89ddf7b 8b839c010000     mov     eax,[ebx+0x19c]   ds:0023:0000019c=????????
.cxr
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from f89ddf9d to f89ddf7b

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
f8a38804 f89ddf9d 82104b00 82104c60 82104afc tfsnboio+0xf7b
f8a3881c f880c9ae 82104b00 82104c9c 82104afc tfsnboio+0xf9d
f8a38848 f5702b09 82104b00 f5702b9f 00000000 tfsnifs!UnblockSystemIo+0xec4
f8a388bc f69c4dc7 00000000 82464f48 81ef5480 tfsnopio+0xb09
f8a388d4 f8af1614 00000001 f8a38914 f8af13cd drvnddm!EdmDeviceRefresh+0x81
f8a388e0 f8af13cd 00000001 82d66cd0 81ef5480 sscdbhk5+0x614
f8a38914 f8af1a2f 02ef5480 82464e90 82460320 sscdbhk5+0x3cd
f8a38950 804eddf9 82464e90 81ef5480 81ef5480 sscdbhk5+0xa2f
f8a38960 f89f9b47 81ef55e4 82d13d10 822c9c08 nt!IopfCallDriver+0x31
f8a38980 804eddf9 82d66cd0 81ef5480 82d3c808 PxHelp20+0xb47
f8a38990 f889e3d9 82d5bdf0 f8a389c0 f889e4b0 nt!IopfCallDriver+0x31
f8a3899c f889e4b0 82d5bd38 81ef5480 00000002 ASAPIW2K+0x13d9
f8a389c0 804eddf9 82d5bd38 81ef5480 81ef5608 ASAPIW2K+0x14b0
f8a389d0 f865ebfa 81ef5608 82d5b780 82d139f4 nt!IopfCallDriver+0x31
f8a389f4 82d139c8 822c9b50 81ef5480 00200242 CLASSPNP!ClassDispatchPnp+0x231
f8a38a4c f86d93c4 822d1d18 81ef5480 80521e47 0x82d139c8
f8a38aa4 804eddf9 822d1c60 81ef5480 82266f5c redbook!RedBookPnp+0x354
f8a38ab4 f800262b 82266d40 82266d40 81ef5480 nt!IopfCallDriver+0x31
f8a38acc f8004192 81ef5480 00000000 00000000 Pcatip+0x662b
f8a38b18 f8006b77 81ef5480 81ef5658 82d68bd8 Pcatip+0x8192
f8a38b34 f8001899 02ef5480 804eddf9 82266c88 Pcatip+0xab77
f8a38b9c 804eddf9 822c88a0 81ef5480 f8a38c28 Pcatip+0x5899
f8a38bac 80586d67 822cd5c0 822cd5c0 00000002 nt!IopfCallDriver+0x31
f8a38bd8 80586e8b 822c88a0 f8a38c04 00000000 nt!IopSynchronousCall+0xb7
f8a38c2c 804f5b48 822cd5c0 00000002 00000000 nt!IopRemoveDevice+0x93
f8a38c54 8058899c e384c388 00000015 e36b38b8 nt!IopRemoveLockedDeviceNode+0x160
f8a38c6c 80588a03 824655b0 00000002 e36b38b8 nt!IopDeleteLockedDeviceNode+0x34
f8a38ca0 8058e673 822cd5c0 026b38b8 00000002 nt!IopDeleteLockedDeviceNodes+0x3f
f8a38d34 8058e936 f8a38d70 806d0778 e384b3b0 nt!PiProcessQueryRemoveAndEject+0x76b
f8a38d50 8058ea8f f8a38d70 81e8b1c0 8055a1fc nt!PiProcessTargetDeviceEvent+0x2a
f8a38d74 80533dd0 81e8b1c0 00000000 82dc88b8 nt!PiWalkDeviceList+0xfd
f8a38dac 805c4a28 81e8b1c0 00000000 00000000 nt!ExpWorkerThread+0x100
f8a38ddc 80540fa2 80533cd0 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

So it looks like it crashed while you were unplugging, or powering off an external CDROM drive? Device manager is in the process of removing the device object for it anyhow. It blew up in one of these third party drivers, and because of that, we dont know exactly why it did. This driver is 3 years old though, so theres a good chance the vendor has already fixed the problem.

tfsnboio.sys Tue Aug 20 02:10:46 2002 - looks like a component of DirectCD?

You will need to identify what software this driver came from and look for an update from the vendor.

Go to \windows\system32\drivers or search your hard drive for it. Once you find it, right click on it, properties and that should help you figure it out.

thank you for your help. it was from veritas software and was used for a program called stomp recordnow max which is a burning program that i had on trial but i have recently purchased nero burning prgram. and i have decided to uninstall the program.

again thanks for your help, it is greatly appreciated,