BleepingComputer.com: PC restart during DVD burning

PC with XP professionnal.
I experienced sometimes spontaneous restart of my computer (no blue screen, only the black screen and directly the boot) but when I burned a DVD the restart became very frequent (8 over 10 tryings).
I have check the CPU temperature (43°C) and the different voltages which are set at standard values.
I suspect "microswitching off" of the power supply which could be enhanced when the power supply was drained by using HDD + DVD burner...

What is your idea? Some hints?

Difficult issue to solve... Coud the DVD burner be also suspected?

Patch

No answers?

Patch

Your title says one thing, your content seems to say another (IMO).

If the system reboots/crashes during a burn...the logical place to look (IMO) is the software used for the burn.

I suggest that you Disable Automatic Restarts When Windows Crashes - http://www.bleepingcomputer.com/forums/topic74644.html so that a proper error message might be generated.

Once that happens, post it, please.

Louis

Can I pick up this thread? I am having the exact same issue. Running XP burning to DVDs from ULEAD Video Studio 11 without a problem. Then one day I get auto reboots after burning from the program. Each time now the program will allow one single complete perfect burn and as it finishes *reboot*.

I followed the steps above to turn the auto restart off so I culd get the BSOD. Here's the weird part: I had tried to add a firewire burner and then a USB burner (all with firmware update on all 3) the stand alones all had issues and wouldn't complete their burns. After unchecking the auto restart box I did a drag to disk (roxio) and the remote USB drive worked! When I opened Ulead VS11 to make the DVD through there the exact problem occurred and I got the BSOD

BAD_POOL_CALLER

I use Ulead Video Studio 12...but I never burn from it or any video-editor...but you might check that you have applicable updates installed.

My feeling is that all Video Studio programs I have had (5, 6, 8, 9, 10, 12) have momentary RAM management problems from time to time where the program will freeze while dragging clips. I just close the program and that takes care of it...but it's indicative (to me) of possible problems with RAM management.

Or...maybe the C: partition just needs a chkdsk /r and a defrag.

I don't know, it happens on occasion and I suspect that other users have situations like this.

When in doubt, uninstall/reinstall Corel/Ulead Video Studio...and install any applicable updates.

You can also check Event Viewer for errors which might offer clues.

How To Use Event Viewer - http://www.bleepingcomputer.com/forums/topic40108.html

0x000000C2: BAD_POOL_CALLER
A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.

Every video-editor and every burn program...employ drivers. And files become damaged every day, with no warning of such damage.

Louis

Just another update to what I have done so far.....
I tore down the system and re-seated the ram. I am not ready to remove one of the ram cards because I don't know if the PC would start without it, but that may be next.

I powered up and tried to burn a DVD through Ulead VS11 - same problem and same BSOD code as before. Here are the stop codes:
0x000000c2 (0x00000040, 0x000000000, 0x80000000,0x000000000)

AT this point I have disconnected the portable burners.

Thanks for the reply. I was typing the last while that came in.

I ran chekdsk initially at the start of troubleshooting

I have reinstalled 11 twice with the updates

I have never had the freezing issue you describe.

How can I determine if it is one of the drivers, and which ones should I check other that the DVD burner?

Here is a screen shot (attachment) of the "more information section" after the warning "Your computer has had some serious issues"

Thank you for help.

Since you have a .dmp file generated as the result of the error...you can do a search for it...and then apply the following suggestions.

Help Diagnosing BSODs And Crashes (BC) - http://www.bleepingcomputer.com/forums/topic176011.html

Hopefully, analysis will point to a specific driver.

Louis

Here is the report



Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini102909-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Oct 29 13:59:52.408 2009 (GMT-5)
System Uptime: 0 days 0:19:21.168
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {40, 0, 80000000, 0}

