Some different BSOD's can't fix any of them

dimyke · 20 Oct 2010

I searched a lot on the internet and my conclusion for each bsod is that the problem can be a lot of different things..
So i don't know what's wrong with my system.
Now i found this forum and i'll give it a try to post my problem (:.

Well i built me own pc and i have some bsod's. It's my 4th own-built pc and the 3earlier worked awesome. 2 32 bits and 2 64 bits.
My system is a 64 bit
my OS is a downloaded home premium win 7 version from msdn (site/organisation for school stuff/programs i need)
so yeah kinda retail version?
I built this pc recently (september)

I tried a couple of things allready, like i have 4 memory slots for my RAM and i have 3x 2gb (all the same from ocz). So i checked the slots (all ok)
Ran some stress tests for my cpu (these were OK i thought 60° max and idle 41)
But didn't ran any tests on my video card.

all help is verry welcome and appreciated
Dimitri

zigzag3143 · 20 Oct 2010

dimyke said:

I searched a lot on the internet and my conclusion for each bsod is that the problem can be a lot of different things..
So i don't know what's wrong with my system.
Now i found this forum and i'll give it a try to post my problem (:.

Well i built me own pc and i have some bsod's. It's my 4th own-built pc and the 3earlier worked awesome. 2 32 bits and 2 64 bits.
My system is a 64 bit
my OS is a downloaded home premium win 7 version from msdn (site/organisation for school stuff/programs i need)
so yeah kinda retail version?
I built this pc recently (september)

I tried a couple of things allready, like i have 4 memory slots for my RAM and i have 3x 2gb (all the same from ocz). So i checked the slots (all ok)
Ran some stress tests for my cpu (these were OK i thought 60° max and idle 41)
But didn't ran any tests on my video card.

all help is verry welcome and appreciated
Dimitri

There are several causes all pointing to hardware. One sure problem is the Rt64win7.sys Realtek Ethernet driver.. I would update it and all the other dirvers listed below (especially the Teamviewer VPN)

Code:

PA707UCM.SYS        fffff880`0288d000    fffff880`02927000    0x0009a000    0x45513a06    11/7/2006 21:59:34  Cammaestro 2+years old                      
Alpham264.sys        fffff880`02970000    fffff880`02975500    0x00005500    0x45ffae87    3/20/2007 05:51:03                        
Alpham164.sys        fffff880`02963000    fffff880`0296ff00    0x0000cf00    0x46a45f4f    7/23/2007 03:57:03                        
teamviewervpn.sys        fffff880`03eac000    fffff880`03eb9000    0x0000d000    0x4760f9c1    12/13/2007 05:22:09                        
seehcri.sys        fffff880`01000000    fffff880`0100c000    0x0000c000    0x478488bf    1/9/2008 04:41:35                        
spldr.sys        fffff880`015e4000    fffff880`015ec000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
lirsgt.sys        fffff880`073d1000    fffff880`073de000    0x0000d000    0x4a100bf1    5/17/2009 09:06:57                        
atksgt.sys        fffff880`07379000    fffff880`073c8000    0x0004f000    0x4a1012e2    5/17/2009 09:36:34                        
GEARAspiWDM.sys        fffff880`040c5000    fffff880`040d2000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`00ea4000    fffff880`00eaf000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
Tpkd.sys        fffff880`013d9000    fffff880`013fc000    0x00023000    0x4a15c952    5/21/2009 17:36:18                        
PxHlpa64.sys        fffff880`01070000    fffff880`0107be00    0x0000be00    0x4a416253    6/23/2009 19:16:35

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\091810-31168-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a13000 PsLoadedModuleList = 0xfffff800`02c50e50
Debug session time: Sat Sep 18 11:00:00.056 2010 (GMT-4)
System Uptime: 0 days 0:20:26.461
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880041b8180, fffff8800a752ea0, 0}

Probably caused by : Rt64win7.sys ( Rt64win7+e180 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880041b8180, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800a752ea0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
Rt64win7+e180
fffff880`041b8180 0803            or      byte ptr [rbx],al

CONTEXT:  fffff8800a752ea0 -- (.cxr 0xfffff8800a752ea0)
rax=0000000000aad235 rbx=0000000000000000 rcx=00000000003f87ff
rdx=0000035c00000000 rsi=fffff8800a754100 rdi=fffffa8006f74000
rip=fffff880041b8180 rsp=fffff8800a753880 rbp=0000000000000000
 r8=0000000000000200  r9=0000000000000000 r10=0000000000000000
