Chasing BSODs Down

[Gunslinger2]

Hello, first time poster here because I have no idea what else to do & no where else to turn in hopes of solving apparently multiple issues.

I will try to cover as much as I can but this has been an ongoing problem for many months now & I have tried to solve my completely random BSOD problems on and off again over the months to no avail.

The steps that I have taken as best as I can recollect to fix the BSOD errors are as follows:
------
Re-Installed Windows (multiple times as there is a boot issue where after I log in to the system the start menu/mouse cursor(with busy circle) will freeze for up to 5 minutes & longer)

Multiple Antivirus scans (by different online/offline virus/Malware detection software)

To the best of my knowledge keeping & ensuring all drivers including motherboard BIOs are up to date

Using CCleaner to clean out registry & junk

Erasing ALL system/event logs & memory dumps to start fresh in tracking down any issues related to the BSODs & log in issue
------

Now I'm at my wits end because nothing I have tried has gotten me any closer to solving the issues above so here I am posting.

Utilities that I have used to gather most of the required information are:
BSOD Dump & System File Collection app
BlueScreen Viewer
Speccy
sfc /scannow

I cannot run a System Health Report (I don't know when this stopped working but I do know that it did work sometime in the past) as I get the error msg:
"Error: An error occured while attempting to generate the report. The system cannot find the path specified."

Here are the required items from the BSOD Posting Instructions attached below:

Windows_NT6_BSOD_jcgriff2.zip - Contains files gathered from the BSOD Dump & System File Collection app

BlueScreener Viewer Reports.zip - Contains reports from the minidumps (html & txt versions)

CBS.log - log from sfc /scannow showing some files could not be repaired apparently

System Specs.txt - Full System Specs report from Speccy

 

[yowanvista]

Seems to be memory related, test your RAM
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

ASACPI.sys the 2005 version is a huge cause of BSODs

   Information

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005)

Do this if safemdoe

ASACPI.sys        fffff880`06b00000    fffff880`06b08000    0x00008000    0x42476c4c    28/03/2005 06:30:36

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffffffffff89, memory referenced
Arg2: 000000000000000f, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800036cbe0c, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003911100
 ffffffffffffff89 

CURRENT_IRQL:  f

FAULTING_IP: 
nt!KeInsertQueueDpc+ec
fffff800`036cbe0c 024889          add     cl,byte ptr [rax-77h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  tvnserver.exe

TRAP_FRAME:  fffff88009aa49c0 -- (.trap 0xfffff88009aa49c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800036cbe0c rsp=fffff88009aa4b50 rbp=fffffa80089eb5a8
 r8=0000000000000000  r9=0000000000000000 r10=fffff88009aa4c28
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
nt!KeInsertQueueDpc+0xec:
fffff800`036cbe0c 024889          add     cl,byte ptr [rax-77h] ds:0b60:ffffffff`ffffff89=??
Resetting default scope

MISALIGNED_IP: 
nt!KeInsertQueueDpc+ec
fffff800`036cbe0c 024889          add     cl,byte ptr [rax-77h]

LAST_CONTROL_TRANSFER:  from fffff800036e12a9 to fffff800036e1d00

