Possible out of date drivers:
Code:
giveio 873fc000 873fc680 Wed Apr 03 20:33:25 1996 (316334f5) 00003355 giveio.sys
UVCFTR_S 98338000 98340000 Thu Jun 26 02:25:19 2008 (4863526f) 00008ab4 UVCFTR_S.SYS
tos_sps32 8713a000 87181000 Tue Jun 23 23:36:21 2009 (4a41bb55) 000454e1 tos_sps32.sys
Your ADC Analyzer/SwiftForth/Disspy - ?SpeedFan? driver is from 1996. Recommend removing the software. The other two drivers do not seem to be of concern.
Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\lShifta\Windows7_Vista_jcgriff2\042112-18985-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.x86fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0x84600000 PsLoadedModuleList = 0x847494d0
Debug session time: Fri Apr 20 18:38:29.684 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:44.709
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
........
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00001001, Verifier predicted potential deadlock.
Arg2: 93738e4c, Lock address.
Arg3: 90c3e6f0, Verifier internal data.
Arg4: 00000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for srs_sscfilter_i386.sys
*** ERROR: Module load completed but symbols could not be loaded for srs_sscfilter_i386.sys
BUGCHECK_STR: 0xc4_1001
DRIVER_DEADLOCK: Deadlock detection not initialized
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 84936f1f to 846def1c
STACK_TEXT:
9f96c204 84936f1f 000000c4 00001001 93738e4c nt!KeBugCheckEx+0x1e
9f96c224 84942522 93738e4c 84947d40 00000000 nt!VerifierBugCheckIfAppropriate+0x30
9f96c238 849416ca 90c3e6f0 00000000 90c3e6f0 nt!ViDeadlockReportIssue+0x2f
9f96c25c 84941db6 93738e4c 00000001 00000001 nt!ViDeadlockAnalyze+0x1cb
9f96c2ec 8493de95 93738e4c 00000001 9144d450 nt!VfDeadlockAcquireResource+0x2da
9f96c314 8493c9e9 00000001 9f96c344 00000000 nt!ViKeObjectAcquired+0x3e
9f96c33c 92bb13b4 93738e4c 00000000 00000000 nt!VerifierKeWaitForSingleObject+0x118
9f96c358 92bb7759 93738d78 966f4278 a3d9ef00 ks!CKsDevice::AcquireDevice+0x41
9f96c370 849316c3 9143b430 a3d9ef00 a3d9efd4 ks!CKsDevice::DispatchCreate+0x49
9f96c394 84637545 00000000 a3d9eff8 9143b430 nt!IovCallDriver+0x258
9f96c3a8 849433d0 9669bb58 a3d9ef00 91549738 nt!IofCallDriver+0x1b
9f96c3c0 849316c3 915497f0 a3d9ef00 90c3e668 nt!ViFilterDispatchGeneric+0x5e
9f96c3e4 84637545 00000000 90c3e6c4 91549738 nt!IovCallDriver+0x258
9f96c3f8 84846427 ec0cb082 9f96c5a0 00000000 nt!IofCallDriver+0x1b
9f96c4d0 84825c2e 87741bc8 857297a8 87728498 nt!IopParseDevice+0xed7
9f96c54c 84836040 00000000 9f96c5a0 00000240 nt!ObpLookupObjectName+0x4fa
9f96c5a8 8482cb1e 9f96c750 877297a8 914ab900 nt!ObOpenObjectByName+0x165
9f96c624 84832ca4 9f96c7b0 c0000000 9f96c750 nt!IopCreateFile+0x673
9f96c66c 8463e20a 9f96c7b0 c0000000 9f96c750 nt!NtOpenFile+0x2a
9f96c66c 8463c581 9f96c7b0 c0000000 9f96c750 nt!KiFastCallEntry+0x12a
9f96c6fc 849454f9 9f96c7b0 c0000000 9f96c750 nt!ZwOpenFile+0x11
9f96c724 92b9b024 9f96c7b0 c0000000 9f96c750 nt!VfZwOpenFile+0x42
WARNING: Stack unwind information not available. Following frames may be wrong.
9f96c784 92b9a809 9f96c7b0 00000000 00000000 srs_sscfilter_i386+0x3c024
9f96c7a8 92b9a987 00000000 a4906da0 92b889d8 srs_sscfilter_i386+0x3b809
9f96c808 92b61dd8 0000bb80 00000000 a34d2f98 srs_sscfilter_i386+0x3b987
9f96c824 92bb592c a53dcfc0 00000000 00000000 srs_sscfilter_i386+0x2dd8
9f96c840 92bb9d7f 9f96c894 a34d2f98 00000000 ks!CKsPin::ValidateDataFormat+0x24
9f96c86c 92bb6250 c0000272 92b88a30 00000001 ks!KspValidateDataFormat+0x27c
9f96c8a4 92bb5fd8 a34d2f98 00000068 92b89020 ks!CKsPin::SetDataFormat+0xe0
9f96c904 92bb6326 8cdb4f00 8ccd8ebc a6930fa0 ks!CKsPin::Init+0x43d
9f96c93c 92bb5648 8cdb4f00 8ccd8ebc a6930fa0 ks!KspCreatePin+0x98
9f96c980 92bb914f 9143b430 8cdb4f00 00000000 ks!CKsFilter::DispatchCreatePin+0xb9
9f96c9a4 92bb7825 9143b430 00000000 907ba850 ks!DispatchCreate+0xe0
9f96c9c0 849316c3 9143b430 8cdb4f00 8cdb4fd4 ks!CKsDevice::DispatchCreate+0x115
9f96c9e4 84637545 00000000 8cdb4ff8 9143b430 nt!IovCallDriver+0x258
9f96c9f8 849433d0 9665cb30 8cdb4f00 91549738 nt!IofCallDriver+0x1b
9f96ca10 849316c3 915497f0 8cdb4f00 90c3e920 nt!ViFilterDispatchGeneric+0x5e
9f96ca34 84637545 00000000 90c3e97c 91549738 nt!IovCallDriver+0x258
9f96ca48 84846427 ec0cbf72 90c3ed68 90dcea28 nt!IofCallDriver+0x1b
9f96cb20 848812de 91549738 857297a8 918da3a8 nt!IopParseDevice+0xed7
9f96cb60 84825c2e 90c3ed68 877297a8 918da3a8 nt!IopParseFile+0x51
9f96cbdc 84836040 000001bc 9f96cc30 00000040 nt!ObpLookupObjectName+0x4fa
9f96cc38 8482cb1e 0024e1c0 877297a8 90c3e901 nt!ObOpenObjectByName+0x165
9f96ccb4 84850396 0024e238 c0000000 0024e1c0 nt!IopCreateFile+0x673
9f96cd00 8463e20a 0024e238 c0000000 0024e1c0 nt!NtCreateFile+0x34
9f96cd00 77317094 0024e238 c0000000 0024e1c0 nt!KiFastCallEntry+0x12a
0024e1ec 00000000 00000000 00000000 00000000 0x77317094
STACK_COMMAND: kb
FOLLOWUP_IP:
ks!CKsDevice::AcquireDevice+41
92bb13b4 5d pop ebp
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: ks!CKsDevice::AcquireDevice+41
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ks
IMAGE_NAME: ks.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799d9
FAILURE_BUCKET_ID: 0xc4_1001_VRF_ks!CKsDevice::AcquireDevice+41
BUCKET_ID: 0xc4_1001_VRF_ks!CKsDevice::AcquireDevice+41
Followup: MachineOwner
---------
SRS Audio Sandbox driver seems to be involved in this Driver Verifier Enabled crash.
Your other crashes were network related. Did you use DriverMax to update the network driver before these problems started? We do not recommend automated driver update software because it often installed "updated" drivers for devices that are not exactly the same as those installed on the system being updated. If the driver is updated for a similar device instead of the actual device, this can cause conflicts on the system.
It is also not necessary to keep all drivers up to date, and doing so as a regular maintenance task can cause problems like you are seeing now. Not all driver updates improve stability.
It is better to get the driver updates from Toshiba and nowhere else unless you are actually having problems with the system and those problems seem to be driver related. Were you having any problems prior to the driver updates?
If you are unable to roll back the drivers to drivers that provide stability, I would recommend that you
Repair Install Windows 7 and then only get your drivers from your Toshiba website or the Toshiba drivers disc. To repair install, use steps 1-3 of
Clean Reinstall - Factory OEM Windows 7 to get the installation media for Windows 7; you will want Windows 7 Ultimate SP1-U ISO and the x86 version appropriate for your language.
Quote