Alway get BSOD finalizing DVDs with Sonic DLA

Dell INSPIRON 6000
June 9, 2010 at 19:54:01
Specs: Microsoft Windows XP Professional, 1.595 GHz / 1015 MB
For the past 9 months, I have been plagued with the Blue Screen of Death after finalizing any DVD. I use Sonic DLA on my Sony DVD DW-Q28A. As long as I don't write to the DVD it works fine for reading. (My recollection is that I also get the Blue Screen whether or not I finalize the DVD.) I have been unable to find a later version of the DVD driver on the Net.

In frustration, I purchased an external DVD R/W in the hope that this would solve the problem. Much to my surprise, the first time I finalized a DVD created on the external DVD drive, I again received the Blue Screen.

Seems to me that the this points to the Sonic software. Any suggestions for a solution would be much appreciated.

Thanks,

Steve


See More: Alway get BSOD finalizing DVDs with Sonic DLA

Report •


#1
Report •

#2
June 10, 2010 at 08:21:53
Thanks for your response and the links to BlueScreenView. After downloading and running it, I see that most of the incidents highlight the file FLTMGR.SYS and NTOSKRNL.EXE in the lower half of the screen. The file HAL.DLL is also highlighted often.

This is certainly the most solid clue I've had in months. As BlueScreenView appears to merely identify these files (a welcome identification), the next step is unclear. Is it possible to boot in safe mode and merely copy these files from the install disks to the appropriate location? Or is there more to this than meets the eye? What if these files have been updated by Microsoft's system updates since the install? How would I then get the latest files?

Thanks for your help.

Steve


Report •

#3
June 10, 2010 at 16:49:39
Googling > NTOSKRNL got this as a possible fix.

http://support.microsoft.com/defaul...

This issue may occur if the Hal.dll and Ntoskrnl.exe files are mismatched.

To resolve this issue, start your computer from the Windows CD, and then perform an in-place upgrade of Windows. For additional information about how to do so, click the following article number to view the article in the Microsoft Knowledge Base:
315341 (http://support.microsoft.com/kb/315341/ ) How to Perform an In-Place Upgrade (Reinstallation) of Windows XP
http://windows.microsoft.com/en-us/...



Report •

Related Solutions

#4
June 10, 2010 at 16:58:38
The next step is here, make sure you have backed up all your important stuff, address book etc.

http://support.microsoft.com/kb/978788


Report •

#5
June 11, 2010 at 04:57:25
Yikes! After reading the references to the solution you cite, maybe I can live with the BSOD! Looks like I'll have to set a day aside in order to implement this fix. And then I'm concerned about the use of your phrases like "possible fix" and "may occur" [because of mismatched files].

If I understand your response correctly, I can spend the better part of a day performing an in-place Windows upgrade and this MIGHT solve the problem? And if the basis for this procedure is "mismatched files", since Microsoft files performs all of my system updates, how can the files become mismatched?

I sincerely appreciate your responses to this problem as I had no place to turn for its solution. Now I have at least a possible solution, but I wonder if the cure is worse than the disease. I do have some reservations about proceeding with a procedure that will take much of a day when there is only a "chance" of success. In the simplest of terms, I can reboot from BSODs a lot of times in the duration it would take me to eliminate the BSOD from this problem. If I took my PC into a shop and had them do it, I may be money ahead buying a new PC.

Thank you for this solution. I now have to mull over how to proceed.

Steve


Report •

#6
June 11, 2010 at 05:28:20
Does this minidump output from the BlueScreenViewer of my latest BSOD either corroborate or negate the potential solution?
==================================================
Dump File : Mini060810-03.dmp
Crash Time : 6/8/2010 3:31:33 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x804eca10
Parameter 3 : 0xf7962c2c
Parameter 4 : 0xf7962928
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+17b6c
File Description : Microsoft Filesystem Filter Manager
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini060810-03.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================



Report •

#7
June 11, 2010 at 06:07:47
With millions upon millions of problems on computers, no one can know them without referring to google, which is what I have been doing.

This is part of basic maintenance on Windows when things go wrong, you run Check Disk.

How to Use Chkdsk in Windows XP
http://vlaurie.com/computers2/Artic...
http://www.qbs-pchelp.co.uk/chkdsk....
http://en.wikipedia.org/wiki/Chkdsk
http://en.wikipedia.org/wiki/CHKDSK
http://www.schrockinnovations.com/c...
Troubleshooting Disks and File Systems
http://technet.microsoft.com/en-us/...

If you still have problems after running CHKDSk, it's back to google.

0x1000007e

http://www.google.com.au/#hl=en&sou...


Report •

#8
June 11, 2010 at 09:55:05
Thanks, John, for the links. Been through the CHKDSK already but I'll try further research on your suggested links.

Steve


Report •


Ask Question