Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSod's after Format...

02 Oct 2011   #21
DennisS

Windows 7 Home Premium 64-bit
 
 

Quote   Quote: Originally Posted by panais View Post
Just post back and we will try to find a solution.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1043

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002EFD3A2
BCP3: FFFFF88008B63110
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1


My System SpecsSystem Spec
.
02 Oct 2011   #22
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

No probably causes are been pointed out, run Driver Verifier and upload any dumps which are then created
Your system may be rendered unusable during that time, so use safemode with networking to access and upload dumps
Driver Verifier - Enable and Disable
My System SpecsSystem Spec
02 Oct 2011   #23
DennisS

Windows 7 Home Premium 64-bit
 
 

Quote   Quote: Originally Posted by yowanvista View Post
No probably causes are been pointed out, run Driver Verifier and upload any dumps which are then created
Your system may be rendered unusable during that time, so use safemode with networking to access and upload dumps
Driver Verifier - Enable and Disable
I just did. Couldn't get to safe mode either because of CyberLink PowerRecover. Had to recover to an earlier state, lost track of newly installed drivers now.

Good news: i've got a minidump.
I wrote one down and I THINK i've got one of them saved.

0x000000C9
0x000000000000023E
0FFFFF88003E14308
0xFFFFF98003DB6EE0
0x0

&

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1043

Additional information about the problem:
BCCode: c9
BCP1: 000000000000023E
BCP2: FFFFF880043B1308
BCP3: FFFFF98003CFEEE0
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

+attachment
My System SpecsSystem Spec
.

02 Oct 2011   #24
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

The cause is a Deamon Tools driver, please uninstall this software
Code:
dtsoftbus01.sys    dtsoftbus01.sys+1308    fffff880`043b0000    fffff880`043f6000    0x00046000    0x4dfb047d    17/06/2011 11:38:37
GEARAspiWDM.sys was also invloved, this driver used by a variety of DVD/CD related programs such as this GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering
Your should remove such software
You can turn Off Driver Verifier now
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff880043b1308, fffff98003cfeee0, 0}

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


DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff880043b1308, The address in the driver's code where the error was detected.
Arg3: fffff98003cfeee0, IRP address.
Arg4: 0000000000000000, Status code.

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


BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+1308
fffff880`043b1308 4053            push    rbx

FOLLOWUP_IP: 
dtsoftbus01+1308
fffff880`043b1308 4053            push    rbx

IRP_ADDRESS:  fffff98003cfeee0

DEVICE_OBJECT: fffffa800935b060

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800033603dc to fffff80002ed6c40

