bsod help

[pearcie]

hi heres my new build setup:
Asus P5Q Pro Turbo motherboard
Windows 7 professional 64 bit operating system
Intel Core 2 Duo E7500 2.93GHz Socket 775 1066FSB 3MB L2 Cache Retail Boxed Processor
OCZ 4GB Kit (2x2GB) DDR2 1066MHz/PC2-8500 Reaper Memory HPC Edition Dual Channel
XFX HD 4890 XXX Edition 1GB DDR5 Dual DVI HDTV Out PCI-E Graphics
850w NorthQ Black Magic Flex Power Supplie
2 x 1TB Seagate ST310005N1D1AS-RK Barracuda 7200.11, SATA 3Gb/s, 7200rpm, 32MB Cache, 8.5 ms set up in raid
i keep getting the blue screen of death with random error codes memory has been tested lots of times with no errors also the graphis card and cpu seems to be no problems
downloaded lastet drivers from asus
heres some of the many error codes:
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.48 Locale
ID: 2057 Additional information about the problem:
BCCode: 1e BCP1: FFFFFFFFC0000005 BCP2: FFFFF80002AFC35F BCP3: 0000000000000000 BCP4: FFFFFFFFFFFFFFFF OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.48 Locale
ID: 2057 Additional information about the problem:
BCCode: 3b BCP1: 00000000C0000005 BCP2: FFFFF80002BF40F3 BCP3: FFFFF88006F2CB40 BCP4: 0000000000000000 OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1 plus many many more also installed windows 7 32 bit everything seems to work fine no crashes but i do not want to run a 32 bit operating system so please can anybody help...........

 

[TGSoldier]

Welcome.

Can you please upload your minidump file?

 

[pearcie]

will do where do i find it

 

[pearcie]

here you go thanx for help ...View attachment 27088

 

[pearcie]

attached dumps above

 

[mckillwashere]

May I ask which anti-virus you are using?

 

[zigzag3143]

here you go thanx for help ...View attachment 27088

Pearcie

After a quick look at the latest dump file it seems to have been caused by the atikmdag.sys. If I were you I would download the ati driver again and install it. You can check to see what version you have by going into device manager (type device manager in search) and look for the appropriate drivers


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


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

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
Debug session time: Sun Sep 6 19:33:54.732 2009 (GMT-4)
System Uptime: 0 days 0:05:33.339
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880042b23a6, fffff880026cb800, 0}

