BSOD is killing me

GT40FIED said:

I'm about at my wit's end with my computer. It's practically brand new (about 2 months old). I'm actually having to re-type this because it BSOD'ed me while typing my original post about it BSOD'ing me. This happens at the very least 2-3 times a day. The quick and dirty rundown of critical components are an AMD Phenom II X6 1100T, NVIDIA GTX 460 2GB, 8GB of Corsair (had a brainfart when registering and put Crucial) DDR3 1600Mhz dual channel memory, and a Gigabyte 870A-UD3 MoBo.

The problem I have is that the BSOD messages are all over the place. Everything from IRQL not less or equal, system service exception, page fault in non-paged area, win32k.sys, ntfs.sys, and so on. I'll attach the dump logs, but the perfmon report kept telling me there was an error while generating the file. I'm using a retail copy of Windows 7 Ultimate x64. This is not the original OS...the original was the same version but gave me even more issues so I reinstalled a different version (clean install, not a repair job). I've run memtest86+ through about 4-5 passes and came back with no errors. I've tried to keep my driver installation to a minimum so I'm hoping that's not an issue. The problem seems to happen most often with the processor under moderate load (30%-60%) and around a temp of 100F if the fan controller display is to be believed. Memory usage is rarely above 1-1.5GB (again, if the Nexus display is to be believed) and again, memtest reported no errors. So I'm stumped and beginning to get more than a bit frustrated, so any help would be appreciated. if I've left anything out, my apologies, it's my first post. I tried to follow all the directions in the BSOD sticky.

Several problems

1-Old, really old drivers from as far back as 2005

Code:

  Cardex TBPanel video conversion app/Configuration utility for Gainward graphics cards 2005.

2- your network driver is indicated in about half of these ( Rt64win7.sys) I would re-install with the newest available version

3-memory some driver is causing memory exceptions in most of these you should run memtest just to make sure it is a driver and not the memory itself.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

4-Once you fix the above we can try and find the actual problem causing them which appears to be 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. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try

Thanks


Ken

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\020311-15865-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e4fe90
Debug session time: Thu Feb  3 02:12:28.349 2011 (GMT-5)
System Uptime: 0 days 0:20:06.245
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8800a2f1f40, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+11af7 )

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

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800a2f1f40, 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: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+6604952f0354dcb4
fffff880`0a2f1f40 682e2f0a80      push    0FFFFFFFF800A2F2Eh

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebb0e8
 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff8800a2f2e68 -- (.exr 0xfffff8800a2f2e68)
ExceptionAddress: fffff88001729be3 (tcpip!IpFlcReceivePackets+0x0000000000000233)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800a2f2f10 -- (.trap 0xfffff8800a2f2f10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000028 rbx=0000000000000000 rcx=fffffa8008809590
rdx=ffff0080088448e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001729be3 rsp=fffff8800a2f30a0 rbp=fffffa8007a3d000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=fffffa8008809460 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
tcpip!IpFlcReceivePackets+0x233:
fffff880`01729be3 48ff02          inc     qword ptr [rdx] ds:ffff0080`088448e0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d1276b to fffff80002c8a640

STACK_TEXT:  
fffff880`0a2f1e88 fffff800`02d1276b : 00000000`0000001e ffffffff`c0000005 fffff880`0a2f1f40 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a2f1e90 fffff800`02cde5bc : 00000000`00000000 fffff880`01471624 00000000`00000000 fffffa80`08888010 : nt!KipFatalFilter+0x1b
fffff880`0a2f1ed0 fffff800`02cb64ec : fffffa80`07524a10 fffff880`043bd199 fffffa80`087b6dc0 fffffa80`07f981a0 : nt! ?? ::FNODOBFM::`string'+0x83d
fffff880`0a2f1f10 fffff800`02cb5f6d : fffff800`02dc9d00 fffff880`0a2f33d0 00000000`00000000 fffff800`02c0a000 : nt!_C_specific_handler+0x8c
fffff880`0a2f1f80 fffff800`02cb4d45 : fffff800`02dc9d00 fffff880`0a2f1ff8 fffff880`0a2f2e68 fffff800`02c0a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0a2f1fb0 fffff800`02cc5dc1 : fffff880`0a2f2e68 fffff880`0a2f26c0 fffff880`00000000 00000000`08840b01 : nt!RtlDispatchException+0x415
fffff880`0a2f2690 fffff800`02c89cc2 : fffff880`0a2f2e68 fffff880`018419a0 fffff880`0a2f2f10 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`0a2f2d30 fffff800`02c885ca : fffffa80`07a3d000 fffff880`0172ccaa 00000000`00000000 fffff880`018419a0 : nt!KiExceptionDispatch+0xc2
fffff880`0a2f2f10 fffff880`01729be3 : 00000000`00000001 fffffa80`07a3d000 fffff880`018419a0 00000000`08840b01 : nt!KiGeneralProtectionFault+0x10a
fffff880`0a2f30a0 fffff880`017295f2 : fffffa80`08841970 00000000`00000000 fffffa80`08840b01 00000000`00000001 : tcpip!IpFlcReceivePackets+0x233
fffff880`0a2f32a0 fffff880`01728a8a : fffffa80`08840ba0 fffff880`0a2f33d0 fffffa80`08840ba0 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`0a2f3380 fffff800`02c97078 : fffffa80`08809460 00000000`00004800 fffffa80`07adfb60 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`0a2f33d0 fffff880`01729152 : fffff880`017289b0 00000000`00000410 00000000`30363802 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`0a2f34b0 fffff880`0152e0eb : fffffa80`08842010 00000000`00000000 fffffa80`07f981a0 fffffa80`07f981a0 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`0a2f3520 fffff880`014f7ad6 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`0a2f3590 fffff880`01470cc1 : fffffa80`07f981a0 00000000`00000002 00000000`00000001 fffff880`13055000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`0a2f3a10 fffff880`1304faf7 : fffffa80`08780000 00000000`00000000 fffff880`05290a70 00000000`00000001 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff880`0a2f3a60 fffffa80`08780000 : 00000000`00000000 fffff880`05290a70 00000000`00000001 00000000`00000001 : Rt64win7+0x11af7
fffff880`0a2f3a68 00000000`00000000 : fffff880`05290a70 00000000`00000001 00000000`00000001 00000000`00000000 : 0xfffffa80`08780000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+11af7
fffff880`1304faf7 ??              ???

SYMBOL_STACK_INDEX:  11

SYMBOL_NAME:  Rt64win7+11af7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49a65b0d

FAILURE_BUCKET_ID:  X64_0x1E_Rt64win7+11af7

BUCKET_ID:  X64_0x1E_Rt64win7+11af7

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

Thanks for the reply. That would make sense. What doesn't make sense is that I installed the GPU drivers directly from the manufacturer-provided disc. Seems like a crap move to include 6 year old drivers for a new product. Downloading newer Win 7 x64 driver now. I'll have to see what I can find for my network card...it's a Zonet dual band B/N card, but if the graphics card drivers on the disc can be 6 years old, maybe the network card is way out of date as well.

I noticed the 0x124 error as well but hadn't given it much thought. I'll have to check the link for possible solutions. One thing that gives me pause is that these drives are linked via on of those front loading "easy swap" (not true hot swap since you have to turn the PC off to swap) setups. There's a little red LED on for the bay where my older SATA II drive is, but not for the SSD or the SATA III drive. I can't find much info, but most people say it's a "device ready" indicator...but then why wouldn't it be on for the other 2 drives? Wish this case came with a decent manual.