BSOD- rdyboost.sys

Pandy90 · 27 Mar 2010

My windows 7 laptop keeps getting the BSOD.

The blue screen shows the following:

Code:

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: rdyboost.sys

MEMORY_MANAGEMENT

I don't even use readyboost

How can I solve this?

Thanks in Advance

Bill2 · 27 Mar 2010

Go through this.

Windows 7 Random Crashes- Rdyboost.sys?

nickle · 27 Mar 2010

If anyone has ever inserted a usb flash memory drive or SD memory card in your computer it may have been setup automatically by Windows. See this article: Explore the features: Windows ReadyBoost

Pandy90 · 27 Mar 2010

Bill2 said:

Go through this.

Windows 7 Random Crashes- Rdyboost.sys?

That doesn't help me

ickymay · 27 Mar 2010

Pandy90 said:

Bill2 said:

Go through this.

Windows 7 Random Crashes- Rdyboost.sys?

That doesn't help me

is your windows system fully patched and are all your drivers up to date ?

Is your bios up to date ?

zip and upload your .dmp file and am sure someone can take a look to see if theres any other information that could help ?

Pandy90 · 27 Mar 2010

ickymay said:

Pandy90 said:

Bill2 said:

Go through this.

Windows 7 Random Crashes- Rdyboost.sys?

That doesn't help me

is your windows system fully patched and are all your drivers up to date ?

Is your bios up to date ?

zip and upload your .dmp file and am sure someone can take a look to see if theres any other information that could help ?

As far as I know, everything is up to date

Here is my minidump file...

whs · 27 Mar 2010

Disable Superfetch (in Services) and see whether that helps.

ickymay · 27 Mar 2010

windows debugger says this is a BugCheck 1E , KMODE_EXCEPTION_NOT_HANDLED (1e) and complains it's unable to load the image for netw5v64.sys , also the process named is msnmsgr.exe

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88007819b90, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\netw5v64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+5d3e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88007819b90, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

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

FAULTING_IP:
+3439323031663235
fffff880`07819b90 b8aa810780 mov eax,800781AAh

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fa0e0
0000000000000000

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

BUGCHECK_STR: 0x1E_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff8800781aab8 -- (.exr 0xfffff8800781aab8)
ExceptionAddress: fffff800032c7105 (nt!ExpInterlockedPopEntrySListFault16)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff8800781ab60 -- (.trap 0xfffff8800781ab60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000033c1b0001 rbx=0000000000000000 rcx=fffff80003446700
rdx=00590053005c0046 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032c7105 rsp=fffff8800781acf0 rbp=0000000000000008
r8=00590053005c0045 r9=0000000000000000 r10=fffff80003446700
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!ExpInterlockedPopEntrySListFault16:
fffff800`032c7105 498b08 mov rcx,qword ptr [r8] ds:0001:00590053`005c0045=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003354b2b to fffff800032c3f00

STACK_TEXT:
fffff880`07819ad8 fffff800`03354b2b : 00000000`0000001e ffffffff`c0000005 fffff880`07819b90 00000000`00000000 : nt!KeBugCheckEx
fffff880`07819ae0 fffff800`03317390 : fffffa80`02fdbab0 fffff880`04075515 fffffa80`02fdbab0 fffffa80`02fc4f58 : nt!KipFatalFilter+0x1b
fffff880`07819b20 fffff800`032f24dc : 00000000`00000000 fffffa80`02fc4f58 fffffa80`02fdbab0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff880`07819b60 fffff800`032e9bed : fffff800`0340a470 fffff880`0781c360 00000000`00000000 fffff800`03252000 : nt!_C_specific_handler+0x8c
fffff880`07819bd0 fffff800`032f1250 : fffff800`0340a470 fffff880`07819c48 fffff880`0781aab8 fffff800`03252000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`07819c00 fffff800`032fe1b5 : fffff880`0781aab8 fffff880`0781a310 fffff880`00000000 fffff800`00000004 : nt!RtlDispatchException+0x410
fffff880`0781a2e0 fffff800`032c3542 : fffff880`0781aab8 00000000`00000000 fffff880`0781ab60 fffffa80`07b86ab0 : nt!KiDispatchException+0x135
fffff880`0781a980 fffff800`032c1e4a : fffffa80`0882a068 fffffa80`0882a038 00000000`00000018 00000000`00000124 : nt!KiExceptionDispatch+0xc2
fffff880`0781ab60 fffff800`032c7105 : 00000000`00000000 fffff800`032d3c63 fffff880`0781ad20 fffff880`0781ad1c : nt!KiGeneralProtectionFault+0x10a
fffff880`0781acf0 fffff800`032d3c63 : fffff880`0781ad20 fffff880`0781ad1c 00000001`00000001 00000001`00000013 : nt!ExpInterlockedPopEntrySListFault16
fffff880`0781ad00 fffff880`018375a0 : 00000000`00000000 fffffa80`09504eb0 fffffa80`00000000 00000000`00000000 : nt!IoAllocateMdl+0xf3
fffff880`0781ad50 fffff880`0406ed3e : 00000000`00000000 fffff880`01909bb1 fffff880`07810018 fffff880`0781b168 : ndis!NdisAllocateMdl+0x20
fffff880`0781ad90 00000000`00000000 : fffff880`01909bb1 fffff880`07810018 fffff880`0781b168 fffffa80`08b6d9a0 : netw5v64+0x5d3e

