BSOD when Ripping Movies, Memory corruption related?

Hello all!

Built a system in January, solid as a rock ever since. Started ripping my dvd collection a week or two back, and started getting BSOD's after the third or fourth movie I ripped. Have posted my system stats elsewhere on the net and basically think that my ram is bad. Can this be confirmed? Also, assuming my BSOD's are ram related, is what I've attached to this post enough information to make a guess as to WHY my ram is going bad all of a sudden? The BSOD's only happen when ripping DVD using Handbrake.

Else where on the net, a forum reported to me that a memory leak can occurr between my Norton Security Suite and my Cisco VPN client. Can anyone confirm?

Edit: Running Win7 x64 on an AMD Phenom X4 965, 4 gb of Geil ddr3 (used to be 8), a Kingston SSD, HIS Radeon HD6850, and Jetway HZ03-GT-LF motherboard. Thanks.


Thanks so much,
G

Anybody?

grock1722 said:

Hello all!

Built a system in January, solid as a rock ever since. Started ripping my dvd collection a week or two back, and started getting BSOD's after the third or fourth movie I ripped. Have posted my system stats elsewhere on the net and basically think that my ram is bad. Can this be confirmed? Also, assuming my BSOD's are ram related, is what I've attached to this post enough information to make a guess as to WHY my ram is going bad all of a sudden? The BSOD's only happen when ripping DVD using Handbrake.

Else where on the net, a forum reported to me that a memory leak can occurr between my Norton Security Suite and my Cisco VPN client. Can anyone confirm?

Edit: Running Win7 x64 on an AMD Phenom X4 965, 4 gb of Geil ddr3 (used to be 8), a Kingston SSD, HIS Radeon HD6850, and Jetway HZ03-GT-LF motherboard. Thanks.


Thanks so much,
G

G

The two most recent point to hardware.


Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

Some generic advice.

If you are overclocking STOP. return to the default settings at least for now.
If you are running a RAID update its driver.


You can read more on this error and what to try here... Stop 0x124 - what it means and what to try