STACK_TEXT:  
fffff880`09aa4878 fffff800`036e12a9 : 00000000`0000000a ffffffff`ffffff89 00000000`0000000f 00000000`00000000 : nt!KeBugCheckEx
fffff880`09aa4880 fffff800`036dff20 : fffff800`03649460 fffff880`09aa4a70 fffff800`03649460 fffff800`03854e80 : nt!KiBugCheckDispatch+0x69
fffff880`09aa49c0 fffff800`036cbe0c : fffff880`09aa4c30 fffffa80`099f0b60 00000000`00000000 fffffa80`099f0c68 : nt!KiPageFault+0x260
fffff880`09aa4b50 fffff880`01753488 : fffff880`09aa4ca0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeInsertQueueDpc+0xec
fffff880`09aa4be0 fffff800`036ddb3c : 00000000`000814d8 fffff880`09aa4c01 00000000`7efaa000 00000000`00000000 : ndis!ndisMiniportMessageIsr+0xa8
fffff880`09aa4c20 00000000`77bbfd84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0x16c
00000000`016ef9c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bbfd84


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ndis!ndisMiniportMessageIsr+a8
fffff880`01753488 84c0            test    al,al

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  ndis!ndisMiniportMessageIsr+a8

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

 

[Gunslinger2]

Sorry for taking so long to reply but here's the skinny as of now. Running Memtest86+ at the moment, currently I have ran the standard test for 7 hours / 3 passes in that amount of time.

Right now I am running the bit fade test (currently at 43 minute mark) but the Pass & Test %'s are not showing any progress. I don't know if that is indicative of any sort of problem how it does say that the bit fade test takes 90 minutes, 2 patterns so I'm not sure.

As for the ASACPI.SYS version issue I did check and make sure that it was not an '05 version. Still experiencing multiple BSODs for whatever reason. If anymore information is required I'll be happy to provide it as these issues are becoming so problematic that I can't trust to be in the middle of something on the PC and it just BSOD on me.

 

[Gunslinger2]

update: Bitfade test also shows no errors

 

[Gunslinger2]

2 new BSOD's in the span of minutes. 1 BSOD & then another upon immediate reboot/logon.

Updating the required BSOD posting files required but according to BlueScreenViewer the BSOD's where due to something related ntoskrnl.exe, tcpip.sys

 

[yowanvista]

Are you using SVCD2DVD? I suspect one of its process to have caused the last Crash
Update any Creative software associated with your sound card
Creative Worldwide Support

Update the Logitech QuickCam software
http://www.logitech.com/en-us/support-downloads

Remove any Asus Utilities such as Asus Update/ PC Probe

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff800036a31d5, The address that the exception occurred at
Arg3: 0000000000000002, Parameter 0 of the exception
Arg4: fffff8000361f000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nt!KeSetEvent+5e7
fffff800`036a31d5 ff              ???

EXCEPTION_PARAMETER1:  0000000000000002

EXCEPTION_PARAMETER2:  fffff8000361f000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  ffmpeg.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800036ea5d8 to fffff8000369ed00

FAILED_INSTRUCTION_ADDRESS: 
nt!KeSetEvent+5e7
fffff800`036a31d5 ff              ???

STACK_TEXT:  
fffff880`03192c78 fffff800`036ea5d8 : 00000000`0000001e ffffffff`c000001d fffff800`036a31d5 00000000`00000002 : nt!KeBugCheckEx
fffff880`03192c80 fffff800`0369e382 : fffff880`03193458 00000000`00000400 fffff880`03193500 fffffa80`07eb9da0 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`03193320 fffff800`0369c4df : fffff880`03193500 00000000`00000202 00000000`00000000 fffff880`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`03193500 fffff800`036a31d5 : fffff880`018b30e7 00000000`00000003 00000000`00000002 00000000`002869fe : nt!KiInvalidOpcodeFault+0x11f
fffff880`03193698 00000000`00000000 : 00000000`00000400 fffff880`03193ac8 fffff800`0369a596 00000000`00000002 : nt!KeSetEvent+0x5e7


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeSetEvent+5e7
fffff800`036a31d5 ff              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KeSetEvent+5e7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0x1E_BAD_IP_nt!KeSetEvent+5e7

BUCKET_ID:  X64_0x1E_BAD_IP_nt!KeSetEvent+5e7

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

 

[Gunslinger2]

I've never even heard of SVCD2DVD so no I don't use it. However I see the ffmpeg.exe which I believe is part of my TV recording process. I use my Hauppauge WinTV-HVR-1600 to record shows & use MCEBuddy to automatically convert/move recordings to my media drive. I believe MCEBuddy uses ffmpeg to do the conversion.

I have no ASUS utilities installed that I can find. It seems that I have the latest drivers for the Creative Soundblaster X-Fi XtremeGamer card (2.18.0015) & updating the camera drivers at the moment.

 

[Gunslinger2]

