BSODs - Various BS on Win7 64-bit

EmZon · 25 Sep 2010

Hello, (warning: Bad grammar may accure)

I have had some various Bluescreens lately. They are sometimes the same, but may change to another code (BScode i.e. 0x1a) all of a sudden. I have been googling for answers, most of the answers don`t do any good for me. Therefore I ask you, as I have done a previous time with another problem.

General info:

Specs: (info from CPU-Z)
Os: Windows 7 32-bit
MB: XFX MI-9300-7AS9 Nvidia nForce 730i (Gefore 9300)
RAM: 2x DDR2 PC2-6400 (400MHz)
Graph: Radeon HD 5770 1024 MB PCI-E
Bios: American Megatrends V1.0B25 (date: 11/04/2008)

New hardware/programs?
I have not installed any new hardware. The only hardware that is relatively new, is my RAM that I installed in May. I have not had any problems until the last two weeks.
I have a new program installed, Norton 360 AntiVirus. I don`t know if this program has anything to do with it, as I am not an expert.

Memtest? Overclocking? Hot pc?
I have been running MemTest for an hour -+, no errors have yet been displayed.
OCing, I have been testing out some settings, but not over the limit due to that I am not an expert and will not harm my computer since I love it. Only the CPU has been overclocked, only 0.3GHz, but has been set back to normal now.
My computer is relatively cool, CPU 35 Celsuis -+, Graphic Card 38-+. 3 big fans in my case lets the air flow quite well.

Bluescreens appear, when?
The bluescreens appears randomly. One day I can start the computer and play/watch movies/listen to music without anything happening, it can even run for days (not turning it off) withour crashing.
When the bluescreens first appear, they ALL appear, one after the other.

BSODs may stop,when..
..I switch my two ram sticks (2GBx2) with the other slots. The solution is not permanent, the BS may appear even though this is performed.

Answers will be appreciated

Emil / EmZon - Norway

zigzag3143 · 25 Sep 2010

EmZon said:

Hello, (warning: Bad grammar may accure)

I have had some various Bluescreens lately. They are sometimes the same, but may change to another code (BScode i.e. 0x1a) all of a sudden. I have been googling for answers, most of the answers don`t do any good for me. Therefore I ask you, as I have done a previous time with another problem.

General info:

Specs: (info from CPU-Z)
Os: Windows 7 32-bit
MB: XFX MI-9300-7AS9 Nvidia nForce 730i (Gefore 9300)
RAM: 2x DDR2 PC2-6400 (400MHz)
Graph: Radeon HD 5770 1024 MB PCI-E
Bios: American Megatrends V1.0B25 (date: 11/04/2008)

New hardware/programs?
I have not installed any new hardware. The only hardware that is relatively new, is my RAM that I installed in May. I have not had any problems until the last two weeks.
I have a new program installed, Norton 360 AntiVirus. I don`t know if this program has anything to do with it, as I am not an expert.

Memtest? Overclocking? Hot pc?
I have been running MemTest for an hour -+, no errors have yet been displayed.
OCing, I have been testing out some settings, but not over the limit due to that I am not an expert and will not harm my computer since I love it. Only the CPU has been overclocked, only 0.3GHz, but has been set back to normal now.
My computer is relatively cool, CPU 35 Celsuis -+, Graphic Card 38-+. 3 big fans in my case lets the air flow quite well.

Bluescreens appear, when?
The bluescreens appears randomly. One day I can start the computer and play/watch movies/listen to music without anything happening, it can even run for days (not turning it off) withour crashing.
When the bluescreens first appear, they ALL appear, one after the other.

BSODs may stop,when..
..I switch my two ram sticks (2GBx2) with the other slots. The solution is not permanent, the BS may appear even though this is performed.

Answers will be appreciated

Emil / EmZon - Norway

Hi Emil and welcome

Two of 4 crashes were directly caused by your Norton intrusion detection (IDSvai64.sys). Symantec has a history of causing BSOD's

I would remove all traces of the Norton product using their un-install tool, and replace them with Microsoft Security Essentials

I would also run a system file check to verify and repair your system files.

Let us know the results at the end

