memory dump crash

[Morlean]

why do i get a blue screen memeory dump crash once in awhile?


Asus P8P67 LE B3 motherboard
Intel i3 2nd gen 2100 3.1ghz CPU 1155 socket
Cool Master Hyper TX3 CPU Cooler
DDR3 corsair xms3 ram 3x2 6GB installed
MSI R6670 1GB GDDR5 128 bit
Coolmaster 550w power supply
Thermaltake v3 black case
Hp 23" monitor 1920x1080 resolution
Razer Deathadder mouse /Lycosa keyboard
Conexant Falcon II NTSC video Capture tuner card
Seagate 2TB Expasiondrive
Seagate HDD 500gig main drive
Windows 7 Premium 64bit OS.

 

[Bubbaleone]

Unless you want to post the stop error code and event summary for us, nobody can help you with that vague a question.

 

[Morlean]

Source
Windows
Summary
Shut down unexpectedly
Date
7/8/2012 10:35 PM
Status
Not reported
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Files that help describe the problem
070812-21325-01.dmp
sysdata.xml
WERInternalMetadata.xml
Extra information about the problem
BCCode: 109
BCP1: A3A039D8A0164692
BCP2: 0000000000000000
BCP3: C37ABA9B4E2EC07B
BCP4: 0000000000000101
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

 

[Morlean]

im hoping this is what is needed

 

[Bubbaleone]

Source
Windows
Summary
Shut down unexpectedly
Date
7/8/2012 10:35 PM
Status
Not reported
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Files that help describe the problem
070812-21325-01.dmp
sysdata.xml
WERInternalMetadata.xml
Extra information about the problem
BCCode: 109
BCP1: A3A039D8A0164692
BCP2: 0000000000000000
BCP3: C37ABA9B4E2EC07B
BCP4: 0000000000000101
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

From Microsoft:

The CRITICAL_STRUCTURE_CORRUPTION bug check has a value of 0x00000109. This indicates that the kernel has detected critical kernel code or data corruption.

Cause

There are generally three different causes for this bug check:

1] A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1, and later versions of Windows for x64-based computers, do not allow the kernel to be patched except through authorized Microsoft-originated hot patches.

2] A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.

3] A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.

Try running MemTest86 for 24 hours to test for any bad RAM first. Make sure you're running the latest BIOS version also.

The R6670 and the Falcon II are both video capture cards, which makes me suspect there may be a driver conflict or incompatibility. Try temporarily uninstalling the Conexant, make sure the R6670 driver is updated, and test it like that for an extended period to see if the problem re-occurs.

Make sure you've got the latest Microsoft patches/updates.


.

 

[Morlean]

will give it a try Bubbaleone thanks