r11=000000000002020a r12=fffffa8007d46f00 r13=fffff8800a754100
r14=0000000000000098 r15=0000000000000098
iopl=0         nv up ei pl nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010216
Rt64win7+0xe180:
fffff880`041b8180 0803            or      byte ptr [rbx],al ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  vmware-hostd.e

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880041b8180

STACK_TEXT:  
fffff880`0a753880 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Rt64win7+0xe180


FOLLOWUP_IP: 
Rt64win7+e180
fffff880`041b8180 0803            or      byte ptr [rbx],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Rt64win7+e180

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a8d7432

STACK_COMMAND:  .cxr 0xfffff8800a752ea0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_Rt64win7+e180

BUCKET_ID:  X64_0x3B_Rt64win7+e180

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880041b8180, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800a752ea0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
Rt64win7+e180
fffff880`041b8180 0803            or      byte ptr [rbx],al

CONTEXT:  fffff8800a752ea0 -- (.cxr 0xfffff8800a752ea0)
rax=0000000000aad235 rbx=0000000000000000 rcx=00000000003f87ff
rdx=0000035c00000000 rsi=fffff8800a754100 rdi=fffffa8006f74000
rip=fffff880041b8180 rsp=fffff8800a753880 rbp=0000000000000000
 r8=0000000000000200  r9=0000000000000000 r10=0000000000000000
r11=000000000002020a r12=fffffa8007d46f00 r13=fffff8800a754100
r14=0000000000000098 r15=0000000000000098
iopl=0         nv up ei pl nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010216
Rt64win7+0xe180:
fffff880`041b8180 0803            or      byte ptr [rbx],al ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  vmware-hostd.e

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880041b8180

STACK_TEXT:  
fffff880`0a753880 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Rt64win7+0xe180


