Satellite A105-S4284 gets Blue Screen of Death when coming out of standby

Question

MySatellite A105-S4284 runnings Windows XP gets a BSOD after coming out of standby or hibernation. With standby, I'll see the login screen where I enter my password, and then it may show the desktop background or even the open app (Outlook or Word, typically) for a second, afterwhich the BSOC appears. For weeks I was getting a black screen sporadically after standby. Researched the problem and saw recommendations to update BIOS. So I updated the BIOS to the latest version, and then I started getting blue screens of death rather than a black screen. Thought the problem was McAfee, because I'd get crashes right after McAfee became active in the background, sometimes without going into standby. Cancelled McAfee, took it off with the cleaner, used Avast instead, and that seemed to help. But then BSODs came back. I uninstalled non-essential software, clearned registry with CC Cleaner, freed up more HD space and defragged, ran SpyBot, etc - but I still get the BSOD almost every time I go into standby or hibernate. 
The stop messages on the BSOD don't show a driver. and all begin with 0x0000007E (0x000000C5, ... and then differ after that.  One recent one followed with 0x804E13D5, 0xAA6B9B8C, 0xAA6B9888). Does that mean anything?
I've installed Microsoft's debugging tools to look at the dumps after a BSOD. Here is output for two recent crashes. Doesn't point to a driver. NTKRMLMP.exe is what crashes - do I need to replace that from the I386 folder somehow? I did have my Matsu**bleep**a DVD-CD drive suddenly quit a time or two until the computer was restarted. Should I reinstall the DVD driver? Or the graphics driver? Worried that I might break something by doing that. 
Loading Dump File [C:\WINDOWS\Minidump\Mini030809-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sun Mar  8 16:05:07.187 2009 (GMT-5)
System Uptime: 0 days 4:22:53.890
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
BugCheck 1000007E, {c0000005, 804e13d5, a9860b8c, a9860888}
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+7a9 )
Followup: MachineOwner<snip> 
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  <SNIP>
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804e13d5, The address that the exception occurred at
Arg3: a9860b8c, Exception Record Address
Arg4: a9860888, Context Record Address
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!IopfCallDriver+2d
804e13d5 ff548638        call    dword ptr [esi+eax*4+38h]
EXCEPTION_RECORD:  a9860b8c -- (.exr 0xffffffffa9860b8c)
ExceptionAddress: 804e13d5 (nt!IopfCallDriver+0x0000002d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000070
Attempt to read from address 00000070
CONTEXT:  a9860888 -- (.cxr 0xffffffffa9860888)
eax=0000000e ebx=00000001 ecx=87546020 edx=853fe1a0 esi=00000000 edi=f772471c
eip=804e13d5 esp=a9860c54 ebp=a9860ca0 iopl=0         nv up ei ng nz ac po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010292
nt!IopfCallDriver+0x2d:
804e13d5 ff548638        call    dword ptr [esi+eax*4+38h] ds:0023:00000070=????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  2
PROCESS_NAME:  System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1:  00000000
EXCEPTION_PARAMETER2:  00000070
READ_ADDRESS:  00000070
FOLLOWUP_IP:
nt!ExAllocatePoolWithTag+7a9
805517b9 e9e4feffff      jmp     nt!ExAllocatePoolWithTag+0x7bf (805516a2)
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER:  from 804e13d9 to 804e13d5
STACK_TEXT: 
a9860c6c 804e13d9 8753d018 853fe1a0 00000000 nt!IopfCallDriver+0x2d
a9860ccc 805517b9 00000000 00000002 00000000 nt!IopfCallDriver+0x31
a9860dac 80575723 a9f4533c 00000000 00000000 nt!ExAllocatePoolWithTag+0x7a9
a9860ddc 804ec6d9 f7720ce2 a9f4533c 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  nt!ExAllocatePoolWithTag+7a9
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  48a4044a
STACK_COMMAND:  .cxr 0xffffffffa9860888 ; kb
FAILURE_BUCKET_ID:  0x7E_nt!ExAllocatePoolWithTag+7a9
BUCKET_ID:  0x7E_nt!ExAllocatePoolWithTag+7a9
Followup: MachineOwner
0: kd> lmvm nt
start    end        module name
804d7000 806ff000   nt       # (pdb symbols)          c:\symbols\ntkrnlmp.pdb\B883868B88CB415A92EC010CF6A115A52\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: c:\symbols\ntkrnlmp.exe\48A4044A228000\ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Thu Aug 14 05:09:14 2008 (48A4044A)
    CheckSum:         0021B760
    ImageSize:        00228000
    File version:     5.1.2600.5657
    Product version:  5.1.2600.5657
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0401.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   5.1.2600.5657
    FileVersion:      5.1.2600.5657 (xpsp_sp3_gdr.080814-1236)

Answer 1

In safe mode it is not possible to standby. That is disabled. Tried to make it possible with Toshiba's power control service, but it is not available. 
In a new account, the BSOD still occurs. I created a new account, logged out of my account, and went to the new one. Tried standby. It came out of standby for a second and then had the blue screen of death. 
In checking the event manager, I seen errors shortly before crashes sometimes that involve the CD.
So I went to Toshiba.com and downloaded the DVD RAM driver and ran it, reinstalling the driver, and then restarted.  I also saw that there was C-Dilla driver in my drivers. I uninstalled the SafeCast program that I think is associated with C-Dilla, moved the C-Dilla driver out of the drivers to a distant folder, unchecked C-Dilla in MSCONFIG so it won't load (it was still there after removing SafeCast), and then reinstarted. So with a new DVD Ram driver and neutering, I hope, of C-Dilla, I tried things again and the system appeared to be crash free - better than it had been. But then a crash occurred - BSOD - and upon restart, the CD locked up, and crashed again. 
After restarting, there was a new dialog that popped up after Windows launched indicating that there had been an error with SONIC DLA. Before the crash, there was an event n the event viewer:
My last error comes from the Plug and Play Manager:
The device 'MAT**bleep**A DVD-RAM UJ-841S' (IDE\CdRomMAT**bleep**A_DVD-RAM_UJ-841S________________1.60____\5&226f6cf2&0&0.0.0) disappeared from the system without first being prepared for removal.
Hmmm. So things are still vulnerable. Any ideas? Buy new CD drive? Or new computer?