Bsod
Thanks Duracell,
the BSOD occured a few times when I was trying to write data to my DVD writer
(I was trying to backup my ghost file, thankfully since joining this forum I saw a thread that reminded me Ghost 2003 writes directly to DVD drives from it's DOS back-up operations, so I have since performed my back up in Ghost with no trouble) The thing I am concerned about is what will happen when I try to back-up other data (such as my Digital Photos)
Initially (when I first got the DVD burner and installed it's software I had managed to do a small test DVD movie of my kids from a couple of small movies taken with my digital camera, using the software provided with the Pioneer A07 bundle (U-lead DVD stuff and also Media-chance DVD lab) that went ok (except for some missing audio, but I'm sure thats because I had different audio formats in the project, I was just testing the software out really...)
As I said the problem was trying to write data with Ulead's Burn.Now. The operation would get part way through and then the BSOD would rear its head.
I got varying messages on the BSOD for the repeated attempts I made:
BAD_POOL_CALLER
** STOP: 0x000000C2 (0x0000007, 0x000000CD4, 0xB7FFB7FF, 0XE1298008)
PFN_LIST_CORRUPT
** STOP: 0x00000099, 0x00000000, 0x00000000, 0x00000000)
IRQL_NOT_LESS_OR_EQUAL
** STOP: 0x0000000A (0xFFBE0000, 0x00000001, 0x00000000, 0x804F2982)
(my apologies if you don't need all these strings, I'm not sure how detalied I should get) - eventually (after a few of tries) on rebooting, the system told me it couldn't find WINDOWS/SYSTEM/CONFIG which I sort of guessed was not a good thing...I couldn't get the system to run after that so had to fdisk, format and "re-ghost" to an older version of my C drive. I was a bit nervous to try anything more after that...
I was not sure why I was getting different BSOD messages each time, or why the burn would sometimes get (or seem to get) nearly all of the way through before crashing, and sometimes crash soon after the burn started...?
Note that this was before I used forced ASPI after discovering that stuff here, I did notice that when I used the dumpASPI to back up the original ASPI the same file names (WOWPOST.EXE etc) were in the dump as what force ASPI installed. Are these just different versions of the same exec's or is it possible the software I installed (either the mediachance or Ulead installed these during those programs set-ups?)
One other thing I have noted that may or may not have anything to do with anything is that when setting up my devices as recommended here, is that when I go to exit the device manager after changing details I get this message:
mmc.exe The Instruction at "0x77f516c5" referenced memory at "0x008a0010" The memory could not be "read"
On checking, the changes I have made are still there, but I don't know what that message means... (I don't know much of anything really do I? LOL)
My system information:
AMD Duron 800mhz processor
917,504 K PC133 RAM
80GB MASTER 40GB SLAVE HD's on the primary channel and
A07 DVD burner (MASTER) and Creative 12 10 32x CD Burner (SLAVE) on 2nd channel.
As far as other hardware, I also have a Matrox G550 dual head graphics card in the AGP slot and a USB 2.0 x 4 Hub in one of my other PCI slots with scanner, ADSL modem and Wacom tablet - along with digital camera USB cable (not always connected to camera of course) connected...
Once again, I'm sorry if I'm being too verbose with all this info, but I guess it's better to provide too much info than not enough...
Thanks for your patience reading this!