FOLLOWUP_IP: 
Rt64win7+e180
fffff880`041b8180 0803            or      byte ptr [rbx],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Rt64win7+e180

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a8d7432

STACK_COMMAND:  .cxr 0xfffff8800a752ea0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_Rt64win7+e180

BUCKET_ID:  X64_0x3B_Rt64win7+e180

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

dimyke · 20 Oct 2010

Hey,
thanks for your answer
but you're saying that the crashes point to my hardware? Can you be more specific?
I'm also updating these drivers although i don't get where that teamviewer comes from? It's an program that i've installed what does that has to do with drivers? Certainly when i even don't use it at the time of any of my bsod's.
And how do i update those others things? Like PA707UCM.sys or Alpham264.sys?

I'm getting a bit confused with all the info that i'm getting from different sites and so. ):
and thank you for your quick reply ^^

zigzag3143 · 20 Oct 2010

dimyke said:

Hey,
thanks for your answer
but you're saying that the crashes point to my hardware? Can you be more specific?
I'm also updating these drivers although i don't get where that teamviewer comes from? It's an program that i've installed what does that has to do with drivers? Certainly when i even don't use it at the time of any of my bsod's.
And how do i update those others things? Like PA707UCM.sys or Alpham264.sys?

I'm getting a bit confused with all the info that i'm getting from different sites and so. ):
and thank you for your quick reply ^^

1-hardware. to be more specific we have to eliminate the things that we see now. Then we can isolate the specific piece of hardware.

2-Teamviewer is loaded wether you are using it or not, and yours is 2+years old. They do have a much newer client (im using it). You also have logmein from 2+years ago loaded

3-Updating drivers
How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

dimyke · 21 Oct 2010

hey,
thanks again, updated all drivers
(altough some were up to date, => manufacturers aren't updating them anymore :/)
What do I do now? Wait till new bsod's appear or be lucky and problem solved?

Thanks for all your help allready ^^

Dimitri

CarlTR6 · 21 Oct 2010

To support what Ken has said, out of date drivers can and do cause conflicts, memory corruption, and BSOD's.

PxHlpa64.sys 6/23/2009 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs
Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.

GEARAspiWDM.sys 5/18/2009 - I don't believe there is an update for this driver. It may work OK. You can ignore this one for now.

Tpkd.sys 5/21/2009 - InterLok system file belongs to the software InterLok(R) or InterLok Driver Kit or TPkd or Sonic RecordNow! or Adobe eBook Migration Utility or Interlok driver setup x or nGenius InfiniStream by PACE Anti-Piracy, Inc (www.paceap.com). If there is no update for this driver, I suggest you uninstall the software and upgrade to software that is certified compatible with Win 7.

amdxata.sys - there is no update for this driver. It should be OK.

atksgt.sys 5/17/2009 - part of a Copy Protection platform dveloped by Tages SA, TAGES, the AAA Copy Protection System. If there is no update for this driver, uninstall the software.

lirsgt.sys 5/17/2009 - part of a Copy Protection platform developed by Tages SA TAGES, the AAA Copy Protection System. See above.

spldr.sys - This is an MS system driver. It is fine. Ignore it.

seehcri.sys 1/9/2008 - Sony Ericsson Device 0016 (likely a phone) Sony Ericsson - Support - Softwaredownloads. This software/device is way obsolete. Update or uninstall.

Alpham164.sys 7/23/2007 - Ideazon ZBoard http://www.steelseries.com/download. This an XP driver, way obsolete. It is not compatible with Win 7. If you cannot update the driver or the software, uninstall.

Win 7 is an entirely different OS from XP and even different from Vista. Software and hardware designed and programmed for XP are not going to run on Win 7, except in the XP mode. That said, some Vista drivers do work with Win 7. Third party (non MS) drivers dated prior to 13 July 2009 are out of date. Some of the drivers with dates in 2009 will work; these are Vista drivers.

dimyke · 21 Oct 2010

CarlTR6 said:

To support what Ken has said, out of date drivers can and do cause conflicts, memory corruption, and BSOD's.

PxHlpa64.sys 6/23/2009 - Sonic CD/DVD driver (used by many different CD/DVD programs) pxHelp20.sys programs
Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.

GEARAspiWDM.sys 5/18/2009 - I don't believe there is an update for this driver. It may work OK. You can ignore this one for now.

Tpkd.sys 5/21/2009 - InterLok system file belongs to the software InterLok(R) or InterLok Driver Kit or TPkd or Sonic RecordNow! or Adobe eBook Migration Utility or Interlok driver setup x or nGenius InfiniStream by PACE Anti-Piracy, Inc (www.paceap.com). If there is no update for this driver, I suggest you uninstall the software and upgrade to software that is certified compatible with Win 7.

amdxata.sys - there is no update for this driver. It should be OK.

atksgt.sys 5/17/2009 - part of a Copy Protection platform dveloped by Tages SA, TAGES, the AAA Copy Protection System. If there is no update for this driver, uninstall the software.

lirsgt.sys 5/17/2009 - part of a Copy Protection platform developed by Tages SA TAGES, the AAA Copy Protection System. See above.

spldr.sys - This is an MS system driver. It is fine. Ignore it.

seehcri.sys 1/9/2008 - Sony Ericsson Device 0016 (likely a phone) Sony Ericsson - Support - Softwaredownloads. This software/device is way obsolete. Update or uninstall.

Alpham164.sys 7/23/2007 - Ideazon ZBoard http://www.steelseries.com/download. This an XP driver, way obsolete. It is not compatible with Win 7. If you cannot update the driver or the software, uninstall.

Win 7 is an entirely different OS from XP and even different from Vista. Software and hardware designed and programmed for XP are not going to run on Win 7, except in the XP mode. That said, some Vista drivers do work with Win 7. Third party (non MS) drivers dated prior to 13 July 2009 are out of date. Some of the drivers with dates in 2009 will work; these are Vista drivers.

Hey,
thank you verry much for this answer. That's what i kinda asked in my earlier replies.
But i worked on it and spent a few hours googling what they ment.
When I installed this drivers a month or 2 ago there weren't any win7 drivers for them.
But now i found all win7 drivers.
And cheers on the LG cd/dvd driver, didn't found a solution for that one .
So now everything's updated the chance of a bsod should be smaller?

Thanks again
Dimitri

CarlTR6 · 31 Oct 2010

Updating these drivers should definitely improve your system's stability. Have you had any more BSOD'S?

dimyke · 08 Nov 2010

Hey Carl,
Yes i did had one more bsod since i tried to update all my drivers.
Idk what it said because i was gone when it appeared.
But part from that one bsod none. So that's quit an improvement i think.

Dimitri

CarlTR6 · 09 Nov 2010

Dimitri, that is good news. I am glad that things are better, much better. Can you upload that latest BSOD to us? Did you rename that PxHlpa64.sys driver?