Ken J

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\092610-23421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03413000 PsLoadedModuleList = 0xfffff800`03650e50
Debug session time: Sat Sep 25 20:50:14.187 2010 (GMT-4)
System Uptime: 0 days 0:00:38.312
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800d764585, 2, 1, fffff88003c4abf4}

Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\Norton\Definitions\ipsdefs\20100924.001\IDSvia64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
Probably caused by : IDSvia64.sys ( IDSvia64+2dbf4 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8800d764585, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88003c4abf4, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036bb0e0
 fffff8800d764585 

CURRENT_IRQL:  2

FAULTING_IP: 
IDSvia64+2dbf4
fffff880`03c4abf4 c8dbfdff        enter   0FDDBh,0FFh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff8800d7742d0 -- (.trap 0xfffff8800d7742d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005122078
rdx=0000000000000011 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003c4abf4 rsp=fffff8800d774460 rbp=fffffa8005e06098
 r8=fffff8800d774528  r9=fffff8800d774520 r10=0000000000000000
r11=fffff8800d774450 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
IDSvia64+0x2dbf4:
fffff880`03c4abf4 c8dbfdff        enter   0FDDBh,0FFh
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003482ca9 to fffff80003483740

STACK_TEXT:  
fffff880`0d774188 fffff800`03482ca9 : 00000000`0000000a fffff880`0d764585 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0d774190 fffff800`03481920 : 00000000`00000000 fffff880`0d774520 fffffa80`06b62450 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0d7742d0 fffff880`03c4abf4 : fffffa80`077b0a98 fffff880`0d774610 fffffa80`06d03c68 fffff880`0d774528 : nt!KiPageFault+0x260
fffff880`0d774460 fffffa80`077b0a98 : fffff880`0d774610 fffffa80`06d03c68 fffff880`0d774528 00000000`00000033 : IDSvia64+0x2dbf4
fffff880`0d774468 fffff880`0d774610 : fffffa80`06d03c68 fffff880`0d774528 00000000`00000033 fffffa80`076dfca0 : 0xfffffa80`077b0a98
fffff880`0d774470 fffffa80`06d03c68 : fffff880`0d774528 00000000`00000033 fffffa80`076dfca0 00000000`0000f5e3 : 0xfffff880`0d774610
fffff880`0d774478 fffff880`0d774528 : 00000000`00000033 fffffa80`076dfca0 00000000`0000f5e3 fffff880`0d774600 : 0xfffffa80`06d03c68
fffff880`0d774480 00000000`00000033 : fffffa80`076dfca0 00000000`0000f5e3 fffff880`0d774600 fffff880`0d774628 : 0xfffff880`0d774528
fffff880`0d774488 fffffa80`076dfca0 : 00000000`0000f5e3 fffff880`0d774600 fffff880`0d774628 fffffa80`05090068 : 0x33
fffff880`0d774490 00000000`0000f5e3 : fffff880`0d774600 fffff880`0d774628 fffffa80`05090068 fffff880`0d774610 : 0xfffffa80`076dfca0
fffff880`0d774498 fffff880`0d774600 : fffff880`0d774628 fffffa80`05090068 fffff880`0d774610 fffff880`03c20e24 : 0xf5e3
fffff880`0d7744a0 fffff880`0d774628 : fffffa80`05090068 fffff880`0d774610 fffff880`03c20e24 fffffa80`05e06098 : 0xfffff880`0d774600
fffff880`0d7744a8 fffffa80`05090068 : fffff880`0d774610 fffff880`03c20e24 fffffa80`05e06098 fffffa80`076d0011 : 0xfffff880`0d774628
fffff880`0d7744b0 fffff880`0d774610 : fffff880`03c20e24 fffffa80`05e06098 fffffa80`076d0011 fffff880`0d774528 : 0xfffffa80`05090068
fffff880`0d7744b8 fffff880`03c20e24 : fffffa80`05e06098 fffffa80`076d0011 fffff880`0d774528 fffff880`0162d3fe : 0xfffff880`0d774610
fffff880`0d7744c0 fffffa80`05e06098 : fffffa80`076d0011 fffff880`0d774528 fffff880`0162d3fe fffff880`0d774520 : IDSvia64+0x3e24
fffff880`0d7744c8 fffffa80`076d0011 : fffff880`0d774528 fffff880`0162d3fe fffff880`0d774520 fffffa80`05080018 : 0xfffffa80`05e06098
fffff880`0d7744d0 fffff880`0d774528 : fffff880`0162d3fe fffff880`0d774520 fffffa80`05080018 0602a8c0`6e14d054 : 0xfffffa80`076d0011
fffff880`0d7744d8 fffff880`0162d3fe : fffff880`0d774520 fffffa80`05080018 0602a8c0`6e14d054 fffff880`03020002 : 0xfffff880`0d774528
fffff880`0d7744e0 fffff880`0d7744f8 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!WfpAssociateContextToFlow+0x8e
fffff880`0d774530 00000000`00000001 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`0d7744f8
fffff880`0d774538 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
IDSvia64+2dbf4
fffff880`03c4abf4 c8dbfdff        enter   0FDDBh,0FFh

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  IDSvia64+2dbf4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: IDSvia64

IMAGE_NAME:  IDSvia64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bfe2836

FAILURE_BUCKET_ID:  X64_0xD1_IDSvia64+2dbf4

BUCKET_ID:  X64_0xD1_IDSvia64+2dbf4

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

CarlTR6 · 25 Sep 2010

Norton is known to cause BSOD's on some Win 7 systems. The fact that your crashes starting occurring after you installed Norton adds suspicion to Norton as the cause. Uninstall Norton using this this tool:Info > Tool. Install Microsoft Security Essentials in its place and make sure Windows Firewall is turned on.

I will take a look at your dumps and post back.

Ken was posting as I was typing. Follow Ken's advice.

EmZon · 25 Sep 2010

Thank you, Zigzag.

I remember you from the last time I posted here in may. You were the first then and you are the first now. I was just repping you from last time, as I saw there was a function to do so.

Your response are quick, wich is pretty brilliant for users that are impatient and want their answers straight up, thanks.

OT:
I have NOW uninstalled everything that has to do with Norton, and will perform a restart. Microsoft Sec. Ess. is downloaded and will be installed right away after the reboot.

Q: How do I perform the system file check?

EDIT:

As I search for my question, I found the answer: cmd > sfc /scannow

Another problem came up. It says that I have to be a system(manager(?) to run the SFC tool. I am the only user of this computer, and I have only created one account wich is an administrator.
Q: Shouldn`t I be able to use this SFC tool?

CarlTR6 · 25 Sep 2010

Use an elevated command prompt. Go to Start and type in "cmd.exe" (without the quotes) At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

EmZon · 25 Sep 2010

CarlTR6 said:

Use an elevated command prompt. Go to Start and type in "cmd.exe" (without the quotes) At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

Thank you, I am performing the scan now.

Minor update:

-I have played some games now, Bad Company 2 and Civilization 5. I ran both games individually without any Bluescreens, yet.
- Norton 360 is uninstalled and out of the picture, Microsoft Security Ess. took over the antivirus control
- Performing scan now

EmZon · 25 Sep 2010

1st BlueScreen after uninstalling Norton
- I just got my first bluescreen after the uninstall of Norton 360
- The system file check was performing while the BlueScreen appeared, I don`t know if it was finished or not.

I just got a glimt of what it said in the top left corner on the BlueScreen:
Something about: win32k. "something,something"

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
ID for locale: 1044

Additional information about the problem:
BCCode: 50
BCP1: FFFFF900C60A6038
BCP2: 0000000000000000
BCP3: FFFFF9600030A92C
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

EDIT:

SFC was performed 100% now. I got a message that said that it had some damaged files that it could not repair.
There were also a CBS.log, were I could find additional information about the errors. CBS.log will be attached.

CarlTR6 · 26 Sep 2010

Error code 50, PAGE_FAULT_IN_NONPAGED_AREA -usual causes are Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

Code:

Kernel base = 0xfffff800`03449000 PsLoadedModuleList = 0xfffff800`03686e50
Debug session time: Sat Sep 25 23:32:58.583 2010 (GMT-4)
System Uptime: 0 days 1:31:37.708
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c60a6038, 0, fffff9600030a92c, 2}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!ttfdSemDestroyFont+2c )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c60a6038, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600030a92c, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036f10e0
 fffff900c60a6038 

FAULTING_IP: 
win32k!ttfdSemDestroyFont+2c
fffff960`0030a92c 488b5e08        mov     rbx,qword ptr [rsi+8]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800ad63680 -- (.trap 0xfffff8800ad63680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c201e500 rbx=0000000000000000 rcx=fffffa8005da8c60
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600030a92c rsp=fffff8800ad63810 rbp=fffff900c01dbca0
 r8=0000000000000001  r9=fffffa8006336b30 r10=0000000000000002
r11=fffff800036b9b60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
win32k!ttfdSemDestroyFont+0x2c:
fffff960`0030a92c 488b5e08        mov     rbx,qword ptr [rsi+8] ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800035388f2 to fffff800034b9740

STACK_TEXT:  
fffff880`0ad63518 fffff800`035388f2 : 00000000`00000050 fffff900`c60a6038 00000000`00000000 fffff880`0ad63680 : nt!KeBugCheckEx
fffff880`0ad63520 fffff800`034b782e : 00000000`00000000 fffff960`0030a900 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`0ad63680 fffff960`0030a92c : fffff880`0ad63930 00000000`74052450 fffffa80`00000038 fffff960`00000000 : nt!KiPageFault+0x16e
fffff880`0ad63810 fffff960`002d1cc2 : fffff960`0030a900 fffff880`0ad63930 fffff880`0ad639a0 fffff960`001441c5 : win32k!ttfdSemDestroyFont+0x2c
fffff880`0ad63840 fffff960`002cfefe : fffffa80`05da74e0 fffff880`0ad63940 fffff880`0ad639a0 fffff880`0ad63b18 : win32k!PDEVOBJ::DestroyFont+0xf2
fffff880`0ad638b0 fffff960`000f7af3 : fffffa80`05da74e0 fffff900`c01dbca0 fffff900`c008a010 fffff960`000fb474 : win32k!RFONTOBJ::vDeleteRFONT+0x4a
fffff880`0ad63920 fffff960`000f7523 : fffff900`c01dbca0 fffff880`0ad639c0 fffff900`c01dbca0 00000000`00000000 : win32k!RFONTOBJ::bMakeInactiveHelper+0x427
fffff880`0ad639a0 fffff960`00145f15 : fffff880`0ad63b20 fffff880`0ad63b20 00000000`00000000 00000000`00000001 : win32k!RFONTOBJ::vMakeInactive+0xa3
fffff880`0ad63a40 fffff960`00146174 : fffff880`0ad63b20 fffff900`c2390100 00000000`00000000 fffff900`c224aca0 : win32k!XDCOBJ::bCleanDC+0x36d
fffff880`0ad63b00 fffff960`0013f11b : fffff900`c2390100 fffff900`c0581e90 00000000`74052450 00000000`001de9c0 : win32k!GreCleanDC+0x34
fffff880`0ad63b40 fffff960`0013f003 : 00000000`28010af8 fffff880`0ad63c60 fffff960`00153d6c 00000000`00000000 : win32k!ReleaseCacheDC+0xfb
fffff880`0ad63b80 fffff960`00153dba : 00000000`001dfd20 00000000`7407ab7c 00000000`00000006 fffff960`00153d6c : win32k!ReleaseDC+0xb
fffff880`0ad63bb0 fffff800`034b8993 : 00000000`00000002 00000000`0014d9c8 00000000`00000020 00000000`00000000 : win32k!NtUserCallOneParam+0x4e
fffff880`0ad63be0 00000000`7409fbea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001de058 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7409fbea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!ttfdSemDestroyFont+2c
fffff960`0030a92c 488b5e08        mov     rbx,qword ptr [rsi+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k!ttfdSemDestroyFont+2c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c483f

FAILURE_BUCKET_ID:  X64_0x50_win32k!ttfdSemDestroyFont+2c

BUCKET_ID:  X64_0x50_win32k!ttfdSemDestroyFont+2c

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

You still have a couple of drivers that need updating:

nvsmu.sys Mon Jun 29 03:36:37 2009 - nVidia nForce System Management Controller (nVidia nForce chipset driver) Drivers - Download NVIDIA Drivers. See if you can update this chipset driver.

Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver, Realtek. Update this network driver.

Looking at your dump file, I see evidence that Catalyst Control Center drivers were involved in the crash. If updating the above drivers does not work, you can try updating to the latest version or remove the Catalyst Control Center and only install the Display Driver, Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

It bothers me that SFC reported some files that could not be repaired. After you update these drivers, run SFC again. If you get that same message, it may be time for a repair install: Repair Install

EmZon · 26 Sep 2010

Looking at your dump file, I see evidence that Catalyst Control Center drivers were involved in the crash. If updating the above drivers does not work, you can try updating to the latest version or remove the Catalyst Control Center and only install the Display Driver, Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

It bothers me that SFC reported some files that could not be repaired. After you update these drivers, run SFC again. If you get that same message, it may be time for a repair install: Repair Install

Thanks.

Thoughts
I had my thoughts too, with the defective hardware, but I don`t understand that it may be possible for my RAM to be damaged in such a short time since it was purchased and installed.

Chkdsk & repair, sfc/ scannow
- I did the CHKDSK which i chose to perform after reboot. (before windows start up, it performs file check) It took a long time, and I fell asleep. When I woke up, there were not any errors, maybe it had repaired it, but no.
- I did another sfc / scannow and the result were the same as I provided in the previous post; File damaged, but could not repair.

Driver updates
- Newest Radeon CCC drivers are installed, (all installed, not only the display driver)
- Newest nVidia driver installed (I found only one for my GeForce 9300 MotherB.)

Version:
15.49 WHQL
Release Date:
2009.10.01
Operating System:
Windows Vista 64-bit, Windows 7 64-bit
Language:
English (U.S.)
File Size:
210 MB

- I can`t seem to find the driver for the Realtek

Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver, Realtek. Update this network driver.

CarlTR6 · 26 Sep 2010

EmZon said:

Thanks.

Thoughts
I had my thoughts too, with the defective hardware, but I don`t understand that it may be possible for my RAM to be damaged in such a short time since it was purchased and installed.

RAM can be defective right out of the box.

Chkdsk & repair, sfc/ scannow
- I did the CHKDSK which i chose to perform after reboot. (before windows start up, it performs file check) It took a long time, and I fell asleep. When I woke up, there were not any errors, maybe it had repaired it, but no.
- I did another sfc / scannow and the result were the same as I provided in the previous post; File damaged, but could not repair.

Follow this article and run Startup Repair Startup Repair and make sure you run it at least 3 or 4 times.

Driver updates
- Newest Radeon CCC drivers are installed, (all installed, not only the display driver)
- Newest nVidia driver installed (I found only one for my GeForce 9300 MotherB.)

Version:
15.49 WHQL
Release Date:
2009.10.01
Operating System:
Windows Vista 64-bit, Windows 7 64-bit
Language:
English (U.S.)
File Size:
210 MB

- I can`t seem to find the driver for the Realtek

Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver, Realtek. Update this network driver.

I cannot determine whether this driver is a software, a utility program, or an actual hardware driver It looks like it may be part of a diagnostic utility. Here is a link I found that has both software and a Win 7 driver: Realtek

You can try several things here; but first, create a restore point or a system image or both.

1. You can navigate to C:\Windows\System32\Drivers, find Rt64win7.sys and rename it from .sys to .bak. Reboot. This will break whatever software/hardware this driver is associated with; but it will not load. If it disables your network adapter, simply rename it again to .sys. You also have a restore point to fall back on.

2. If it breaks a utility program, you can try to update the utility program from the link above and see if you get an updated driver.

3. You can download just the Win 7 driver from the link above and install it. If the download does not include an .exe file, you can navigate back to the Drivers folder, rename the driver to back and copy the new driver from your desktop to the Driver folder. Reboot.