BSOD and crashes - during encoding

[videofx]

I have an editing machine and have been plagued with crashes when encoding in Adobe CS5. I have taken out all extra cards, and now with core i7 and quadro 3800 I am still unable to complete a encoding process.
Here is my latest bccode:

Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFFA8054E907FC
BCP2: 0000000000000001
BCP3: FFFFF960000FAA4E
BCP4: 0000000000000005
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

I am almost suspecting a bad cpu.....

 

[ttran]

Hi and Welcome to SF videofx

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

memory corruption was blamed in the minidump. I would download third party called memtestx86, burn it to CD using iso recorder http://isorecorder.alexfeinman.com/W7.htm , and let it run for at least 7 passes.

Also, in looking through your loaded drivers, I see you have this old driver:

ASACPI   ASACPI.sys   Mon Mar 28 09:30:36 2005 (42476C4C)

It is dated from 2005, which is known for causing BSOD, please update it, follow the instruction in this article:
http://www.sevenforums.com/787431-post2.html

BugCheck 50, {fffffa8054e907fc, 1, fffff960000faa4e, 5}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------
PROCESS_NAME:  explorer.exe

 

[videofx]

Well, that is interesting. Where do you find the meaning of the various Bccodes?

Is there a guide or website?

I actually just formatted my C drive and reinstalled windows 7 and the programs, so it should be all clean. The core i7 was installed originally with dual channel memory and then the mobo and memory were replaced with the proper trriple channel. I did memory checks and diagnostics and everything checked out. still the BSOd and crashes. Not sure if something could be wrong with the cpu.
I will replace that old driver, but it was just installed from the fresh install.

 

[videofx]

this is the latest from the last crash:

Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF880033466B8
BCP3: FFFFF88003345F10
BCP4: FFFFF88001310173
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

 

[Tews]

Hi videofx ... Welcome to SevenForums...

ttran is spot on with his analysis... this is a memory problem... You need to Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 7passes.

 

[videofx]

I replaced the ASACPI file, sitll crashes.

I did run a memory diagnostics check the other day- it was ok. I will try Memtest86.
If the memory controller in the cpu was damaged, would it give results like bad memory?

 

[ttran]

If you run the memtestx86 and get error, please run memtestx86 on individual Ram stick to find a good one, then test it on different slots to find a bad motherboard slots (It's possible).

When you replace the ASACPI file, make sure it date 2009 until now.

 

[reventon]

Hi,

this is the latest from the last crash:

Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF880033466B8
BCP3: FFFFF88003345F10
BCP4: FFFFF88001310173
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Can you upload the minidump please - the more BSOD dumps we have the more likely it is that a suspect driver is mentioned.

From the code I can see that the above BSOD is a 0x24 NTFS_FILE_SYSTEM error - usually meaning disk hardware, memory corruption.

What hard drives are you using?

If the memory controller in the cpu was damaged, would it give results like bad memory?

As in MEMORY_CORRUPTION - most certainly.

CPU stress test (note that this is not 100% accurate and we have seen it not pick up a failed CPU before):

Prime95 Setup:
Download from: Free Software - GIMPS
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Regards,
Reventon

 

[videofx]

The hard drives are Hitachi E7K1000 - one just for OS and programs

I have a 16 drive raid for data.

attached are more mini dumps.

The one thing I am starting to think is the problem is the cpu - it was used with dual channel memory - higher voltage, with problems, and now it is in a new mobo and using the low voltage triple channel memory. I wish I had another cpu to throw in and see if that cures it. It usually crashes during the encoding process which pushes cpu usage up to 90 plus percent.

 

[ttran]

This new dmp file still point to hard drive and memory issue. Please run the memtestx86 as suggest, then run this:
http://www.sevenforums.com/tutorials/433-disk-check.html
and HD Diagnostic

Please run the CPU stress test as Reventon suggested, he is a really good hardware specialist

BugCheck 50, {fffffa8054e907fc, 1, fffff960000faa4e, 5}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------
BugCheck F4, {3, fffffa800c896b30, fffffa800c896e10, fffff80002bd3240}

Probably caused by : wininit.exe

Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff880033466b8, fffff88003345f10, fffff88001310173}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFcbTableCompare+3 )

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

Let us know if you need help

Tuan

 

[videofx]

Running memtest 86 and have gotten 6 failures already
Only on pass 0 and up to test #7

 

[ttran]

Have you done what I suggested? Test individual to find good ram sticks, then test one of them on different slot to find bad motherboard slots. If all individual Ram test give you no error, as well as slots=>you have compatibility issue !