DVD2ONE and shrink keep crashing system PLEASE HELP

[lingy]

OK ive changed all the whole system including corsair memory new named psu 50 quids worth 100 for memory swapped mobo,s and 2700xp athlon processors still dvd2one and shrink is crashing my system could this be a graffix card problem im well sick of it now check my profile for system info please please help ive posted this b4 but nobody came to our aid ....could win xp be at fault ive had pro and home yet same probs
thanx in advance


lingy

[spaceman]

U r unlucky both progs crashing ur system.

Well its not XP cos i'm running both progs fine on my XP os.

Sorry don't know how else to help,

[txpharoah]

Clean your registry. Norton WinDoctor.

[lingy]

txpharoah its a new install of windows could this program really help i dont mind paying for it if it works
regards


lingy

[mrbass]

how many memory sticks? If you got two try putting them in slot 1 and slot 3. Also run memtest86.com takes about 20 to 30 mins for one complete pass of all 10 tests.

[lingy]

mrbass why does that memory test go on for hours and yes i always install memory in 1 and 3

[SaSi]

What exactly is the error message you get? Is it a stop error and a blue screen (although I think they turned green in XP). Or is the program terminated because of an illegal instruction?

Additionally, go to Control panel, administrative tools and select Event viewer and view the system and application logs. Crash messages are logged there. Here is an example of a crash of VirtualDUB trying to read a badly created DivX/AC3 file

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 10/7/2003
Time: 9:48:18 πμ
User: N/A
Description:
Application popup: VirtualDubMod.exe - Application Error : The instruction at "0x0046408e" referenced memory at "0x0507fe4e". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program


The message above may seem incomprehensible, however what it means is that the program read unexpected data, went wild and started destroying the stack. So Windows stopped it.

If you get a STOP ERROR, write down the details. There is the stop error number and 3~5 digits within parenthesis. They usually (at least in Win2K) point clearly to something.

[mrbass]

mrbass why does that memory test go on for hours and yes i always install memory in 1 and 3

many places like to burn-in test for 24 hours. If it passes 1 pass (all 10 tests) sucessfully then you should be good to go.

[lingy]

sasi i have done the tests you were advising me to do there doesnt seem to be any answers but the error message is minidump blah blah with total closure of my system and the blue screen does this help you to solve my problemo
regards lingy