STACK_TEXT:  
fffff880`033d2738 fffff800`033603dc : 00000000`000000c9 00000000`0000023e fffff880`043b1308 fffff980`03cfeee0 : nt!KeBugCheckEx
fffff880`033d2740 fffff800`0336a47a : fffff800`0335e9f0 fffff880`043b1308 fffff980`03cfeee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`033d2780 fffff800`0336b34e : 00000000`0000023e 00000000`00000000 fffff980`03cfeee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`033d27d0 fffff800`0337671f : fffffa80`08aef300 fffffa80`08adb8e0 fffffa80`08adb998 fffff880`043b5080 : nt!VfErrorReport6+0x6e
fffff880`033d28a0 fffff800`03376b63 : fffffa80`08adb8e0 00000000`00000002 fffffa80`0935b060 fffff880`043b13d8 : nt!IovpCallDriver2+0x13f
fffff880`033d2900 fffff800`0337cc2e : fffff980`03cfeee0 fffff980`03cfeee0 00000000`00000002 fffffa80`0935b060 : nt!VfAfterCallDriver+0x353
fffff880`033d2950 fffff880`00e1e0c2 : fffff880`00e977c0 fffffa80`06dff3a0 00000000`00000025 fffffa80`08adb8e0 : nt!IovCallDriver+0x57e
fffff880`033d29b0 fffff880`00e3359f : fffffa80`08afcb50 00000000`00000000 fffff880`00000000 fffff880`01a055d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a
fffff880`033d2a60 fffff880`01a19e95 : fffffa80`00000020 fffffa80`08afcb50 fffffa80`06dff3a0 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`033d2ab0 fffff880`01a1a2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`033d2c70 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`033d2b10 fffff880`01a18f04 : 0000057f`f7595fd8 fffff880`033d2c70 fffffa80`08aeea80 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`033d2c40 fffff880`01a17825 : fffffa80`00000002 fffffa80`08a6a390 fffff880`01a0f3b8 0000057f`f7595fd8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`033d2d10 fffff880`00e889d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00e91620 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`033d2d50 fffff880`00e8894e : fffffa80`05900cf0 00000000`0000000c fffff880`00e91620 fffff880`00e91600 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`033d2d80 fffff880`00e7cb9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00e91620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`033d2df0 fffff880`00e7c6eb : 00000000`00000312 00000000`00000000 fffff880`00e91600 fffff6fc`c001df00 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`033d2e20 fffff880`00e7c38e : fffffa80`08c6da90 00000000`00000040 fffff880`00e913e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
fffff880`033d2f50 fffff880`00e7c06c : 00000000`00000000 00000000`00000040 00000000`00000501 fffffa80`08c6da90 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`033d2fc0 fffff880`00e89b5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
fffff880`033d3050 fffff880`00e89abb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`0337b5ec : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`033d3080 fffff880`00e85950 : fffffa80`08c6da90 00000000`00000001 00000000`00000000 fffff880`00e8dff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7
fffff880`033d3100 fffff880`00e85372 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`08b00e00 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8
fffff880`033d3170 fffff880`00e81a45 : 00000000`00000000 fffffa80`08b00e00 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2
fffff880`033d3200 fffff880`00e81841 : 00000000`00000101 00000000`00000108 00000000`00000108 07e00000`9e782860 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`033d3240 fffff880`00e814fe : fffffa80`08c6da90 fffff880`033d3370 00000000`00000004 fffff880`00e90390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff880`033d32b0 fffff880`00e81201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`08c6da90 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`033d3320 fffff880`00e78d9c : 00000000`00000000 fffffa80`08c6da90 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff880`033d33b0 fffff880`00e77dd6 : fffffa80`08859e70 00000000`00000002 00000000`00000000 fffffa80`08c6da90 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff880`033d33e0 fffff880`00e47245 : fffff980`016e6d80 fffff980`016e6d80 fffffa80`08b27e20 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`033d3450 fffff880`00e4714b : fffff880`033d3538 fffff980`016e6d80 00000000`00000002 fffffa80`08b27e20 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`033d3480 fffff800`0337cc16 : fffff980`016e6d80 00000000`00000002 fffffa80`08b27e20 fffff800`0337837e : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`033d34c0 fffff800`0337f52a : fffff980`016e6ee0 fffffa80`08b27e20 fffffa80`08aff450 fffffa80`08adb810 : nt!IovCallDriver+0x566
fffff880`033d3520 fffff800`0337cc16 : fffff980`016e6d80 00000000`00000002 fffffa80`08aff450 fffffa80`08ad44f0 : nt!ViFilterDispatchPnp+0x13a
fffff880`033d3550 fffff880`03f17202 : fffffa80`08aff450 00000000`00000000 fffffa80`08c2c190 fffffa80`08ad44f0 : nt!IovCallDriver+0x566
fffff880`033d35b0 fffffa80`08aff450 : 00000000`00000000 fffffa80`08c2c190 fffffa80`08ad44f0 fffff980`016e6fb8 : GEARAspiWDM+0x7202
fffff880`033d35b8 00000000`00000000 : fffffa80`08c2c190 fffffa80`08ad44f0 fffff980`016e6fb8 fffffa80`08b2f2b8 : 0xfffffa80`08aff450


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1308

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dfb047d

FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

Followup: MachineOwner
---------
My System SpecsSystem Spec
02 Oct 2011   #25
DennisS

Windows 7 Home Premium 64-bit
 
 

Quote   Quote: Originally Posted by yowanvista View Post
The cause is a Deamon Tools driver, please uninstall this software
Code:
dtsoftbus01.sys    dtsoftbus01.sys+1308    fffff880`043b0000    fffff880`043f6000    0x00046000    0x4dfb047d    17/06/2011 11:38:37
GEARAspiWDM.sys was also invloved, this driver used by a variety of DVD/CD related programs such as this GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering
Your should remove such software
You can turn Off Driver Verifier now
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff880043b1308, fffff98003cfeee0, 0}

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


DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff880043b1308, The address in the driver's code where the error was detected.
Arg3: fffff98003cfeee0, IRP address.
Arg4: 0000000000000000, Status code.

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


BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+1308
fffff880`043b1308 4053            push    rbx