3 BSODs today alone, I'm sure there will be more. Seriously considering doing a drive wipe & fresh install even though it's not something I want to do because of the amount of customization I've done to the system & files that I have. Dumps included

*hangs head in shame & frustration*

 

[yowanvista]

You CPU seems to have cause the latest crash

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  d

EXCEPTION_RECORD:  fffff8800318c8c8 -- (.exr 0xfffff8800318c8c8)
ExceptionAddress: fffff800036dbd4d (nt!KiSecondaryClockInterrupt+0x000000000000013d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800318c970 -- (.trap 0xfffff8800318c970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ad521bb272156c00 rbx=0000000000000000 rcx=0000000000000011
rdx=000000000001642e rsi=0000000000000000 rdi=0000000000000000
rip=fffff800036dbd4d rsp=fffff8800318cb00 rbp=fffff8800318cb80
 r8=000000000001a7ed  r9=0000000000000000 r10=0000000000015657
r11=fffff88003164180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
nt!KiSecondaryClockInterrupt+0x13d:
fffff800`036dbd4d 65488b0c2520000000 mov   rcx,qword ptr gs:[20h] gs:ffff:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800036c76be to fffff800036cfcd0

STACK_TEXT:  
fffff880`0318b9a8 fffff800`036c76be : 00000000`00000000 fffffa80`0b2862a0 fffff880`0318c120 fffff800`036fb890 : nt!KeBugCheck
fffff880`0318b9b0 fffff800`036fb55d : fffff800`038d66d4 fffff800`03814ccc fffff800`03650000 fffff880`0318c8c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0318b9e0 fffff800`036fa335 : fffff800`038170fc fffff880`0318ba58 fffff880`0318c8c8 fffff800`03650000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0318ba10 fffff800`0370b3b1 : fffff880`0318c8c8 fffff880`0318c120 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x415
fffff880`0318c0f0 fffff800`036cf382 : fffff880`0318c8c8 00000000`00000000 fffff880`0318c970 fffff880`03164180 : nt!KiDispatchException+0x135
fffff880`0318c790 fffff800`036cdc8a : 00000000`00000000 fffff880`06d1ed03 fffff880`00000000 00000000`00000031 : nt!KiExceptionDispatch+0xc2
fffff880`0318c970 fffff800`036dbd4d : 00000000`00000000 fffff880`0318cb80 fffff880`03164180 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`0318cb00 fffff880`02f787f2 : fffff800`036d9509 00000000`002869fe fffffa80`08b09218 fffff880`0316ef80 : nt!KiSecondaryClockInterrupt+0x13d
fffff880`0318cc98 fffff800`036d9509 : 00000000`002869fe fffffa80`08b09218 fffff880`0316ef80 00000000`00000001 : amdppm!C1Halt+0x2
fffff880`0318cca0 fffff800`036c79fc : fffff880`03164180 fffff880`00000000 00000000`00000000 fffff880`1120f160 : nt!PoIdle+0x52a
fffff880`0318cd80 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318cd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
amdppm!C1Halt+2
fffff880`02f787f2 c3              ret

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  amdppm!C1Halt+2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: amdppm

IMAGE_NAME:  amdppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x1E_amdppm!C1Halt+2

BUCKET_ID:  X64_0x1E_amdppm!C1Halt+2

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

 

[Gunslinger2]

Small FFTs - CPU & motherboard was @ 190+ degrees Fahrenheit after 7 minutes, produced no errors other than proceeding to tempt me to throw an egg on it to see if it would cook....

Large FFTs - "FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected" on 2nd or 3rd core

Blend - "FATAL ERROR: Rounding was 0.4921875, expected less than 0.4
Hardware failure detected" on 1st or 3rd core

I can rerun the test again after the PC cools but the heat issue concerns me because I can't afford to cook the PC as I can't afford to rebuild another computer at the moment.

 

[yowanvista]

Small FFTs - CPU & motherboard was @ 190+ degrees Fahrenheit after 7 minutes, produced no errors other than proceeding to tempt me to throw an egg on it to see if it would cook....

Large FFTs - "FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected" on 2nd or 3rd core

Blend - "FATAL ERROR: Rounding was 0.4921875, expected less than 0.4
Hardware failure detected" on 1st or 3rd core

I can rerun the test again after the PC cools but the heat issue concerns me because I can't afford to cook the PC as I can't afford to rebuild another computer at the moment.

This means you've got a defective CPU, you should get another one

 

[Gunslinger2]

A few not so nice four letter words are coming to mind right about now....:huh:.

Well I'm certainly open to suggestions on what I could replace/upgrade the CPU to without have to buy a new board, ram, psu...actually I need a new power supply...and a SLI capable board but that would involve just building a new PC.

This is my current setup:

Case - Newegg.com - APEVIA X-Alien ATXA7AW-BL/420 Blue Aluminum Server Computer Case 420W Power Supply
Motherboard - http://www.newegg.com/Product/Product.aspx?Item=N82E16813131603
CPU - Newegg.com - AMD Athlon II X3 425 Rana 2.7GHz 3 x 512KB L2 Cache Socket AM3 95W Triple-Core Processor ADX425WFGIBOX
RAM - Newegg.com - G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-4GBRL
Graphics Card - Newegg.com - PNY VCG941024GXPB GeForce 9400 GT 1GB 128-bit DDR2 PCI Express 2.0 x16 HDCP Ready Low Profile Video Card

Not sure if current board could support either of the CPU's I'm looking at though.

1. AMD Phenom II X4 965 Black Edition Deneb 3.4GHz 4 x 512KB L2 Cache 6MB L3 Cache Socket AM3 125W Quad-Core Processor HDZ965FBGMBOX

2. AMD Athlon II X4 640 Propus 3.0GHz 4 x 512KB L2 Cache Socket AM3 95W Quad-Core Desktop Processor ADX640WFGMBOX

Leaning toward #1 though as a quad core should suit my gaming needs WoW, BF2, CoD, SW:TOR

In conclusion I guess if the CPU is defective then there's not much I can do other than put up with the BSOD issues until I can afford to upgrade/rebuild. If it weren't for the BSOD issues this PC would be great but with all these problems I'm having trying to fix every blue screen error one at time just...well ...sucks.

 

[yowanvista]

A few not so nice four letter words are coming to mind right about now....:huh:.

Well I'm certainly open to suggestions on what I could replace/upgrade the CPU to without have to buy a new board, ram, psu...actually I need a new power supply...and a SLI capable board but that would involve just building a new PC.

This is my current setup:

Case - Newegg.com - APEVIA X-Alien ATXA7AW-BL/420 Blue Aluminum Server Computer Case 420W Power Supply
Motherboard - Newegg.com - ASUS M4A77TD AM3 AMD 770 ATX AMD Motherboard
CPU - Newegg.com - AMD Athlon II X3 425 Rana 2.7GHz 3 x 512KB L2 Cache Socket AM3 95W Triple-Core Processor ADX425WFGIBOX
RAM - Newegg.com - G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-4GBRL
Graphics Card - Newegg.com - PNY VCG941024GXPB GeForce 9400 GT 1GB 128-bit DDR2 PCI Express 2.0 x16 HDCP Ready Low Profile Video Card

Not sure if current board could support either of the CPU's I'm looking at though.

1. AMD Phenom II X4 965 Black Edition Deneb 3.4GHz 4 x 512KB L2 Cache 6MB L3 Cache Socket AM3 125W Quad-Core Processor HDZ965FBGMBOX

2. AMD Athlon II X4 640 Propus 3.0GHz 4 x 512KB L2 Cache Socket AM3 95W Quad-Core Desktop Processor ADX640WFGMBOX

Leaning toward #1 though as a quad core should suit my gaming needs WoW, BF2, CoD, SW:TOR

In conclusion I guess if the CPU is defective then there's not much I can do other than put up with the BSOD issues until I can afford to upgrade/rebuild. If it weren't for the BSOD issues this PC would be great but with all these problems I'm having trying to fix every blue screen error one at time just...well ...sucks.

Yes it supports both CPUs
ASUSTeK Computer Inc. - Motherboards- ASUS M4A77TD PRO