Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD when burning disks


  • Please log in to reply
9 replies to this topic

#1 cumbiebob

cumbiebob

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:05:42 AM

Posted 25 October 2010 - 03:01 PM

Hi Folks

I am running OEM version of Windows XP with SP3 installed in the last couple of weeks I have been receiving a BSOD whenever I try to burn a CD from Itunes or Pinnicle software that I have on my machine. I can read and copy from the CD drive but not write to it.

It may be coincidental but I think it started after I installed OVISUITE for my Nokia phone but even uninstalling that doesn't help.

I followed the instructions on the board and attach the following minidump from the latest crash:


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


Loading Dump File [C:\WINDOWS\Minidump\Mini102310-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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.100427-1636
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Sat Oct 23 14:24:55.203 2010 (UTC + 1:00)
System Uptime: 0 days 2:04:37.767
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 806d2753, a6211488, 0}

Unable to load image bdfsfltr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bdfsfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfsfltr.sys
*** WARNING: Unable to verify timestamp for AVGIDSFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.sys
Probably caused by : bdfsfltr.sys ( bdfsfltr+9c3f )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 806d2753, The address that the exception occurred at
Arg3: a6211488, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
hal!ExAcquireFastMutex+f
806d2753 ff09 dec dword ptr [ecx]

TRAP_FRAME: a6211488 -- (.trap 0xffffffffa6211488)
ErrCode = 00000002
eax=00000000 ebx=00000000 ecx=00000001 edx=88940de0 esi=88698b68 edi=8899fb80
eip=806d2753 esp=a62114fc ebp=a621150c iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
hal!ExAcquireFastMutex+0xf:
806d2753 ff09 dec dword ptr [ecx] ds:0023:00000001=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: iTunes.exe

LAST_CONTROL_TRANSFER: from 804ec7f0 to 806d2753

STACK_TEXT:
a62114f8 804ec7f0 8899fb80 00000000 00000000 hal!ExAcquireFastMutex+0xf
a621150c b9ebef56 88698b68 886be638 00000000 nt!FsRtlLookupPerStreamContextInternal+0x14
a6211570 b9eb9bc4 886be638 8899fb80 00000000 fltmgr!FltpGetStreamListCtrl+0x5a
a621158c b9e6ac3f 88940de0 8899fb80 a62115c4 fltmgr!FltGetStreamContext+0x1a
WARNING: Stack unwind information not available. Following frames may be wrong.
a62115e0 b9e615c1 88a5ef5c a6211690 00000000 bdfsfltr+0x9c3f
a6211670 b9eb9888 00000b24 a6211690 a62116c0 bdfsfltr+0x5c1
a62116d0 b9ebb2a0 00211718 886c5fd8 a6211718 fltmgr!FltpPerformPreCallbacks+0x2d4
a62116e4 b9ebbc48 a6211718 00000000 88a46178 fltmgr!FltpPassThroughInternal+0x32
a6211700 b9ebc059 a6211718 886c5dc8 8ac7eba8 fltmgr!FltpPassThrough+0x1c2
a6211730 804ee129 88a46178 886c5db8 89448a20 fltmgr!FltpDispatch+0x10d
a6211740 addfb855 8899fb80 886c5fd8 a6211794 nt!IopfCallDriver+0x31
a6211750 804ee129 8875f020 886c5db8 886c5db8 AVGIDSFilter+0x4855
a6211760 80578dae 8899fb68 8ace1040 8899fb80 nt!IopfCallDriver+0x31
a6211794 805b21d4 88eedba8 8875f020 00120089 nt!IopCloseFile+0x27c
a62117c4 805b1b01 88eedba8 00000001 8ace1040 nt!ObpDecrementHandleCount+0xd4
a62117ec 805b1b9f e3325800 8899fb80 00000224 nt!ObpCloseHandleTableEntry+0x14d
a6211834 805b1cd7 00000224 00000001 00000000 nt!ObpCloseHandle+0x87
a6211848 8053d668 00000224 0012d820 7c90e514 nt!NtClose+0x1d
a6211848 7c90e514 00000224 0012d820 7c90e514 nt!KiFastCallEntry+0xf8
0012d820 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
bdfsfltr+9c3f
b9e6ac3f ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: bdfsfltr+9c3f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bdfsfltr