FOLLOWUP_IP: 
dtsoftbus01+1308
fffff880`043b1308 4053            push    rbx

IRP_ADDRESS:  fffff98003cfeee0

DEVICE_OBJECT: fffffa800935b060

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800033603dc to fffff80002ed6c40

STACK_TEXT:  
fffff880`033d2738 fffff800`033603dc : 00000000`000000c9 00000000`0000023e fffff880`043b1308 fffff980`03cfeee0 : nt!KeBugCheckEx
fffff880`033d2740 fffff800`0336a47a : fffff800`0335e9f0 fffff880`043b1308 fffff980`03cfeee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`033d2780 fffff800`0336b34e : 00000000`0000023e 00000000`00000000 fffff980`03cfeee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`033d27d0 fffff800`0337671f : fffffa80`08aef300 fffffa80`08adb8e0 fffffa80`08adb998 fffff880`043b5080 : nt!VfErrorReport6+0x6e
fffff880`033d28a0 fffff800`03376b63 : fffffa80`08adb8e0 00000000`00000002 fffffa80`0935b060 fffff880`043b13d8 : nt!IovpCallDriver2+0x13f
fffff880`033d2900 fffff800`0337cc2e : fffff980`03cfeee0 fffff980`03cfeee0 00000000`00000002 fffffa80`0935b060 : nt!VfAfterCallDriver+0x353
fffff880`033d2950 fffff880`00e1e0c2 : fffff880`00e977c0 fffffa80`06dff3a0 00000000`00000025 fffffa80`08adb8e0 : nt!IovCallDriver+0x57e
fffff880`033d29b0 fffff880`00e3359f : fffffa80`08afcb50 00000000`00000000 fffff880`00000000 fffff880`01a055d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a
fffff880`033d2a60 fffff880`01a19e95 : fffffa80`00000020 fffffa80`08afcb50 fffffa80`06dff3a0 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`033d2ab0 fffff880`01a1a2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`033d2c70 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`033d2b10 fffff880`01a18f04 : 0000057f`f7595fd8 fffff880`033d2c70 fffffa80`08aeea80 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`033d2c40 fffff880`01a17825 : fffffa80`00000002 fffffa80`08a6a390 fffff880`01a0f3b8 0000057f`f7595fd8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`033d2d10 fffff880`00e889d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00e91620 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`033d2d50 fffff880`00e8894e : fffffa80`05900cf0 00000000`0000000c fffff880`00e91620 fffff880`00e91600 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`033d2d80 fffff880`00e7cb9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00e91620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`033d2df0 fffff880`00e7c6eb : 00000000`00000312 00000000`00000000 fffff880`00e91600 fffff6fc`c001df00 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`033d2e20 fffff880`00e7c38e : fffffa80`08c6da90 00000000`00000040 fffff880`00e913e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
fffff880`033d2f50 fffff880`00e7c06c : 00000000`00000000 00000000`00000040 00000000`00000501 fffffa80`08c6da90 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`033d2fc0 fffff880`00e89b5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
fffff880`033d3050 fffff880`00e89abb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`0337b5ec : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`033d3080 fffff880`00e85950 : fffffa80`08c6da90 00000000`00000001 00000000`00000000 fffff880`00e8dff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7
fffff880`033d3100 fffff880`00e85372 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`08b00e00 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8
fffff880`033d3170 fffff880`00e81a45 : 00000000`00000000 fffffa80`08b00e00 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2
fffff880`033d3200 fffff880`00e81841 : 00000000`00000101 00000000`00000108 00000000`00000108 07e00000`9e782860 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`033d3240 fffff880`00e814fe : fffffa80`08c6da90 fffff880`033d3370 00000000`00000004 fffff880`00e90390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff880`033d32b0 fffff880`00e81201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`08c6da90 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`033d3320 fffff880`00e78d9c : 00000000`00000000 fffffa80`08c6da90 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff880`033d33b0 fffff880`00e77dd6 : fffffa80`08859e70 00000000`00000002 00000000`00000000 fffffa80`08c6da90 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff880`033d33e0 fffff880`00e47245 : fffff980`016e6d80 fffff980`016e6d80 fffffa80`08b27e20 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`033d3450 fffff880`00e4714b : fffff880`033d3538 fffff980`016e6d80 00000000`00000002 fffffa80`08b27e20 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`033d3480 fffff800`0337cc16 : fffff980`016e6d80 00000000`00000002 fffffa80`08b27e20 fffff800`0337837e : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`033d34c0 fffff800`0337f52a : fffff980`016e6ee0 fffffa80`08b27e20 fffffa80`08aff450 fffffa80`08adb810 : nt!IovCallDriver+0x566
fffff880`033d3520 fffff800`0337cc16 : fffff980`016e6d80 00000000`00000002 fffffa80`08aff450 fffffa80`08ad44f0 : nt!ViFilterDispatchPnp+0x13a
fffff880`033d3550 fffff880`03f17202 : fffffa80`08aff450 00000000`00000000 fffffa80`08c2c190 fffffa80`08ad44f0 : nt!IovCallDriver+0x566
fffff880`033d35b0 fffffa80`08aff450 : 00000000`00000000 fffffa80`08c2c190 fffffa80`08ad44f0 fffff980`016e6fb8 : GEARAspiWDM+0x7202
fffff880`033d35b8 00000000`00000000 : fffffa80`08c2c190 fffffa80`08ad44f0 fffff980`016e6fb8 fffffa80`08b2f2b8 : 0xfffffa80`08aff450


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1308

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dfb047d

FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

Followup: MachineOwner
---------
Okies, ive uninstalled D-Tools lite.
I can't find the GEAR software though :s
My System SpecsSystem Spec
02 Oct 2011   #26
DennisS

Windows 7 Home Premium 64-bit
 
 

I deleted DT, Ashampoo Burning Studio and all things related to CyberLink.
I've still got iTunes, I heard it can cause BSODs too cause it runs that driver?... as of lately.

Anyways, I will report back
My System SpecsSystem Spec
04 Oct 2011   #27
DennisS

Windows 7 Home Premium 64-bit
 
 

Really now? A new BSOD today 3b system service exception. AGAIN. I thought it might still be the gear software, but i'm not sure
i can't get into safemode. I need cyberlink powerrecover. :s

dump in attachment
i want to use verifier, but if i cant get to safemode..
My System SpecsSystem Spec
04 Oct 2011   #28
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

Quote   Quote: Originally Posted by DennisS View Post
bump. i have gotten two other blue screens not knowing what it is
Latest crashes were caused by your display driver, it should be updated.
That Cyberlink software should be temporarily removed for troubleshooting purposes.
My System SpecsSystem Spec
05 Oct 2011   #29
DennisS

Windows 7 Home Premium 64-bit
 
 

Quote   Quote: Originally Posted by yowanvista View Post
Quote   Quote: Originally Posted by DennisS View Post
bump. i have gotten two other blue screens not knowing what it is
Latest crashes were caused by your display driver, it should be updated.
That Cyberlink software should be temporarily removed for troubleshooting purposes.
How do I temporarily remove it? I can't find it manually and it's not in the list of software in control panel
My System SpecsSystem Spec
06 Oct 2011   #30
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

Quote   Quote: Originally Posted by DennisS View Post
Quote   Quote: Originally Posted by yowanvista View Post
Quote   Quote: Originally Posted by DennisS View Post
bump. i have gotten two other blue screens not knowing what it is
Latest crashes were caused by your display driver, it should be updated.
That Cyberlink software should be temporarily removed for troubleshooting purposes.
How do I temporarily remove it? I can't find it manually and it's not in the list of software in control panel
There should an uninstall utility provided with the program
My System SpecsSystem Spec
Reply

 BSod's after Format...




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Searches in folder with general format - results in music format
Can you control the folder format that your search results opens with? My work computer keeps reverting to music format when I want the general format. I don't need to know contributing artist of my solid modeling files.
General Discussion
Best Format For Lossless Video Compression/Conversion to .avi Format?
Hi all, Just wondering, for you video editors out there, which format you prefer from the following: BGR24 RGB555 YUY2 RGBA32
Music, Pictures & Video
Can't format external HDD, except to exFat and 'quick format' enabled
Hi, So, the title basically says it all. This is what happened: My 1TB external hard drive worked just fine. I used to store there everything. It was using NTFS file system. Last week I connected it to my laptop and it was really slow when I tried to move or delete files from my pc to the...
Hardware & Devices
How do I change Video Library format to a different viewing format?
I am having a tiny problem with my computer that I don't know how to fix. Recently I had installed a new program to my computer but in doing so, the library style of my videos changed and I don't know how to fix it to what it was before. Previously it resembled the layout of my picture folder. I've...
Media Center
lots of BSOD - Format, Clean windows install - Still same BSOD
Hi, I use a 1.5 year old aces aspire 5738z and I think it just died on me. Here is what happens. Whatever I do it cannot stay without a BSOD for more than 10 minutes. I tried reinstalling drivers and it did not change anything so I tried several things but finally just formated it and installed...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 06:39.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App