Here is my build...
CPU: Intel Core i7 920
MB: Asus P6X58D Premium
RAM: Corsair Dominator DDR3 6GB 1600 (3x2GB sticks) (TR3X6G1600C8D)
VGA: XFX ATI 5870
HDD: WD Caviar Black 1 TB 32 MB Cache, 7200 RPM SATA II
Cooling: Corsair H50
Case: Coolermaster HAF 932
PWR: Corsair 1000HX 1000-Watt
Thanks for any help that can be provided
windows debugger came up with this for the first three
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\drivers\Lycosa.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
Probably caused by : Lycosa.sys ( Lycosa+1267 )
Followup: MachineOwner
---------
2: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, 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: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+0
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002e69c2e to fffff80002e71ed0
STACK_TEXT:
fffff880`02f8bc38 fffff800`02e69c2e : 00000000`00000000 fffff880`03f0a3f1 fffff880`02f8c440 fffff800`02e9ee28 : nt!KeBugCheck
fffff880`02f8bc40 fffff800`02e97bed : fffff800`0307ec24 fffff800`02fb7a3c fffff800`02e00000 fffff880`02f8c3a0 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8bc70 fffff800`02e9f250 : fffff800`02fbfb5c fffff880`02f8bce8 fffff880`02f8c3a0 fffff800`02e00000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8bca0 fffff800`02ea082e : fffff880`02f8c3a0 fffff880`02f8c440 00000000`00000001 00000000`0000000b : nt!RtlDispatchException+0x410
fffff880`02f8c380 fffff800`02ece7c2 : fffffa80`00000000 fffffa80`07fe4000 fffffa80`07fff4c0 fffff880`03f8a54a : nt!RtlRaiseStatus+0x4e
fffff880`02f8c920 fffff880`039f1267 : fffffa80`087eddc0 00000000`00000000 fffffa80`078568b0 fffffa80`07856a00 : nt! ?? ::FNODOBFM::`string'+0xf63c
fffff880`02f8c9a0 fffffa80`087eddc0 : 00000000`00000000 fffffa80`078568b0 fffffa80`07856a00 00000000`00000000 : Lycosa+0x1267
fffff880`02f8c9a8 00000000`00000000 : fffffa80`078568b0 fffffa80`07856a00 00000000`00000000 fffffa80`087edf10 : 0xfffffa80`087eddc0
STACK_COMMAND: kb
FOLLOWUP_IP:
Lycosa+1267
fffff880`039f1267 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: Lycosa+1267
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Lycosa
IMAGE_NAME: Lycosa.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ac2e27e
FAILURE_BUCKET_ID: X64_0x1E_Lycosa+1267
BUCKET_ID: X64_0x1E_Lycosa+1267
Followup: MachineOwner
---------
2: kd> lmvm Lycosa
start end module name
fffff880`039f0000 fffff880`039f4f80 Lycosa T (no symbols)
Loaded symbol image file: Lycosa.sys
Image path: \SystemRoot\system32\drivers\Lycosa.sys
Image name: Lycosa.sys
Timestamp: Wed Sep 30 05:45:50 2009 (4AC2E27E)
CheckSum: 00014D02
ImageSize: 00004F80
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
from the first three crashes citing Lycosa+1267,
lycosa.sys is I think your Razer Tarantula Keyboard Driver, try an unninstall or reinstall or use another keyboard for debugging purposes, possibly run sfc /scannow to see if theres a corrupted driver ?
the fourth .dmp file was
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88003e20ff0, fffff8800212e698, fffff8800212def0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0 )
Followup: MachineOwner
---------
and for
bucheck 0x1e naming
dxgmms1.sys i would advise update or rollback your video drivers or change your video card ?
also for these
0x1e errors Probable Cause "win32k.sys" are normally caused by Invalid Memory or access violations - probably caused by
hardware.
Test your memory to get consistent results by burning to CD (using an ISO burner) & running from boot
memtest86+ for at least 5 passes and moving the sticks between slots to verify motherboard ram slots work as well as the ram sticks.
Also, check the motherboard
bios for correct settings for Vdimm (
RAM voltage, check the RAM maker's site for correct settings) and
timings as well as all settings in general.
Also check your CPU (L2 Cache) by running
prime95 for a cache-parity error on the CPU. This will detect an error in minutes if any.
make sure
your BIOS is up to date and also replace or remove these drivers .........
pcouffin.sys fffff880`03ecb000 fffff880`03edf380 0x00014380 0x457584a2 05/12/2006 14:39:30
WUSB54GCv3.sys fffff880`03830000 fffff880`038fb000 0x000cb000 0x48ace7ab 21/08/2008 03:57:31
purendis.sys fffff880`039c4000 fffff880`039d0000 0x0000c000 0x490695a0 28/10/2008 04:31:28
pnarp.sys fffff880`039b8000 fffff880`039c4000 0x0000c000 0x4906a9ac 28/10/2008 05:57:00
as they are old and out of date ?
Patin-Couffin VSO Software is related to CD/DVD burning software
WUSB54GCv3.sys is possibly a linksys Compact Wireless-G USB Network Adapter ?
purendis.sys is possibly by Network Magic\Pure Networks, Inc and is your NDIS Relay Driver ?
pnarp.sys is likely a driver for this component ?
please take your time run and check all these tests if possible and let us know the results ?