IMAGE_NAME: bdfsfltr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a688490

FAILURE_BUCKET_ID: 0x8E_bdfsfltr+9c3f

BUCKET_ID: 0x8E_bdfsfltr+9c3f

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

Hope someone can advise

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,092 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:42 AM

Posted 25 October 2010 - 04:05 PM

The designated culprit, bdfsfltr.sys, is a Bit Defender file.

If you have BD installed...try uninstalling it...reinstalling, then updating. Then try a burn, without using either iTunes or Pinnacle's software.

That should help isolate where the problem may lie.

Then I would try a burn with each of those programs. Depending on results, I would uninstall each and then reinstall, followed by update.

Louis

#3 cumbiebob

cumbiebob
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:05:42 AM

Posted 27 October 2010 - 11:57 AM

The designated culprit, bdfsfltr.sys, is a Bit Defender file.

If you have BD installed...try uninstalling it...reinstalling, then updating. Then try a burn, without using either iTunes or Pinnacle's software.

That should help isolate where the problem may lie.

Then I would try a burn with each of those programs. Depending on results, I would uninstall each and then reinstall, followed by update.

Louis


Thanks for getting back to me, I do not appear to have bit defender on my machine although could this perhaps be virgin media's anti-virus? I am not sure and hesitant to uninstall in case its the wrong application although I guess if I am immeadiately reinstalling?

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,092 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:42 AM

Posted 27 October 2010 - 12:40 PM

Let's try this.

Download/install BlueScreenView..

Double-click BlueScreenView.exe file.

When scanning is done, Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

Edited by hamluis, 27 October 2010 - 12:42 PM.


#5 cumbiebob

cumbiebob
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:05:42 AM

Posted 28 October 2010 - 03:34 PM

Hi Louis,

As requested:

