When exiting CDRWin I get BSOD....Any help.

[NeWcS]

For the most part my system is pretty solid(Knock on wood). Although sometimes after buring w/ CDRwin and I hit exit I get a BSOD. Im wondering if this is a driver problem, software problem or what. Im not at home right now so I can't give you the version of cdrwin.. Also as far as I know I have the most current ASPI.

Any other info would be great.

Duron 1.2ghz
512mb pc133
Plextor 8/4/24
Nvidia GF2 mx 32mb
etc. etc. etc.

[NeWcS]

CDRWin 3.8f
ASPI 4.60

[mikerios]

the last build of cdrwin that i used was 3.8d and found it rock solid, never tried the f version. interesting you got the plextor too as it should give you no issue with cdrwin what so ever ( my 2 plextors don't ), so all I can think of is do you have ezcd installed? also one last thing, a while back I had a brand new mobo, and it came with new ide cables ( the ata 66/100 kind ), one thing it had that I did not notice, was it ( the cables ) had a very fine hole across the ribbon. The end result was the computer would boot up and such and run, but disk intensive activity would casue random lock ups, bsd and the occasional reboot. Replacing the cable fixed all that.

[Morheus]

What's ur Oper system Win 9.X, Win2000, ME , XP or non-bill gates?

If you r running one of the latter O/S'es check your page file and your cache.
Make sure your page file meets the min requirements if ur running NT 4.0 or 5.0 I'm not sure about XP ... (I don't love XP YET!)
example 512mb ram = page file min. 524mb
Here's another little hint that alot of people don't know about use a software app that will really clean and wash your program files i.e. Temp file directories , document history, Explorer , media player ...
I don't know if i'm allowed to mention software by name

This is all more important if ur beginning to run at less than 20% free space on your system files hard drive.

p.s.
Don't forget to do a back up b4 cleaning

Tony

[dltf90]

Do not use the latest version of Plextor PlexTools! It has a well documented affect of killing CDrWin. If you uninstall Plextor Plextools it will work just fine. I had to go back to the first release of Plextools 2000 and it doesn't kill my system. I then upgraded to the latest version, it kills with a BSoD. I then uninstalled the latest version and everything works fine. I've submitted the defect to Plextor and Goldenhawk, but I haven't seen anything yet. I'm a Software Quality Engineer, so this kind of stuff comes naturally to me Hope this fixes your problem as it is rather obscure.

[NeWcS]

1) No I don't have chEZe-e cd Crator on my system never have never will!!!

2) Im running XP pro.

3) I've never had PlexTools installed on my system....should I????

As far as the memory managment I let Windows handle it. Im running 512 of pc133. If someone thinks it will help and willing to tell me how to...... hook it up(directions). I like to think I know a shit load about computers but the memory thing I never really took the time to learn.

-Thanx guys.gals

[dltf90]

1) No I don't have chEZe-e cd Crator on my system never have never will!!!

2) Im running XP pro.

3) I've never had PlexTools installed on my system....should I????

1. That is very good to hear, you are already improved your computer by never installing it.

2. Have you tried running the application in W2k compatibility mode? MKW (shn util) was one such case. Didn't work in WinXP unless you switched it to Win2k compatibility mode. I don't have XP with me this weekend, but when I get home Monday I can play with it and see if I get the same error as you.

3. If you don't see a blue "P" icon in you system tray, that eliminates one possible problem. In reality the first iteration of the PlexTools was incredibly useful. Later iterations dropped a great feature for CDDB capabilities.

[mikerios]

have you tried going back a build to 3.8d ? you can get it at www.cdrsoft.cc as they keep older builds of software.

[NeWcS]

Just happened again: Something a about 'Bad Pool Caller'???


Thanx