Solved Frequent BSOD's while playing videos (24, 05, 3B, C4, 1A, and others)

[Kreubs]

My dad's computer has been BSOD'ing like mad. He said it happens most while playing videos. When I use his computer, they happen at any time doing any menial task. I am no stranger to computers, but I have really come to the end of my rope on this one.

Specs:
CPU: AMD Athlon 64 X2 5800+
Motherboard: ASUS M2A-VM
GPU: NVIDIA GeForce 610 1GB
RAM: 4Gb DDR2-800

The computer has been BSOD'ing on and off for a few months, but recently it has gotten much worse. I ran a memtest and one of the chips was bad, so I replaced it. It then went from BSOD's to just locking up. I noticed the GPU (an ancient 8500 GT) was badly overheating. It would idle at 85° C and go into the mid/upper 90's on use. It was about 4 1/2 years old with passive cooling. I am guessing the paste on it went bad, so I just got a new card and an extra case fan.

Since the new RAM chip, I have had memtest run 4 passes with no errors. I am wondering if I have a RAM incompatibility, though? I have 2 Kingmax chips on channel A, and 2 Sycron Chips on channel B. CPU-z shows that all of the chips have the same timings, except one, its tRC is 24, and the have rest 23. I can post the CPU-z info if need be.

I activated Driver Verifier, and got a failure from dne64x.sys. I removed a CISCO VPN driver that had to do with it, but I haven't reactivated verifier to see if it has been resolved.

New single RAM on 5/17/13 and new GPU on the 5/19/13.

Info on the last BSOD:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800a93fa48, fffff8800a93f2a0, fffff880014e9e9b}

Probably caused by : Ntfs.sys ( Ntfs+a6e9b )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800a93fa48
Arg3: fffff8800a93f2a0
Arg4: fffff880014e9e9b

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


EXCEPTION_RECORD:  fffff8800a93fa48 -- (.exr 0xfffff8800a93fa48)
ExceptionAddress: fffff880014e9e9b (Ntfs+0x00000000000a6e9b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800a93f2a0 -- (.cxr 0xfffff8800a93f2a0)
rax=ff31f8a009f7fa90 rbx=fffffa8008855b30 rcx=fffffa8008855b30
rdx=fffffa8008520060 rsi=fffff8800a93fdf0 rdi=fffff8a0018875d0
rip=fffff880014e9e9b rsp=fffff8800a93fc80 rbp=fffffa8008855b30
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8008855b30
r11=0000000000000000 r12=fffff880084d5ac0 r13=0000000000000000
r14=fffff880084d5ab0 r15=fffff880084d5b38
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
Ntfs+0xa6e9b:
fffff880`014e9e9b 0fbaa0980000001f bt      dword ptr [rax+98h],1Fh ds:002b:ff31f8a0`09f7fb28=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Maxthon.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350c100
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs+a6e9b
fffff880`014e9e9b 0fbaa0980000001f bt      dword ptr [rax+98h],1Fh

FAULTING_IP: 
Ntfs+a6e9b
fffff880`014e9e9b 0fbaa0980000001f bt      dword ptr [rax+98h],1Fh

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff880014e7701 to fffff880014e9e9b

STACK_TEXT:  
fffff880`0a93fc80 fffff880`014e7701 : fffffa80`08855b30 fffffa80`087ed320 fffff880`0a93fe50 fffff880`0a93fea0 : Ntfs+0xa6e9b
fffff880`0a93fd50 fffff880`0145140d : fffffa80`08855b30 fffffa80`087ed320 fffff880`084d5ab0 fffffa80`08520000 : Ntfs+0xa4701
fffff880`0a93ff30 fffff800`032cc6f7 : fffff880`084d5a20 59989f7d`9a120fea ca8fef06`f73c8f46 3bdd06fe`2cbba65f : Ntfs+0xe40d
fffff880`0a93ff60 fffff800`032cc6b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffff880`084d58f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs+a6e9b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5167f5fc

STACK_COMMAND:  .cxr 0xfffff8800a93f2a0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs+a6e9b

BUCKET_ID:  X64_0x24_Ntfs+a6e9b

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

 

[x BlueRobot]

[COLOR="red"]BugCheck 24[/COLOR], {1904fb, fffff8800a93fa48, fffff8800a93f2a0, fffff880014e9e9b}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindStartingNode+52b )

Usual causes:  Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

ntfs.sys is the driver used to read and write to hard-drives formatted with the NTFS file system, this is usually caused by a corrupted file system/disk corruption or a corrupted IRP used by a driver.

Update BIOS:

Phoenix Technologies, LTD ASUS M2A-VM ACPI BIOS Revision 2302, [COLOR="Red"]2/5/2009[/COLOR]

Remove (at least to test):

Start Menu\Programs\Bitdefender 2012

• BitDefender Removal Support

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

   Information

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:

• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

 

[Kreubs]

Thanks for the quick reply.

The thing that bugs me the most about the ntfs bugcheck, is that I already ran the extensive check disk and it came back clean. I know it's not a file system error.

I looked into a BIOS update, but the only one newer than mine is a beta BIOS that adds AM3 support (it's an old board). Is it worth using a beta BIOS?

Virus scans came back clean.

It just gave me a 7F, so I am thinking it's the memory.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff8000358d70a}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8000358d70a

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800034ca1a9 to fffff800034cac00

STACK_TEXT:  
fffff880`009edc68 fffff800`034ca1a9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009edc70 fffff800`034c8672 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009eddb0 fffff800`0358d70a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`02f16000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlWalkFrameChain+0x3a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`034c8672 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0x7f_8_VRF_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_VRF_nt!KiDoubleFaultAbort+b2

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

 

[x BlueRobot]

I wouldn't update to a beta BIOS.

Upload the dump file in a zipped folder please.

 

[Kreubs]

I found the problem!

Before I replaced the bad video card (well, just the paste was no good, but it was old), I uninstalled the old drivers and put the new card in. It started bugchecking every 5-10 minutes with driver errors. I uninstalled the drivers again and on the next boot, the NVIDIA setup launched and it rolled back to an even older version that had been installed over. After I got rid of that one, I put the new drivers on and it hasn't crashed in 3 days.

Thanks for the help!

 

[x BlueRobot]

Welcome, glad to help, you may mark this thread as solved if you like