Blue screen of death. Urgent help needed.

Make us a list of the programs/devices you need help with and we will assist. I took a try at this one -

DVD MovieFactory for Toshiba: DVD MovieFactory for TOSHIBA Software Informer: Latest version download, news and info about this Ulead Systems, Inc. program.

What I did was paste "DVD MovieFactory for Toshiba" into Google search. You can do this with each one. If you get stuck, just post and we will help.

Very good. I hope you will be BSOD free! Please update us in a couple of days and let us know how your system is running.

Both dumps are error code 19, BAD_POOL_HEADER. Usual causes are device drivers. Unfortunately, the dumps do point to any specific driver.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 84e0d000, 84e0d300, 8600000}

GetPointerFromAddress: unable to read from 82f7f718
Unable to read MiSystemVaType memory at 82f5f160
Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+1b1 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 84e0d000, The pool entry we were looking for within the page.
Arg3: 84e0d300, The next pool entry.
Arg4: 08600000, (reserved)

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

GetPointerFromAddress: unable to read from 82f7f718
Unable to read MiSystemVaType memory at 82f5f160

BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from 82f7f718
Unable to read MiSystemVaType memory at 82f5f160
 84e0d000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 83038a0e to 82f361b6

STACK_TEXT:  
8a93fc4c 83038a0e 84e0d008 e56c6946 000000f8 nt!ExFreePoolWithTag+0x1b1
8a93fc70 8303878d 84e0d038 84e0d020 00000000 nt!ObpFreeObject+0x275
8a93fc84 82e7ff60 00000000 000c0000 00000000 nt!ObpRemoveObjectRoutine+0x5e
8a93fc98 82e7fed0 84e0d038 83048a75 84ec0630 nt!ObfDereferenceObjectWithTag+0x88
8a93fca0 83048a75 84ec0630 84ec0658 82f81680 nt!ObfDereferenceObject+0xd
8a93fccc 82e42f39 84ec0630 00000000 00000000 nt!MiSegmentDelete+0x191
8a93fd28 82e42e51 84be4d48 00000000 54434653 nt!MiProcessDereferenceList+0xdb
8a93fd50 830256d3 00000000 961af231 00000000 nt!MiDereferenceSegmentThread+0xc5
8a93fd90 82ed70f9 82e42d8a 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExFreePoolWithTag+1b1
82f361b6 cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExFreePoolWithTag+1b1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

FAILURE_BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+1b1

BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+1b1

Followup: MachineOwner
---------

Let's try driver verifier and see what that shows us. Driver Verifier - Enable and Disable

Run Driver Verifier for at least 24 hours and use your computer normally. Upload any BSOD's as soon as it is convenient to do so.

Hope you dont mind, but just to add to Carls astute advice

A pooler header issue is a problem with Windows memory allocation. Device driver issues are probably the msot common, but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers. (By theory, RAM problems would be suspect for memory pool issues.

Just a thought, if memory was not checked.

Bottom line, if you did not take a memory test, take one. Its hit and miss, and I could be wrong, but its a thought.

Download memtest86 and test RAM
RAM - Test with Memtest86+