==================================================
Dump File : Mini102310-01.dmp
Crash Time : 23/10/2010 14:26:54
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x806d2753
Parameter 3 : 0xa6211488
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2753
File Description : Hardware Abstraction Layer DLL
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\Mini102310-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini101510-01.dmp
Crash Time : 15/10/2010 15:52:10
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x806d2753
Parameter 3 : 0xa663b488
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2753
File Description : Hardware Abstraction Layer DLL
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\Mini101510-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini101210-01.dmp
Crash Time : 12/10/2010 20:48:29
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x806d2753
Parameter 3 : 0xaa0434e8
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2753
File Description : Hardware Abstraction Layer DLL
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\Mini101210-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini101110-01.dmp
Crash Time : 11/10/2010 19:38:21
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x806d2753
Parameter 3 : 0xba2c74e8
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2753
File Description : Hardware Abstraction Layer DLL
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\Mini101110-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini100610-01.dmp
Crash Time : 06/10/2010 20:15:24
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x806d2753
Parameter 3 : 0xb11d24e8
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2753
File Description : Hardware Abstraction Layer DLL
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\Mini100610-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini092110-02.dmp
Crash Time : 21/09/2010 18:32:14
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x806d2753
Parameter 3 : 0xa401faec
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2753
File Description : Hardware Abstraction Layer DLL
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\Mini092110-02.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini092110-01.dmp
Crash Time : 21/09/2010 17:31:55
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x806d2753
Parameter 3 : 0xa7c02998
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2753
File Description : Hardware Abstraction Layer DLL
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\Mini092110-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini032809-01.dmp
Crash Time : 28/03/2009 12:31:35
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 0x00000007
Parameter 2 : 0x00000cd4
Parameter 3 : 0x00000000
Parameter 4 : 0x82713460
Caused By Driver : RT2500.sys
Caused By Address : RT2500.sys+3369
File Description : RT2500 802.11g Wireless Adapter Driver
Product Name : RT2500 802.11g Wireless Adapters
Company : Ralink Technology Inc.
File Version : 2.02.07.0000
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini032809-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini121708-01.dmp
Crash Time : 17/12/2008 23:27:17
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0xff183000
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0xf83d6826
Caused By Driver : vobid.sys
Caused By Address : vobid.sys+1826
File Description : InstantDrive
Product Name : InstantDrive
Company : Pinnacle Systems
File Version : 1, 1, 0, 20
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini121708-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini121906-01.dmp
Crash Time : 19/12/2006 22:51:36
Bug Check String : DRIVER_CORRUPTED_MMPOOL
Bug Check Code : 0x100000d0
Parameter 1 : 0xc00ac7ec
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x8054201d
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6b01d
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini121906-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini020206-01.dmp
Crash Time : 02/02/2006 17:29:26
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0xffb31000
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0xf8496826
Caused By Driver : vobid.sys
Caused By Address : vobid.sys+1826
File Description : InstantDrive
Product Name : InstantDrive
Company : Pinnacle Systems
File Version : 1, 1, 0, 20
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini020206-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini053005-01.dmp
Crash Time : 30/05/2005 12:32:50
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xce850ff0
Parameter 2 : 0x00000000
Parameter 3 : 0x804effe5
Parameter 4 : 0x00000000
Caused By Driver : vobiw.SYS
Caused By Address : vobiw.SYS+708f
File Description : InstantWrite File System Driver
Product Name : InstantWrite
Company : Pinnacle Systems GmbH
File Version : 6, 0, 6, 4356
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini053005-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini050805-01.dmp
Crash Time : 08/05/2005 22:11:07
Bug Check String : NO_MORE_IRP_STACK_LOCATIONS
Bug Check Code : 0x00000035
Parameter 1 : 0xff9208a8
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : vobiw.SYS
Caused By Address : vobiw.SYS+6c79
File Description : InstantWrite File System Driver
Product Name : InstantWrite
Company : Pinnacle Systems GmbH
File Version : 6, 0, 6, 4356
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini050805-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,092 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:42 AM

Posted 28 October 2010 - 06:02 PM

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

Your errors point to hal.dll, but it could be any number of things.

http://www.techspot.com/vb/topic48882.html

I'd start with the software, since every burn program includes drivers. Driver issues can be generated by such, firewalls, AV programs and many other types of software.

Louis

#7 cumbiebob

cumbiebob
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:05:42 AM

Posted 30 October 2010 - 05:40 AM

Thanks for the steer Louis, I will try uninstalling and reinstalling some of the software that I suspect and see if that helps. I will let you know if I have any success.

Robert

#8 cumbiebob

cumbiebob
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:05:42 AM

Posted 10 November 2010 - 06:58 PM

Hi Louis,

Well this evening finally managed to burn a cd from both Itunes and Pinnicle writer but unfortunately cannot be sure how I finally did it.

I removed and reinstalled the programs I suspected which didn't seem to solve the problem.

I used uniblue to update drivers and also checked that I had all the windows updates installed.

I had gone as far as ordering another drive just in case it was a hardware issue but when I tried again tonight hey presto it worked so I am afraid it is still a bit of a mystery.

thanks for your help and we can close this thread now.

#9 hamluis

hamluis

    Moderator


  • Moderator
  • 56,092 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:42 AM

Posted 10 November 2010 - 07:04 PM

Happy computing :).

Louis

#10 cumbiebob

cumbiebob
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:05:42 AM

Posted 16 June 2011 - 10:24 AM

Hi,

I know this thread is complete however just an update, although I did manage to write to disk a couple of times the problem reoccurred again several weeks later and I finally installed a new dvd drive. Since then I have had no problems but only time will tell.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users