Sign in with
Sign up | Sign in
Your question

Bugcheck 00000027 When Writing To DVD+RW

Last response: in Windows XP
Share
June 19, 2005 9:55:01 PM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

I use a Plextor DVD Writer and a DVD+RW disc for backups. In a nutshell,
every two weeks or so, I do a search in MyDocs for files that have changed
over the last two weeks. I drag and drop these files to a DVD+RW. Been
doing this for over a year and it worked fine two weeks ago.

Today when I try to create a folder on my DVD+RW, the machine crashes and
reboots.

I can drag and drop a single file onto the DVD+RW, eject the DVD disc,
re-insert it and verify the file was copied correctly. The system crashes
when I try to create a folder on the DVD.

There is an entry in the System Log:

---
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000027
(0xbaad00a0, 0xefdc6438, 0xefdc6134, 0xf14255e6). A dump was saved in:
C:\WINDOWS\Minidump\Mini061905-05.dmp.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---

The system crashes everytime I try to create folder on the DVD+RW. I have 5
"*.dmp" files in the "%systemRoot%\minidump" folder dated today.

I searched this Newsgroup for "bugcheck" and found two interesting hits:

1. Run "verifier" and select "delete exisiting settings". Tried this, but
I got a message saying "No settings were changed".

2. Review the MSDN web page
http://msdn.microsoft.com/library/default.asp?url=/libr...

This page says the problem occured in the SMB redirector file system. The
recommended fixes are to run a debugger command or add memory. My system has
1GB of RAM and Task Manager shows only 271M are in use. I do not understand
how to run the debugger command that is referenced in the MSDN web page.

Last Tues (6/14/2005) MS released MS05-027 (KB896422) that addresses a
problem with SMB. That patch replaces
"%systemroot%\system32\drivers\srv.sys". I checked the version of that file
to verify the patch was installed correctly. The version matches the readme
file. Is this patch a possible cause of my problems?

I checked the DVD+RW and there is 2.91GB in use. For a 4.7GB DVD there
should be plenty of free space.

Here is the output from "dumpchk":

---
C:\WINDOWS\Minidump> dumpchk mini061905-05.dmp
Loading dump file mini061905-05.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 207c6000
PfnDataBase 81a93000
PsLoadedModuleList 8055a420
PsActiveProcessHead 805604d8
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 00000027
BugCheckParameter1 baad00a0
BugCheckParameter2 efdc6438
BugCheckParameter3 efdc6134
BugCheckParameter4 f14255e6
PaeEnabled 00000000
KdDebuggerDataBlock 8054c060
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 0000114c
DriverListOffset 00003d60
DriverCount 0000008d
StringPoolOffset 00006740
StringPoolSize 00001390
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack efdc5eb4
DebuggerDataOffset 00003ad0
DebuggerDataSize 00000290
DataBlocksOffset 00007ad0
DataBlocksCount 00000005


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sun Jun 19 18:07:06 2005
System Uptime: 0 days 0:17:17
start end module name
804d7000 806eb100 nt Checksum: 002198AF Timestamp: Tue Mar 01
17:
59:37 2005 (42250FF9)

Unloaded modules:
f0a35000 f0a5f000 kmixer.sys Timestamp: unavailable (00000000)
f7c84000 f7c85000 drmkaud.sys Timestamp: unavailable (00000000)
f0a5f000 f0a82000 aec.sys Timestamp: unavailable (00000000)
f0c12000 f0c1f000 DMusic.sys Timestamp: unavailable (00000000)
f0c22000 f0c30000 swmidi.sys Timestamp: unavailable (00000000)
f7b75000 f7b77000 splitter.sys Timestamp: unavailable (00000000)
f010c000 f011d000 naveng.sys Timestamp: unavailable (00000000)
f011d000 f01b6000 navex15.sys Timestamp: unavailable (00000000)
f144d000 f145e000 naveng.sys Timestamp: unavailable (00000000)
f145e000 f14f7000 navex15.sys Timestamp: unavailable (00000000)
f6bc1000 f6bca000 processr.sys Timestamp: unavailable (00000000)
f79d7000 f79dc000 Cdaudio.SYS Timestamp: unavailable (00000000)
f7aa7000 f7aaa000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