Unable to load image cdudf_xp.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cdudf_xp.SYS
*** ERROR: Module load completed but symbols could not be loaded for cdudf_xp.SYS
Probably caused by : cdudf_xp.SYS ( cdudf_xp+13f63 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000040, Attempt to free usermode address to kernel pool
Arg2: 00000000, Starting address
Arg3: 80000000, Start of system address space
Arg4: 00000000, 0

Debugging Details:
------------------


BUGCHECK_STR: 0xc2_40

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: vstudio.exe

LAST_CONTROL_TRANSFER: from 80548c2d to 804f9f43

STACK_TEXT:
ba0783c0 80548c2d 000000c2 00000040 00000000 nt!KeBugCheckEx+0x1b
ba078400 8054b49a 00000000 8054b2e0 840dd000 nt!MiFreePoolPages+0x8b
ba078440 f3a3ff63 00000000 00000000 840dd478 nt!ExFreePoolWithTag+0x1ba
WARNING: Stack unwind information not available. Following frames may be wrong.
ba07846c f3a408ad 000035c1 0000000f 8447e930 cdudf_xp+0x13f63
ba07848c f3a45b55 8447e930 00003800 00000800 cdudf_xp+0x148ad
ba0784f8 f3a31857 8447e930 843eec28 843eec28 cdudf_xp+0x19b55
ba078638 805458c4 f7727d00 804f87ef 84513994 cdudf_xp+0x5857
ba078640 804f87ef 84513994 000a9e7c 85fa3978 nt!KiUnlockDispatcherDatabase+0x1c
ba078658 8054c111 00000000 84513994 00000000 nt!KeUnstackDetachProcess+0x10b
ba0786b0 f3a4f728 843eec28 84513994 843eec28 nt!ExAllocatePoolWithTag+0x7a9
ba078714 f72e6a01 851beebc ba078738 f3a60450 cdudf_xp+0x23728
ba078720 f3a60450 86d61000 8053580d 00000000 fltmgr!FltpInitNameCacheVolumeCtrl+0x23
ba0787b0 804ef19f 86bf7dd8 845137e0 845139d4 cdudf_xp+0x34450
ba0787c0 f72e23a8 852a8020 845137e0 845137e0 nt!IopfCallDriver+0x31
ba078834 f72e27ba 852a8020 845137e0 845139d4 fltmgr!FltpFsControlMountVolume+0x186
ba078864 804ef19f 852a8020 845137e0 845139f8 fltmgr!FltpFsControl+0x5a
ba078874 f72e23a8 85499020 845137e0 845137e0 nt!IopfCallDriver+0x31
ba0788e8 f72e27ba 85499020 845137e0 845139f8 fltmgr!FltpFsControlMountVolume+0x186
ba078918 804ef19f 85499020 845137e0 84513a1c fltmgr!FltpFsControl+0x5a
ba078928 f72e23a8 854e3020 845137e0 854e3020 nt!IopfCallDriver+0x31
ba07899c f72e27ba 854e3020 845137e0 86ba2860 fltmgr!FltpFsControlMountVolume+0x186
ba0789cc 804ef19f 854e3020 845137e0 845137e0 fltmgr!FltpFsControl+0x5a
ba0789dc 80581bc7 00000000 86ba2860 806e6a4c nt!IopfCallDriver+0x31
ba078a2c 804f53e6 c0000001 84521201 00000000 nt!IopMountVolume+0x1b9
ba078a5c 80582bc0 84521220 86ba2860 ba078b90 nt!IopCheckVpbMounted+0x5e
ba078b4c 805bf452 86ba2860 00000000 857453e8 nt!IopParseDevice+0x3d8
ba078bc4 805bb9de 00000000 ba078c04 00000040 nt!ObpLookupObjectName+0x53c
ba078c18 80576033 00000000 00000000 47e3a001 nt!ObOpenObjectByName+0xea
ba078c94 805769aa 0013ef08 c0100080 0013eea8 nt!IopCreateFile+0x407
ba078cf0 805790b4 0013ef08 c0100080 0013eea8 nt!IoCreateFile+0x8e
ba078d30 8054162c 0013ef08 c0100080 0013eea8 nt!NtCreateFile+0x30
ba078d30 7c90e514 0013ef08 c0100080 0013eea8 nt!KiFastCallEntry+0xfc
0013ef00 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
cdudf_xp+13f63
f3a3ff63 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: cdudf_xp+13f63

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: cdudf_xp

IMAGE_NAME: cdudf_xp.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 3fff3e2c

FAILURE_BUCKET_ID: 0xc2_40_cdudf_xp+13f63

BUCKET_ID: 0xc2_40_cdudf_xp+13f63

Followup: MachineOwner
---------

For comparison's sake, I went to the minidump files and debugged the oldest dump file.



Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini062509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Jun 25 09:16:49.473 2009 (GMT-5)
System Uptime: 14 days 7:07:23.666
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {40, 0, 80000000, 0}

Unable to load image cdudf_xp.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cdudf_xp.SYS
*** ERROR: Module load completed but symbols could not be loaded for cdudf_xp.SYS
Probably caused by : cdudf_xp.SYS ( cdudf_xp+13f63 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000040, Attempt to free usermode address to kernel pool
Arg2: 00000000, Starting address
Arg3: 80000000, Start of system address space
Arg4: 00000000, 0

Debugging Details:
------------------


BUGCHECK_STR: 0xc2_40

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: vstudio.exe

LAST_CONTROL_TRANSFER: from 80548c2d to 804f9f43

STACK_TEXT:
b43e93c0 80548c2d 000000c2 00000040 00000000 nt!KeBugCheckEx+0x1b
b43e9400 8054b49a 00000000 8054b2e0 854af000 nt!MiFreePoolPages+0x8b
b43e9440 f374df63 00000000 00000000 854af478 nt!ExFreePoolWithTag+0x1ba
WARNING: Stack unwind information not available. Following frames may be wrong.
b43e946c f374e8ad 00000178 0000000f 83c10020 cdudf_xp+0x13f63
b43e948c f3753b55 83c10020 00000200 00010000 cdudf_xp+0x148ad
b43e94f8 f373f857 83c10020 83c2a030 83c2a030 cdudf_xp+0x19b55
b43e9638 805458c4 f7727d00 804f87ef 83c3f4dc cdudf_xp+0x5857
b43e9640 804f87ef 83c3f4dc 00139f70 85169448 nt!KiUnlockDispatcherDatabase+0x1c
f7727d00 00000000 00000000 00000000 000002e0 nt!KeUnstackDetachProcess+0x10b


STACK_COMMAND: kb

FOLLOWUP_IP:
cdudf_xp+13f63
f374df63 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: cdudf_xp+13f63

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: cdudf_xp

IMAGE_NAME: cdudf_xp.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 3fff3e2c

FAILURE_BUCKET_ID: 0xc2_40_cdudf_xp+13f63

BUCKET_ID: 0xc2_40_cdudf_xp+13f63

Followup: MachineOwner
---------

I am dead in the water here. Can you look at the analysis from the debug? Or was there nothing more in information or direction you can provide?

I don't mind starting this as a new thread, I just need to know.

Thanks.

Take a look, http://forums.support.roxio.com/index.php?showtopic=30180.

Louis

Why did you send me there? There is no resolution for the person with a similar issue as mine. My problem was with burning, but I have not been using Roxio.

Can you tell me anything from the analysis I posted above?
Do you know anyone else who can tell me something from the analysis?

I am deeply sorry...that my inability to solve your situation from afar...is so inept.

My humble apologies that I just can't figure it out...since you seem to think it's so easy, I'm am relatively sure that a little thought on your part will guide you the rest of the way, without my bumbling expectations that you would conclude that maybe...just maybe...you might check to see if that file mentioned in your brilliant analysis...is on your system and possibly damaged.

Since you never mentioned what software you were using, I was hoping that it was Roxio. But....Roxio isn't the only software...oh, forgot...I'm done with that .

As for others...this is s voluntary forum, anyone one with a clue has always had the right to just step in and make constructive comments. I'm sure that someone is waiting to jump in right now.

Hope you get better assistance from whomever...

Louis

No need for apologies - we could both do with a little clearer communication between us.

First, I can't tell if you are just patronizing me by refering to my "brilliant anaysis" because through your posts you seemed to be leading me to a solution (as others have) by sending me to a thread on how to perform a debug and analysis. I don't know if you realized it, but that thread directs the user to then post the findings. Well, that's what I did and that's where I seemed to lose your support. I expected that you were qualified to read that analysis and tell me what it pointed to.

As for not telling you what software I was using to burn...not true! In my earlier post to you, I stated that I was using Video Studio 11 to burn (You told me that you were experienced with this program in other versions, but never used it to burn). I said I had only been successful with "drag and drop" to Roxio, but could not do a full DVD burn.

In conclusion, I appreciate your assistance and my "'tude" in my previous post displayed my frustration with the problem overall. If you felt it was directed towards you - I apologize. My problem is solved and your guidance led me there. Unfortunately, I can't share the solution for others to benefit, because my company's IT person took one look at the debug analysis and quickly did something which fixed the problem. So, for your instruction and patience I thank you.

Keep doing that thing you do. gva