STACK_COMMAND: kb

FOLLOWUP_IP:
netw5v64+5d3e
fffff880`0406ed3e ?? ???

SYMBOL_STACK_INDEX: c

SYMBOL_NAME: netw5v64+5d3e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: netw5v64

IMAGE_NAME: netw5v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c3e06

FAILURE_BUCKET_ID: X64_0x1E_c0000005_netw5v64+5d3e

BUCKET_ID: X64_0x1E_c0000005_netw5v64+5d3e

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

looking at the output from debugger I suspect msnmsgr has caused a network crash using the wireless driver netw5v64.sys

you need to update your network driver , presumably Intel ?

Utorrent has issues with this driver also

also what antivirus and or third party firewall are you using ?

you also need to update or remove these drivers as they are old

pcouffin.sys fffff880`010a3000 fffff880`010b7380 0x00014380 0x457584a2 05/12/2006 14:39:30
000.fcl fffff880`06549000 fffff880`06574000 0x0002b000 0x48dcdf7a 26/09/2008 13:11:22

pcouffin.sys is Patin-Couffin VSO Software and is related to CD/DVD burning software ?
000.fcl is possibly a CyberLink FCL Driver or My Book Device Driver by Cyberlink Corp ?

let us know how it goes ?

Pandy90 · 27 Mar 2010

ickymay said:

windows debugger says this is a BugCheck 1E , KMODE_EXCEPTION_NOT_HANDLED (1e) and complains it's unable to load the image for netw5v64.sys , also the process named is msnmsgr.exe

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88007819b90, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\netw5v64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+5d3e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88007819b90, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

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

FAULTING_IP:
+3439323031663235
fffff880`07819b90 b8aa810780 mov eax,800781AAh

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fa0e0
0000000000000000

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