C:\WINDOWS\Minidump>
---

Do not really understand the listing, but maybe someone can help.

What has changed in the last two weeks? I've added a wireless MS keyboard
and mouse.

Any ideas? TIA


System Summary:
Compaq Presario S6000Z
AMD AthlonXP 3000+
1GB Kingston Hyperx Dual channel DDR (2x512MB0
160GB HDD
Plextor 708A DVD Writer
Windows XP Pro, SP2, Windows Updated
Symatec AntiVirus v10
June 20, 2005 12:15:01 AM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Brand new DVD+RW disc, formatted with Roxio Easy Media Creator 7.

Same problem! It's not the media!

Try to create a folder on the DVD and XP crashes. Logs a "Bugcheck
00000027" in the System Log.



"Fred" wrote:

> I use a Plextor DVD Writer and a DVD+RW disc for backups. In a nutshell,
> every two weeks or so, I do a search in MyDocs for files that have changed
> over the last two weeks. I drag and drop these files to a DVD+RW. Been
> doing this for over a year and it worked fine two weeks ago.
>
> Today when I try to create a folder on my DVD+RW, the machine crashes and
> reboots.
>
> I can drag and drop a single file onto the DVD+RW, eject the DVD disc,
> re-insert it and verify the file was copied correctly. The system crashes
> when I try to create a folder on the DVD.
>
> There is an entry in the System Log:
>
> ---
> The computer has rebooted from a bugcheck. The bugcheck was: 0x00000027
> (0xbaad00a0, 0xefdc6438, 0xefdc6134, 0xf14255e6). A dump was saved in:
> C:\WINDOWS\Minidump\Mini061905-05.dmp.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ---
>
> The system crashes everytime I try to create folder on the DVD+RW. I have 5
> "*.dmp" files in the "%systemRoot%\minidump" folder dated today.
>
> I searched this Newsgroup for "bugcheck" and found two interesting hits:
>
> 1. Run "verifier" and select "delete exisiting settings". Tried this, but
> I got a message saying "No settings were changed".
>
> 2. Review the MSDN web page
> http://msdn.microsoft.com/library/default.asp?url=/libr...
>
> This page says the problem occured in the SMB redirector file system. The
> recommended fixes are to run a debugger command or add memory. My system has
> 1GB of RAM and Task Manager shows only 271M are in use. I do not understand
> how to run the debugger command that is referenced in the MSDN web page.
>
> Last Tues (6/14/2005) MS released MS05-027 (KB896422) that addresses a
> problem with SMB. That patch replaces
> "%systemroot%\system32\drivers\srv.sys". I checked the version of that file
> to verify the patch was installed correctly. The version matches the readme
> file. Is this patch a possible cause of my problems?
>
> I checked the DVD+RW and there is 2.91GB in use. For a 4.7GB DVD there
> should be plenty of free space.
>
> Here is the output from "dumpchk":
>
> ---
> C:\WINDOWS\Minidump> dumpchk mini061905-05.dmp
> Loading dump file mini061905-05.dmp
> ----- 32 bit Kernel Mini Dump Analysis
>
> DUMP_HEADER32:
> MajorVersion 0000000f
> MinorVersion 00000a28
> DirectoryTableBase 207c6000
> PfnDataBase 81a93000
> PsLoadedModuleList 8055a420
> PsActiveProcessHead 805604d8
> MachineImageType 0000014c
> NumberProcessors 00000001
> BugCheckCode 00000027
> BugCheckParameter1 baad00a0
> BugCheckParameter2 efdc6438
> BugCheckParameter3 efdc6134
> BugCheckParameter4 f14255e6
> PaeEnabled 00000000
> KdDebuggerDataBlock 8054c060
> MiniDumpFields 00000dff
>
> TRIAGE_DUMP32:
> ServicePackBuild 00000200
> SizeOfDump 00010000
> ValidOffset 0000fffc
> ContextOffset 00000320
> ExceptionOffset 000007d0
> MmOffset 00001068
> UnloadedDriversOffset 000010a0
> PrcbOffset 00001878
> ProcessOffset 000024c8
> ThreadOffset 00002728
> CallStackOffset 00002980
> SizeOfCallStack 0000114c
> DriverListOffset 00003d60
> DriverCount 0000008d
> StringPoolOffset 00006740
> StringPoolSize 00001390
> BrokenDriverOffset 00000000
> TriageOptions 00000041
> TopOfStack efdc5eb4
> DebuggerDataOffset 00003ad0
> DebuggerDataSize 00000290
> DataBlocksOffset 00007ad0
> DataBlocksCount 00000005
>
>
> Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
> Debug session time: Sun Jun 19 18:07:06 2005
> System Uptime: 0 days 0:17:17
> start end module name
> 804d7000 806eb100 nt Checksum: 002198AF Timestamp: Tue Mar 01
> 17:
> 59:37 2005 (42250FF9)
>
> Unloaded modules:
> f0a35000 f0a5f000 kmixer.sys Timestamp: unavailable (00000000)
> f7c84000 f7c85000 drmkaud.sys Timestamp: unavailable (00000000)
> f0a5f000 f0a82000 aec.sys Timestamp: unavailable (00000000)
> f0c12000 f0c1f000 DMusic.sys Timestamp: unavailable (00000000)
> f0c22000 f0c30000 swmidi.sys Timestamp: unavailable (00000000)
> f7b75000 f7b77000 splitter.sys Timestamp: unavailable (00000000)
> f010c000 f011d000 naveng.sys Timestamp: unavailable (00000000)
> f011d000 f01b6000 navex15.sys Timestamp: unavailable (00000000)
> f144d000 f145e000 naveng.sys Timestamp: unavailable (00000000)
> f145e000 f14f7000 navex15.sys Timestamp: unavailable (00000000)
> f6bc1000 f6bca000 processr.sys Timestamp: unavailable (00000000)
> f79d7000 f79dc000 Cdaudio.SYS Timestamp: unavailable (00000000)
> f7aa7000 f7aaa000 Sfloppy.SYS Timestamp: unavailable (00000000)
>
> Finished dump check
>
> C:\WINDOWS\Minidump>
> ---
>
> Do not really understand the listing, but maybe someone can help.
>
> What has changed in the last two weeks? I've added a wireless MS keyboard
> and mouse.
>
> Any ideas? TIA
>
>
> System Summary:
> Compaq Presario S6000Z
> AMD AthlonXP 3000+
> 1GB Kingston Hyperx Dual channel DDR (2x512MB0
> 160GB HDD
> Plextor 708A DVD Writer
> Windows XP Pro, SP2, Windows Updated
> Symatec AntiVirus v10
>
>
Anonymous
June 20, 2005 2:44:34 PM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Hi Fred,

Try this instead. The reference to "deleting existing settings is
turning off Driver Verifier. We will use it to hopefully find what is
causing this.
To determine what driver is causing the problem I need you to enable driver
verifier.
Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit next
4) Click on 'Select all drivers installed on this computer' and hit Finish
5) Reboot

