sister Posted August 20, 2008 Share Posted August 20, 2008 Hello all, I've done a search and have read the FAQs but the search results haven't shown me anything that covers this. I created a DVD of home movies from my mini DV camera and used TDA to author. I used ImgBurn to burn to TY DVDrs. These all play fine in my DVD players, thanks! The problem is that when I try to use ImgBurn (2.4.2.0) to create an ISO for storage purposes, the progress bar shows it at 43% and then my computer restarts. After my computer restarts, I check to see the ImgBurn log file but I don't think it created one that reflects what the problem was. This has happened 3 times. I set my computer not to restart if an error occurs and tried again. This time, the progress bar indicated 43% and my computer froze. I waited a bit and then had to hit the reset button. Oddly enough, it appears to have created and ISO file and the size does match that of the original DVD folder... Checking for logs again, I just see where I've opened ImgBurn to check for logs, haha (at least, that's what I think it's showing): ; //****************************************\\ ; ImgBurn Version 2.4.2.0 - Log ; Wednesday, 20 August 2008, 11:14:22 ; \\****************************************// ; ; I 11:14:08 ImgBurn Version 2.4.2.0 started! I 11:14:08 Microsoft Windows XP Professional x64 Edition (5.2, Build 3790 : Service Pack 1) I 11:14:08 Total Physical Memory: 2,094,512 KB - Available: 1,547,800 KB I 11:14:08 Initialising SPTI... I 11:14:08 Searching for SCSI / ATAPI devices... I 11:14:08 Found 1 DVD Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted August 20, 2008 Share Posted August 20, 2008 ImgBurn creates the file of the required size first and then fills it with the data - that way you cut down on fragmentation. So basically, if your machine crashes/reboots then the images will be useless beyond the point it got up to. You might like to examine the (mini)dump file from when the pc rebooted, it should contain info as to which driver bombed out. Link to comment Share on other sites More sharing options...
sister Posted August 20, 2008 Author Share Posted August 20, 2008 ImgBurn creates the file of the required size first and then fills it with the data - that way you cut down on fragmentation. So basically, if your machine crashes/reboots then the images will be useless beyond the point it got up to. You might like to examine the (mini)dump file from when the pc rebooted, it should contain info as to which driver bombed out. Thank you for your reply. I've been trying to use Debug Diagnostic tool but I'm not having much luck with it. My best guess on my problems with that is A: that I don't know what I'm doing with it B: Maybe it doesn't like the XP 64 bit OS. (?) This is all I keep getting from it: The following threads in ImgBurn.exe__PID__4084__Date__08_20_2008__Time_01_52_04PM__546__Manual Dump.dmp are incomplete and also has/have an invalid Thread Environment Block pointer. As a result, the information reported is most likely inaccurate. ( 0 ) 100.00% of threads blocked If call stacks relevant to the problem could not be accurately analyzed due to bad TEB information then a new dump may need to be obtained. DebugDiag failed to locate the PEB (Process Environment Block) in ImgBurn.exe__PID__4084__Date__08_20_2008__Time_01_52_04PM__546__Manual Dump.dmp, and as a result, debug analysis for this dump may be incomplete or inaccurate. It is recommended that you get another dump of the target process when the issue occurs to ensure accurate data is reported Dump.dmp Type of Analysis Performed Hang Analysis Machine Name Operating System Windows Server 2003 Service Pack 1 Number Of Processors Process ID 4084 Process Image C:\Program Files (x86)\ImgBurn\ImgBurn.exe System Up-Time 00:00:00 Process Up-Time 00:00:23 Top 5 Threads by CPU time Note - Times include both user mode and kernel mode for each thread Extended thread information (including thread CPU times) is unavailable in this dump Thread report Thread 0 - System ID 3852 This thread is incomplete and also has/have an invalid Thread Environment Block pointer. As a result, the information reported is most likely inaccurate. Function Source user32!NtUserWaitMessage+15 ImgBurn+3bd2c8 ImgBurn+1f2093 ImgBurn+44ad07 kernel32!BaseProcessStart+28 I guess I'll go ahead and use ImgTool classic for now to create my ISOs. The ISO created with that and then burned w/ImgBurn played perfectly. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted August 20, 2008 Share Posted August 20, 2008 You need to get the machine into the state where it's doing a BSOD, then just examine the latest mini dump from the minidumps folder (i.e. C:\Windows\MiniDump). You might also have a C:\Windows\Memory.dmp file. You want the windows debugging tools from Microsoft for examining the dump file and you examine it via the (obvious) 'open crash dump' option on the 'File' menu. Link to comment Share on other sites More sharing options...
sister Posted August 20, 2008 Author Share Posted August 20, 2008 (edited) You need to get the machine into the state where it's doing a BSOD, then just examine the latest mini dump from the minidumps folder (i.e. C:\Windows\MiniDump). You might also have a C:\Windows\Memory.dmp file. You want the windows debugging tools from Microsoft for examining the dump file and you examine it via the (obvious) 'open crash dump' option on the 'File' menu. Thanks again and so sorry to be such a hemmy but evidently, it's not as simple as that. I've spent all day on this and haven't gotten anything else done and I'm now getting frustrated. I have installed the windows debugging tools from Microsoft and there is some sort of issues about "symbols" and "Debuggee not connected". Also, the latest dump file in the C:\Windows\MiniDump is dated 8/18 (today is 8/20) and I don't have a Memory.dmp file. If there is some sort of exact, easy to follow, step by step instructions for this windbag thing (ha!) I'd be glad to follow it but I haven't been able to google one up yet. Microsoft ® Windows Debugger Version 6.9.0003.113 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini081808-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011ad0c0 Debug session time: Mon Aug 18 20:03:38.640 2008 (GMT-4) System Uptime: 0 days 2:08:12.620 Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ................................................................................ .......................................... Loading User Symbols Loading unloaded module list ............... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff97fff0609b7, fffffadfc53a2370, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Probably caused by : win32k.sys ( win32k+609b7 ) Followup: MachineOwner --------- Edited August 20, 2008 by sister Link to comment Share on other sites More sharing options...
Recommended Posts