Probably caused by : atikmdag.sys ( atikmdag+2843a6 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880042b23a6, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880026cb800, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP:
atikmdag+2843a6
fffff880`042b23a6 66398a8c000000 cmp word ptr [rdx+8Ch],cx

CONTEXT: fffff880026cb800 -- (.cxr 0xfffff880026cb800)
rax=0000000019740800 rbx=fffff8a008180420 rcx=0000000000001974
rdx=0000003180000004 rsi=fffffa8003a91948 rdi=fffffa8006678940
rip=fffff880042b23a6 rsp=fffff880026cc1e8 rbp=000000000000022c
r8=fffffa8003a91948 r9=000000000001f6a0 r10=fffff8a008180420
r11=fffff8a0081803f0 r12=fffffa80039f8bc0 r13=00000000000009af
r14=00000000000000ac r15=fffff88000be0000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
atikmdag+0x2843a6:
fffff880`042b23a6 66398a8c000000 cmp word ptr [rdx+8Ch],cx ds:002b:00000031`80000090=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: CoDWaW.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880042b23a6

STACK_TEXT:
fffff880`026cc1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x2843a6


FOLLOWUP_IP:
atikmdag+2843a6
fffff880`042b23a6 66398a8c000000 cmp word ptr [rdx+8Ch],cx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+2843a6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5d41c3

STACK_COMMAND: .cxr 0xfffff880026cb800 ; kb

FAILURE_BUCKET_ID: X64_0x3B_atikmdag+2843a6

BUCKET_ID: X64_0x3B_atikmdag+2843a6

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

I dont have a true debugger so Im sugesting you re-install the driver while waiting for one of our debugging guru's to give you a more comprehensive analysis

KEn

 

[pearcie]

thanx zigzag3143 will give it ago im not that hopeful as i have already tried different drivers but will try again..............

 

[zigzag3143]

thanx zigzag3143 will give it ago im not that hopeful as i have already tried different drivers but will try again..............

pearcie

If that doesn't cure it upload the other bsods and we will have aa look at them all

Ken

 

[Snufffed]

thanx zigzag3143 will give it ago im not that hopeful as i have already tried different drivers but will try again..............

pearcie

If that doesn't cure it upload the other bsods and we will have aa look at them all

Ken

Ken

This seems to be another good reason for me not to RUN X64.


Snuffy

 

[pearcie]

thanx again for help didnt seem to work uninstalled old graphics driver,downloaded and installed latest ati driver still crashed bsod heres all the dump files includeing latest weird how on my partioned windows 7 pro 32 bit its as stable as hell no problems View attachment 27253

done loads of hardware test but everything seems to come out ok im worried if it is a hardware problem i may not be able to detect it.hopeing its not anyway and if it was you would think the 32 bit os would crash....

 

[Snufffed]

thanx again for help didnt seem to work uninstalled old graphics driver,downloaded and installed latest ati driver still crashed bsod heres all the dump files includeing latest weird how on my partioned windows 7 pro 32 bit its as stable as hell no problems 090909-20170-01.zip

Have you thought of letting win7 install the default drivers. and test with them. Just a thought.

 

[pearcie]

thanx again for help didnt seem to work uninstalled old graphics driver,downloaded and installed latest ati driver still crashed bsod heres all the dump files includeing latest weird how on my partioned windows 7 pro 32 bit its as stable as hell no problems 090909-20170-01.zip

Have you thought of letting win7 install the default drivers. and test with them. Just a thought.

thanx but yes done that

 

[zigzag3143]

thanx again for help didnt seem to work uninstalled old graphics driver,downloaded and installed latest ati driver still crashed bsod heres all the dump files includeing latest weird how on my partioned windows 7 pro 32 bit its as stable as hell no problems View attachment 27253

done loads of hardware test but everything seems to come out ok im worried if it is a hardware problem i may not be able to detect it.hopeing its not anyway and if it was you would think the 32 bit os would crash....

You know there is enough info here for one of our guru's with debugging to check for you . Im going to send the thread link to someone that specializes in these. 32 bit will give you less grief though.

Ken

 

[pearcie]

thanx again for help didnt seem to work uninstalled old graphics driver,downloaded and installed latest ati driver still crashed bsod heres all the dump files includeing latest weird how on my partioned windows 7 pro 32 bit its as stable as hell no problems View attachment 27253

done loads of hardware test but everything seems to come out ok im worried if it is a hardware problem i may not be able to detect it.hopeing its not anyway and if it was you would think the 32 bit os would crash....

You know there is enough info here for one of our guru's with debugging to check for you . Im going to send the thread link to someone that specializes in these. 32 bit will give you less grief though.

Ken

thanx for your help, yeh probly 32 bit would be easier but lots of people seem to rave about how good 64 is up to 32 bit so would love to run 64 bit lets hope hope one of the gurus can shed some light thanx again..........

 

[usasma]

18 dump files and only one mentions kl1.sys (took a "quick" look) - a long shot, but I'd suggest:

- Downloading a free antivirus (for use while testing). I recommend Avast Free for x64 systems - just google for it.
- Gathering up your Kaspersky product key (in case you want to reinstall later on).
- Uninstall the Kaspersky products from your system.
- IMMEDIATELY install and update the free antivirus
- Reboot and test for problems.

Running all 18 dump files now - be back in a while!

 

[usasma]

The common thread in most of the BSOD's is a memory access violation (c0000005). This is a common trait of a malfunctioning Internet Security application. I'd suggest removing Kaspersky as discussed above.

This is the dump file that blames Kaspersky: 090609-26332-01.dmp It's a STOP 0x1E error about 12th down the list.

Older drivers (2007 and earlier) loaded when the last BSOD occurred:

None

Summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 10:37:57.916 2009 (GMT-4)
System Uptime: 0 days 1:14:37.524
BugCheck A, {28, 2, 0, fffff80002b03090}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 19:59:31.482 2009 (GMT-4)
System Uptime: 0 days 0:13:01.089
BugCheck 24, {1904fb, fffff880031af658, fffff880031aeeb0, fffff80002abd871}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFreeNonpagedDataFcb+20 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 19:45:22.507 2009 (GMT-4)
System Uptime: 0 days 0:07:00.115
BugCheck 1E, {ffffffffc0000005, fffff80002afc35f, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 20:50:25.091 2009 (GMT-4)
System Uptime: 0 days 0:49:45.698
BugCheck 1000007E, {ffffffffc0000005, fffff80002d44b9b, fffff88003324868, fffff880033240c0}
Probably caused by : ntkrnlmp.exe ( nt!PspDereferenceQuotaBlock+17 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 15:02:31.628 2009 (GMT-4)
System Uptime: 0 days 1:26:32.236
BugCheck C2, {7, 1097, 405000a, fffffa8003ebfe60}
Probably caused by : dxgmms1.sys ( dxgmms1!DXGFASTMUTEX::`scalar deleting destructor'+b6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaW.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 05:33:09.262 2009 (GMT-4)
System Uptime: 0 days 0:01:38.870
BugCheck 3B, {c0000005, fffff9600011da7d, fffff880074810a0, 0}
Probably caused by : win32k.sys ( win32k!InternalBuildHwndList+39 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 15:33:12.909 2009 (GMT-4)
System Uptime: 0 days 0:01:24.516
BugCheck 3B, {c0000005, fffff80002db3a5e, fffff88002661d50, 0}
Probably caused by : ntkrnlmp.exe ( nt!PspThreadDelete+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wmi64.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 13:34:18.680 2009 (GMT-4)
System Uptime: 0 days 0:28:33.287
BugCheck 1000007E, {ffffffffc0000005, fffff88005140ff3, fffff880055d2658, fffff880055d1eb0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep  6 09:53:39.154 2009 (GMT-4)
System Uptime: 0 days 0:05:29.762
BugCheck 1A, {41201, fffff68000111408, a45000003e5a4867, fffffa80068bb280}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaWmp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep  6 09:47:20.567 2009 (GMT-4)
System Uptime: 0 days 0:23:29.643
BugCheck 1A, {41201, fffff68000123090, d430000029504847, fffffa80084d4420}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaWmp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep  6 07:20:33.356 2009 (GMT-4)
System Uptime: 0 days 2:33:58.964
BugCheck 1A, {41289, 74a04001, 1695, d700000074a04c05}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a89 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep  6 09:22:57.440 2009 (GMT-4)
System Uptime: 0 days 2:01:30.048
BugCheck 1E, {ffffffffc0000005, fffff88003ca52b0, 0, ffffffffffffffff}
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : kl1.sys ( kl1+382b0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaWmp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Sep  7 12:26:40.603 2009 (GMT-4)
System Uptime: 0 days 0:56:15.086
BugCheck 3B, {c0000005, fffff80002dd1cd6, fffff88005b4a060, 0}
Probably caused by : ntkrnlmp.exe ( nt!AlpcpDestroyBlob+26 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Sep  7 11:51:39.378 2009 (GMT-4)
System Uptime: 0 days 0:19:17.594
BugCheck 1000007E, {ffffffffc0000005, fffff8800458cff0, fffff88004fbc658, fffff88004fbbeb0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Sep  7 17:35:37.836 2009 (GMT-4)
System Uptime: 0 days 3:05:08.444
BugCheck 3B, {c0000005, fffff80002bf40f3, fffff88006f2cb40, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaW.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep  6 19:33:54.732 2009 (GMT-4)
System Uptime: 0 days 0:05:33.339
BugCheck 3B, {c0000005, fffff880042b23a6, fffff880026cb800, 0}
Probably caused by : atikmdag.sys ( atikmdag+2843a6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaW.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Sep  8 19:03:30.420 2009 (GMT-4)
System Uptime: 0 days 0:00:12.902
BugCheck A, {fffffa0006093300, 2, 0, fffff80002ad2719}
Probably caused by : serial.sys ( serial!SerialIoControl+9a1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Sep  9 14:26:11.914 2009 (GMT-4)
System Uptime: 0 days 0:34:15.522
BugCheck 1A, {41201, fffff68000102720, 9e10000059e0c847, fffffa8004600810}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaWmp.exe

 

[pearcie]

will try the antivirus thing and get back with any dump files if bsod occurs and for taking the trouble to help me out really appreciate it.............

 

[Hippeh]

I'm experiencing the same BSODs on Win7 Enterprise x64 RTM. It seems to be aggrivated by 3D gaming, though I've had it crash and restart while perfoming virus scans or even sitting idle. Since I can almost guarantee that it will crash while playing Call of Duty: World at War, I've been using that to test for results.

I've had at least 5 different reported drivers as the culprit, but atikmdag.sys seems to be the most prevalent. The latest showed ks.sys to have caused the crash. My system had been completely stable since built, and I had made no change before I started experiencing the crashes.

I was using Avast av when I first started experiencing the crashes. I tried running with AVG, BitDefender and even with no av. Each change made little difference. I had also been running the 9.7 ATI drivers for my HD4870 gfx card. After the crashes started, I tried upgrading to 9.8, then adding the 9.8 hotfix, to no avail. The most significant difference was when I tried running with no driver, instead letting it revert back to the Win7 drivers. I was able to play for about 30 minutes before it finally crashed, right about the time I thought I had figured it out.

I've also run the Windows memory test and it showed no faults. I've tried various BIOS settings starting from default and working back to where I had adjusted/tweaked. Mind you, this system was perfectly stable with slight overclocking on the CPU.

I'm in process of unistalling drivers until I hit something that seems to stabilize it again. I've just done the Audigy SE sound card drivers but have yet to stress test it, and the only thing left would be the motherboard drivers. When I get home this evening, I'll post my dumps if someone would care to compare them to pearcie's to see if there's some common link here. I get the feeling that something got buggy, perhaps with an update? I could be grasping at straws though...

BTW, you've got a wonderful community here. I'm glad to be part of it.

EDIT: I just noticed the dump summary for pearcie's crashes has alot of references to codwaw.exe/codwawmp.exe. Hmmmmm.......

 

[usasma]

Hippeh - Please start your own thread for your issues.