There is a possibility that your computer will crash on reboot. If this
occurs hit F8 when rebooting just before the windows logo screen and select
the safe mode boot option. Follow the same steps above but on step 4 choose
'Select driver names from a list'; hit next; check the box next to any
driver where the provider is not Microsoft; hit Finish; reboot.

This will slow the performance of you computer a little while enabled but
will hopefully catch the driver causing corruption. Next time you crash
the blue screen will hopefully say something like
"DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
corresponding minidump (by default it is at c:\windows\Minidump ) my way.
If you have any questions or I didn't explain something well enough don't
hesitate to e-mail me (remove "online") back. Good Luck,


Joshua Smith
OpenGL Test Lab
Microsoft
-----

Get Secure! www.microsoft.com/security

This posting is provided "AS IS" with no warranties, and confers no rights
"Fred" <Fred@discussions.microsoft.com> wrote in message
news:57E8BAE2-F5B4-42A2-9E70-7EAAB3FACBA6@microsoft.com...
> Brand new DVD+RW disc, formatted with Roxio Easy Media Creator 7.
>
> Same problem! It's not the media!
>
> Try to create a folder on the DVD and XP crashes. Logs a "Bugcheck
> 00000027" in the System Log.
>
>
>
> "Fred" wrote:
>
>> I use a Plextor DVD Writer and a DVD+RW disc for backups. In a nutshell,
>> every two weeks or so, I do a search in MyDocs for files that have
>> changed
>> over the last two weeks. I drag and drop these files to a DVD+RW. Been
>> doing this for over a year and it worked fine two weeks ago.
>>
>> Today when I try to create a folder on my DVD+RW, the machine crashes and
>> reboots.
>>
>> I can drag and drop a single file onto the DVD+RW, eject the DVD disc,
>> re-insert it and verify the file was copied correctly. The system
>> crashes
>> when I try to create a folder on the DVD.
>>
>> There is an entry in the System Log:
>>
>> ---
>> The computer has rebooted from a bugcheck. The bugcheck was: 0x00000027
>> (0xbaad00a0, 0xefdc6438, 0xefdc6134, 0xf14255e6). A dump was saved in:
>> C:\WINDOWS\Minidump\Mini061905-05.dmp.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> ---
>>
>> The system crashes everytime I try to create folder on the DVD+RW. I
>> have 5
>> "*.dmp" files in the "%systemRoot%\minidump" folder dated today.
>>
>> I searched this Newsgroup for "bugcheck" and found two interesting hits:
>>
>> 1. Run "verifier" and select "delete exisiting settings". Tried this,
>> but
>> I got a message saying "No settings were changed".
>>
>> 2. Review the MSDN web page
>> http://msdn.microsoft.com/library/default.asp?url=/libr...
>>
>> This page says the problem occured in the SMB redirector file system.
>> The
>> recommended fixes are to run a debugger command or add memory. My system
>> has
>> 1GB of RAM and Task Manager shows only 271M are in use. I do not
>> understand
>> how to run the debugger command that is referenced in the MSDN web page.
>>
>> Last Tues (6/14/2005) MS released MS05-027 (KB896422) that addresses a
>> problem with SMB. That patch replaces
>> "%systemroot%\system32\drivers\srv.sys". I checked the version of that
>> file
>> to verify the patch was installed correctly. The version matches the
>> readme
>> file. Is this patch a possible cause of my problems?
>>
>> I checked the DVD+RW and there is 2.91GB in use. For a 4.7GB DVD there
>> should be plenty of free space.
>>
>> Here is the output from "dumpchk":
>>
>> ---
>> C:\WINDOWS\Minidump> dumpchk mini061905-05.dmp
>> Loading dump file mini061905-05.dmp
>> ----- 32 bit Kernel Mini Dump Analysis
>>
>> DUMP_HEADER32:
>> MajorVersion 0000000f
>> MinorVersion 00000a28
>> DirectoryTableBase 207c6000
>> PfnDataBase 81a93000
>> PsLoadedModuleList 8055a420
>> PsActiveProcessHead 805604d8
>> MachineImageType 0000014c
>> NumberProcessors 00000001
>> BugCheckCode 00000027
>> BugCheckParameter1 baad00a0
>> BugCheckParameter2 efdc6438
>> BugCheckParameter3 efdc6134
>> BugCheckParameter4 f14255e6
>> PaeEnabled 00000000
>> KdDebuggerDataBlock 8054c060
>> MiniDumpFields 00000dff
>>
>> TRIAGE_DUMP32:
>> ServicePackBuild 00000200
>> SizeOfDump 00010000
>> ValidOffset 0000fffc
>> ContextOffset 00000320
>> ExceptionOffset 000007d0
>> MmOffset 00001068
>> UnloadedDriversOffset 000010a0
>> PrcbOffset 00001878
>> ProcessOffset 000024c8
>> ThreadOffset 00002728
>> CallStackOffset 00002980
>> SizeOfCallStack 0000114c
>> DriverListOffset 00003d60
>> DriverCount 0000008d
>> StringPoolOffset 00006740
>> StringPoolSize 00001390
>> BrokenDriverOffset 00000000
>> TriageOptions 00000041
>> TopOfStack efdc5eb4
>> DebuggerDataOffset 00003ad0
>> DebuggerDataSize 00000290
>> DataBlocksOffset 00007ad0
>> DataBlocksCount 00000005
>>
>>
>> Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
>> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
>> Debug session time: Sun Jun 19 18:07:06 2005
>> System Uptime: 0 days 0:17:17
>> start end module name
>> 804d7000 806eb100 nt Checksum: 002198AF Timestamp: Tue Mar
>> 01
>> 17:
>> 59:37 2005 (42250FF9)
>>
>> Unloaded modules:
>> f0a35000 f0a5f000 kmixer.sys Timestamp: unavailable (00000000)
>> f7c84000 f7c85000 drmkaud.sys Timestamp: unavailable (00000000)
>> f0a5f000 f0a82000 aec.sys Timestamp: unavailable (00000000)
>> f0c12000 f0c1f000 DMusic.sys Timestamp: unavailable (00000000)
>> f0c22000 f0c30000 swmidi.sys Timestamp: unavailable (00000000)
>> f7b75000 f7b77000 splitter.sys Timestamp: unavailable (00000000)
>> f010c000 f011d000 naveng.sys Timestamp: unavailable (00000000)
>> f011d000 f01b6000 navex15.sys Timestamp: unavailable (00000000)
>> f144d000 f145e000 naveng.sys Timestamp: unavailable (00000000)
>> f145e000 f14f7000 navex15.sys Timestamp: unavailable (00000000)
>> f6bc1000 f6bca000 processr.sys Timestamp: unavailable (00000000)
>> f79d7000 f79dc000 Cdaudio.SYS Timestamp: unavailable (00000000)
>> f7aa7000 f7aaa000 Sfloppy.SYS Timestamp: unavailable (00000000)
>>
>> Finished dump check
>>
>> C:\WINDOWS\Minidump>
>> ---
>>
>> Do not really understand the listing, but maybe someone can help.
>>
>> What has changed in the last two weeks? I've added a wireless MS
>> keyboard
>> and mouse.
>>
>> Any ideas? TIA
>>
>>
>> System Summary:
>> Compaq Presario S6000Z
>> AMD AthlonXP 3000+
>> 1GB Kingston Hyperx Dual channel DDR (2x512MB0
>> 160GB HDD
>> Plextor 708A DVD Writer
>> Windows XP Pro, SP2, Windows Updated
>> Symatec AntiVirus v10
>>
>>
June 21, 2005 1:08:03 AM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Thanks for the reply.

The computer is sure slow when the Driver Verifier is enabled.

When I tried to create folder on the DVD with Driver Verifier enabled, I got
a BSOD with the info:

---
RDR_FILE_SYSTEM

STOP: 0x00000027(0xbaad00a0,0xb56fc3f0,0xb56fc0ec,0xba7775e6)

cdudf_xp.sys Address BA7775E6 base at BA738000
---

Searched the C: drive for "cdudf_xp.sys" and found a copy in
C:\Windows\system32\drivers. A properties listing of that driver showed it
came from Roxio.

Removed the Roxio Easy Media Creator software, rebooted, re-installed it,
applied the patch, and rebooted.

However, same problem! System crashes when I create folder on the DVD+RW disc.

Searched the Roxio support page for "cdudf_xp.sys", but did not find
anything useful. I have posted this problem on the Roxio support forums, but
nothing helpful yet.

I will e-mail you the minidump for analysis.

Thanks again for your help.



"Joshua Smith [MSFT]" wrote:

> Hi Fred,
>
> Try this instead. The reference to "deleting existing settings is
> turning off Driver Verifier. We will use it to hopefully find what is
> causing this.
> To determine what driver is causing the problem I need you to enable driver
> verifier.
> Steps:
> 1) Windows Key + R
> 2) Type in 'verifier' and hit enter
> 3) Make sure 'Create Standard Setting' is selected and hit next
> 4) Click on 'Select all drivers installed on this computer' and hit Finish
> 5) Reboot
>
> There is a possibility that your computer will crash on reboot. If this
> occurs hit F8 when rebooting just before the windows logo screen and select
> the safe mode boot option. Follow the same steps above but on step 4 choose
> 'Select driver names from a list'; hit next; check the box next to any
> driver where the provider is not Microsoft; hit Finish; reboot.
>
> This will slow the performance of you computer a little while enabled but
> will hopefully catch the driver causing corruption. Next time you crash
> the blue screen will hopefully say something like
> "DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
> corresponding minidump (by default it is at c:\windows\Minidump ) my way.
> If you have any questions or I didn't explain something well enough don't
> hesitate to e-mail me (remove "online") back. Good Luck,
>
>
> Joshua Smith
> OpenGL Test Lab
> Microsoft
> -----
>
> Get Secure! www.microsoft.com/security
>
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Fred" <Fred@discussions.microsoft.com> wrote in message
> news:57E8BAE2-F5B4-42A2-9E70-7EAAB3FACBA6@microsoft.com...
> > Brand new DVD+RW disc, formatted with Roxio Easy Media Creator 7.
> >
> > Same problem! It's not the media!
> >
> > Try to create a folder on the DVD and XP crashes. Logs a "Bugcheck
> > 00000027" in the System Log.
> >
> >
> >
> > "Fred" wrote:
> >
> >> I use a Plextor DVD Writer and a DVD+RW disc for backups. In a nutshell,
> >> every two weeks or so, I do a search in MyDocs for files that have
> >> changed
> >> over the last two weeks. I drag and drop these files to a DVD+RW. Been
> >> doing this for over a year and it worked fine two weeks ago.
> >>
> >> Today when I try to create a folder on my DVD+RW, the machine crashes and
> >> reboots.
> >>
> >> I can drag and drop a single file onto the DVD+RW, eject the DVD disc,
> >> re-insert it and verify the file was copied correctly. The system
> >> crashes
> >> when I try to create a folder on the DVD.
> >>
> >> There is an entry in the System Log:
> >>
> >> ---
> >> The computer has rebooted from a bugcheck. The bugcheck was: 0x00000027
> >> (0xbaad00a0, 0xefdc6438, 0xefdc6134, 0xf14255e6). A dump was saved in:
> >> C:\WINDOWS\Minidump\Mini061905-05.dmp.
> >>
> >> For more information, see Help and Support Center at
> >> http://go.microsoft.com/fwlink/events.asp.
> >> ---
> >>
> >> The system crashes everytime I try to create folder on the DVD+RW. I
> >> have 5
> >> "*.dmp" files in the "%systemRoot%\minidump" folder dated today.
> >>
> >> I searched this Newsgroup for "bugcheck" and found two interesting hits:
> >>
> >> 1. Run "verifier" and select "delete exisiting settings". Tried this,
> >> but
> >> I got a message saying "No settings were changed".
> >>
> >> 2. Review the MSDN web page
> >> http://msdn.microsoft.com/library/default.asp?url=/libr...
> >>
> >> This page says the problem occured in the SMB redirector file system.
> >> The
> >> recommended fixes are to run a debugger command or add memory. My system
> >> has
> >> 1GB of RAM and Task Manager shows only 271M are in use. I do not
> >> understand
> >> how to run the debugger command that is referenced in the MSDN web page.
> >>
> >> Last Tues (6/14/2005) MS released MS05-027 (KB896422) that addresses a
> >> problem with SMB. That patch replaces
> >> "%systemroot%\system32\drivers\srv.sys". I checked the version of that
> >> file
> >> to verify the patch was installed correctly. The version matches the
> >> readme
> >> file. Is this patch a possible cause of my problems?
> >>
> >> I checked the DVD+RW and there is 2.91GB in use. For a 4.7GB DVD there
> >> should be plenty of free space.
> >>
> >> Here is the output from "dumpchk":
> >>
> >> ---
> >> C:\WINDOWS\Minidump> dumpchk mini061905-05.dmp
> >> Loading dump file mini061905-05.dmp
> >> ----- 32 bit Kernel Mini Dump Analysis
> >>
> >> DUMP_HEADER32:
> >> MajorVersion 0000000f
> >> MinorVersion 00000a28
> >> DirectoryTableBase 207c6000
> >> PfnDataBase 81a93000
> >> PsLoadedModuleList 8055a420
> >> PsActiveProcessHead 805604d8
> >> MachineImageType 0000014c
> >> NumberProcessors 00000001
> >> BugCheckCode 00000027
> >> BugCheckParameter1 baad00a0
> >> BugCheckParameter2 efdc6438
> >> BugCheckParameter3 efdc6134
> >> BugCheckParameter4 f14255e6
> >> PaeEnabled 00000000
> >> KdDebuggerDataBlock 8054c060
> >> MiniDumpFields 00000dff
> >>
> >> TRIAGE_DUMP32:
> >> ServicePackBuild 00000200
> >> SizeOfDump 00010000
> >> ValidOffset 0000fffc
> >> ContextOffset 00000320
> >> ExceptionOffset 000007d0
> >> MmOffset 00001068
> >> UnloadedDriversOffset 000010a0
> >> PrcbOffset 00001878
> >> ProcessOffset 000024c8
> >> ThreadOffset 00002728
> >> CallStackOffset 00002980
> >> SizeOfCallStack 0000114c
> >> DriverListOffset 00003d60
> >> DriverCount 0000008d
> >> StringPoolOffset 00006740
> >> StringPoolSize 00001390
> >> BrokenDriverOffset 00000000
> >> TriageOptions 00000041
> >> TopOfStack efdc5eb4
> >> DebuggerDataOffset 00003ad0
> >> DebuggerDataSize 00000290
> >> DataBlocksOffset 00007ad0
> >> DataBlocksCount 00000005
> >>
> >>
> >> Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
> >> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
> >> Debug session time: Sun Jun 19 18:07:06 2005
> >> System Uptime: 0 days 0:17:17
> >> start end module name
> >> 804d7000 806eb100 nt Checksum: 002198AF Timestamp: Tue Mar
> >> 01
> >> 17:
> >> 59:37 2005 (42250FF9)
> >>
> >> Unloaded modules:
> >> f0a35000 f0a5f000 kmixer.sys Timestamp: unavailable (00000000)
> >> f7c84000 f7c85000 drmkaud.sys Timestamp: unavailable (00000000)
> >> f0a5f000 f0a82000 aec.sys Timestamp: unavailable (00000000)
> >> f0c12000 f0c1f000 DMusic.sys Timestamp: unavailable (00000000)
> >> f0c22000 f0c30000 swmidi.sys Timestamp: unavailable (00000000)
> >> f7b75000 f7b77000 splitter.sys Timestamp: unavailable (00000000)
> >> f010c000 f011d000 naveng.sys Timestamp: unavailable (00000000)
> >> f011d000 f01b6000 navex15.sys Timestamp: unavailable (00000000)
> >> f144d000 f145e000 naveng.sys Timestamp: unavailable (00000000)
> >> f145e000 f14f7000 navex15.sys Timestamp: unavailable (00000000)
> >> f6bc1000 f6bca000 processr.sys Timestamp: unavailable (00000000)
> >> f79d7000 f79dc000 Cdaudio.SYS Timestamp: unavailable (00000000)
> >> f7aa7000 f7aaa000 Sfloppy.SYS Timestamp: unavailable (00000000)
> >>
> >> Finished dump check
> >>
> >> C:\WINDOWS\Minidump>
> >> ---
> >>
> >> Do not really understand the listing, but maybe someone can help.
> >>
> >> What has changed in the last two weeks? I've added a wireless MS
> >> keyboard
> >> and mouse.
> >>
> >> Any ideas? TIA
> >>
> >>
> >> System Summary:
> >> Compaq Presario S6000Z
> >> AMD AthlonXP 3000+
> >> 1GB Kingston Hyperx Dual channel DDR (2x512MB0
> >> 160GB HDD
> >> Plextor 708A DVD Writer
> >> Windows XP Pro, SP2, Windows Updated
> >> Symatec AntiVirus v10
> >>
> >>
>
>
>
!