BUGCHECK_STR: 0x1E_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff8800781aab8 -- (.exr 0xfffff8800781aab8)
ExceptionAddress: fffff800032c7105 (nt!ExpInterlockedPopEntrySListFault16)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff8800781ab60 -- (.trap 0xfffff8800781ab60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000033c1b0001 rbx=0000000000000000 rcx=fffff80003446700
rdx=00590053005c0046 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032c7105 rsp=fffff8800781acf0 rbp=0000000000000008
r8=00590053005c0045 r9=0000000000000000 r10=fffff80003446700
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!ExpInterlockedPopEntrySListFault16:
fffff800`032c7105 498b08 mov rcx,qword ptr [r8] ds:0001:00590053`005c0045=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003354b2b to fffff800032c3f00

STACK_TEXT:
fffff880`07819ad8 fffff800`03354b2b : 00000000`0000001e ffffffff`c0000005 fffff880`07819b90 00000000`00000000 : nt!KeBugCheckEx
fffff880`07819ae0 fffff800`03317390 : fffffa80`02fdbab0 fffff880`04075515 fffffa80`02fdbab0 fffffa80`02fc4f58 : nt!KipFatalFilter+0x1b
fffff880`07819b20 fffff800`032f24dc : 00000000`00000000 fffffa80`02fc4f58 fffffa80`02fdbab0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff880`07819b60 fffff800`032e9bed : fffff800`0340a470 fffff880`0781c360 00000000`00000000 fffff800`03252000 : nt!_C_specific_handler+0x8c
fffff880`07819bd0 fffff800`032f1250 : fffff800`0340a470 fffff880`07819c48 fffff880`0781aab8 fffff800`03252000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`07819c00 fffff800`032fe1b5 : fffff880`0781aab8 fffff880`0781a310 fffff880`00000000 fffff800`00000004 : nt!RtlDispatchException+0x410
fffff880`0781a2e0 fffff800`032c3542 : fffff880`0781aab8 00000000`00000000 fffff880`0781ab60 fffffa80`07b86ab0 : nt!KiDispatchException+0x135
fffff880`0781a980 fffff800`032c1e4a : fffffa80`0882a068 fffffa80`0882a038 00000000`00000018 00000000`00000124 : nt!KiExceptionDispatch+0xc2
fffff880`0781ab60 fffff800`032c7105 : 00000000`00000000 fffff800`032d3c63 fffff880`0781ad20 fffff880`0781ad1c : nt!KiGeneralProtectionFault+0x10a
fffff880`0781acf0 fffff800`032d3c63 : fffff880`0781ad20 fffff880`0781ad1c 00000001`00000001 00000001`00000013 : nt!ExpInterlockedPopEntrySListFault16
fffff880`0781ad00 fffff880`018375a0 : 00000000`00000000 fffffa80`09504eb0 fffffa80`00000000 00000000`00000000 : nt!IoAllocateMdl+0xf3
fffff880`0781ad50 fffff880`0406ed3e : 00000000`00000000 fffff880`01909bb1 fffff880`07810018 fffff880`0781b168 : ndis!NdisAllocateMdl+0x20
fffff880`0781ad90 00000000`00000000 : fffff880`01909bb1 fffff880`07810018 fffff880`0781b168 fffffa80`08b6d9a0 : netw5v64+0x5d3e

STACK_COMMAND: kb

FOLLOWUP_IP:
netw5v64+5d3e
fffff880`0406ed3e ?? ???

SYMBOL_STACK_INDEX: c

SYMBOL_NAME: netw5v64+5d3e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: netw5v64

IMAGE_NAME: netw5v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c3e06

FAILURE_BUCKET_ID: X64_0x1E_c0000005_netw5v64+5d3e

BUCKET_ID: X64_0x1E_c0000005_netw5v64+5d3e

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

looking at the output from debugger I suspect msnmsgr has caused a network crash using the wireless driver netw5v64.sys

you need to update your network driver , presumably Intel ?

Utorrent has issues with this driver also

also what antivirus and or third party firewall are you using ?

you also need to update or remove these drivers as they are old

pcouffin.sys fffff880`010a3000 fffff880`010b7380 0x00014380 0x457584a2 05/12/2006 14:39:30
000.fcl fffff880`06549000 fffff880`06574000 0x0002b000 0x48dcdf7a 26/09/2008 13:11:22

pcouffin.sys is Patin-Couffin VSO Software and is related to CD/DVD burning software ?
000.fcl is possibly a CyberLink FCL Driver or My Book Device Driver by Cyberlink Corp ?

let us know how it goes ?

Sorry I uploaded the wrong minidump. That was an error I got last week but I resolved it.

Here is My Current minidump...

zigzag3143 · 27 Mar 2010

Pandy90 said:

ickymay said:

windows debugger says this is a BugCheck 1E , KMODE_EXCEPTION_NOT_HANDLED (1e) and complains it's unable to load the image for netw5v64.sys , also the process named is msnmsgr.exe

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88007819b90, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\netw5v64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+5d3e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88007819b90, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

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

FAULTING_IP:
+3439323031663235
fffff880`07819b90 b8aa810780 mov eax,800781AAh

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fa0e0
0000000000000000

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

BUGCHECK_STR: 0x1E_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff8800781aab8 -- (.exr 0xfffff8800781aab8)
ExceptionAddress: fffff800032c7105 (nt!ExpInterlockedPopEntrySListFault16)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff8800781ab60 -- (.trap 0xfffff8800781ab60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000033c1b0001 rbx=0000000000000000 rcx=fffff80003446700
rdx=00590053005c0046 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032c7105 rsp=fffff8800781acf0 rbp=0000000000000008
r8=00590053005c0045 r9=0000000000000000 r10=fffff80003446700
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!ExpInterlockedPopEntrySListFault16:
fffff800`032c7105 498b08 mov rcx,qword ptr [r8] ds:0001:00590053`005c0045=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003354b2b to fffff800032c3f00

STACK_TEXT:
fffff880`07819ad8 fffff800`03354b2b : 00000000`0000001e ffffffff`c0000005 fffff880`07819b90 00000000`00000000 : nt!KeBugCheckEx
fffff880`07819ae0 fffff800`03317390 : fffffa80`02fdbab0 fffff880`04075515 fffffa80`02fdbab0 fffffa80`02fc4f58 : nt!KipFatalFilter+0x1b
fffff880`07819b20 fffff800`032f24dc : 00000000`00000000 fffffa80`02fc4f58 fffffa80`02fdbab0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff880`07819b60 fffff800`032e9bed : fffff800`0340a470 fffff880`0781c360 00000000`00000000 fffff800`03252000 : nt!_C_specific_handler+0x8c
fffff880`07819bd0 fffff800`032f1250 : fffff800`0340a470 fffff880`07819c48 fffff880`0781aab8 fffff800`03252000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`07819c00 fffff800`032fe1b5 : fffff880`0781aab8 fffff880`0781a310 fffff880`00000000 fffff800`00000004 : nt!RtlDispatchException+0x410
fffff880`0781a2e0 fffff800`032c3542 : fffff880`0781aab8 00000000`00000000 fffff880`0781ab60 fffffa80`07b86ab0 : nt!KiDispatchException+0x135
fffff880`0781a980 fffff800`032c1e4a : fffffa80`0882a068 fffffa80`0882a038 00000000`00000018 00000000`00000124 : nt!KiExceptionDispatch+0xc2
fffff880`0781ab60 fffff800`032c7105 : 00000000`00000000 fffff800`032d3c63 fffff880`0781ad20 fffff880`0781ad1c : nt!KiGeneralProtectionFault+0x10a
fffff880`0781acf0 fffff800`032d3c63 : fffff880`0781ad20 fffff880`0781ad1c 00000001`00000001 00000001`00000013 : nt!ExpInterlockedPopEntrySListFault16
fffff880`0781ad00 fffff880`018375a0 : 00000000`00000000 fffffa80`09504eb0 fffffa80`00000000 00000000`00000000 : nt!IoAllocateMdl+0xf3
fffff880`0781ad50 fffff880`0406ed3e : 00000000`00000000 fffff880`01909bb1 fffff880`07810018 fffff880`0781b168 : ndis!NdisAllocateMdl+0x20
fffff880`0781ad90 00000000`00000000 : fffff880`01909bb1 fffff880`07810018 fffff880`0781b168 fffffa80`08b6d9a0 : netw5v64+0x5d3e

STACK_COMMAND: kb

FOLLOWUP_IP:
netw5v64+5d3e
fffff880`0406ed3e ?? ???

SYMBOL_STACK_INDEX: c

SYMBOL_NAME: netw5v64+5d3e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: netw5v64

IMAGE_NAME: netw5v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c3e06

FAILURE_BUCKET_ID: X64_0x1E_c0000005_netw5v64+5d3e

BUCKET_ID: X64_0x1E_c0000005_netw5v64+5d3e

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

looking at the output from debugger I suspect msnmsgr has caused a network crash using the wireless driver netw5v64.sys

you need to update your network driver , presumably Intel ?

Utorrent has issues with this driver also

also what antivirus and or third party firewall are you using ?

you also need to update or remove these drivers as they are old

pcouffin.sys fffff880`010a3000 fffff880`010b7380 0x00014380 0x457584a2 05/12/2006 14:39:30
000.fcl fffff880`06549000 fffff880`06574000 0x0002b000 0x48dcdf7a 26/09/2008 13:11:22

pcouffin.sys is Patin-Couffin VSO Software and is related to CD/DVD burning software ?
000.fcl is possibly a CyberLink FCL Driver or My Book Device Driver by Cyberlink Corp ?

let us know how it goes ?

Sorry I uploaded the wrong minidump. That was an error I got last week but I resolved it.

Here is My Current minidump...

this one was again caused by readyboost (rdyboost.sys). YOu might want to disable the service and test again

ken

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\032710-35381-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03206000 PsLoadedModuleList = 0xfffff800`03443e50
Debug session time: Sat Mar 27 07:19:35.962 2010 (GMT-4)
System Uptime: 0 days 0:01:23.804
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {1236, fffffa80023bdb30, fffffa80023bdc30, 86059}

Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000001236, The subtype of the bugcheck.
Arg2: fffffa80023bdb30
Arg3: fffffa80023bdc30
Arg4: 0000000000086059

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


BUGCHECK_STR:  0x1a_1236

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033707a3 to fffff80003277f00

STACK_TEXT:  
fffff880`05266778 fffff800`033707a3 : 00000000`0000001a 00000000`00001236 fffffa80`023bdb30 fffffa80`023bdc30 : nt!KeBugCheckEx
fffff880`05266780 fffff880`01370f42 : fffffa80`023bdb30 fffffa80`033a5078 00000000`00000f09 fffff880`0137199a : nt!MmFreePagesFromMdl+0x293
fffff880`052667e0 fffff880`0137086f : fffffa80`033a5078 00000000`00000000 fffffa80`033e0b9e 00000000`00000000 : rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+0x4e
fffff880`05266840 fffff880`0136f55e : fffffa80`033a5010 00000000`00000001 fffffa80`033a5010 00000000`00000001 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCleanup+0x183
fffff880`05266880 fffff880`0136ea23 : fffffa80`033a5010 00000000`00000001 fffffa80`033a5010 fffff880`05266c60 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStCleanup+0x7a
fffff880`052668c0 fffff880`0136e986 : fffff880`013918f0 00000000`00000008 fffffa80`033a5010 fffff880`01391870 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmStoreMgrCallback+0x4b
fffff880`05266900 fffff880`013954b8 : fffff880`01391870 fffff880`05266c60 00000000`00000000 fffffa80`083c0310 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmCleanup+0x9a
fffff880`05266930 fffff880`01376b9e : fffffa80`083c0310 fffffa80`083c0310 fffffa80`082786f0 00000000`00000000 : rdyboost!SmdRBContextShutdown+0x94
fffff880`05266970 fffff800`035903a7 : 00000000`00000000 fffffa80`07de08a0 fffffa80`07de09b8 fffffa80`083c0310 : rdyboost!SmdDispatchDeviceControl+0x3ce
fffff880`052669d0 fffff800`03590c06 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`05266b00 fffff800`03277153 : fffffa80`00000000 00000000`00000129 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`05266b70 00000000`776dff2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0264e828 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776dff2a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e
fffff880`01370f42 33d2            xor     edx,edx

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc48a

FAILURE_BUCKET_ID:  X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e

BUCKET_ID:  X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e

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