BSOD

thewalrii · 07 Jun 2010

Earlier this year, I had to replace my motherboard because the onboard sound stopped working. I replaced it with the same model, and reinstalled Windows 7. Since then, I've been having issues with the computer. I have been getting BSOD errors frequently, especially when playing games. I've been trying to get help from techsupportforum.com, but I thought there might be other experts here that could help me, so I decided to ask for help here.

After trying to fix the problems for a while with no success, I reformatted my hard drive and reinstalled Windows 7 last week. It worked fine for about a day, then crashed. After that, it worked fine for almost a week, until it crashed again last night. The dump files are attached.

I am running BIOS version 2001, and the only settings I have changed are to turn off the eSATA controller and to set the RAM voltage to the manufacturer's specification.

Any help would be greatly appreciated.

richc46 · 07 Jun 2010

Based upon your dump reports the BSOD was caused by a realtek NIC Driver. You should replace the driver and check for any other outdated drivers that may have contributed or will cause problems in the future.

you MAY be able to obtain a new driver from this source
http://www.realtek.com/downloads/dow...Level=3&Conn=2

Let us know the results.

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

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp4_Minidump[1].zip\060610-22370-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae50
Debug session time: Sun Jun 6 23:01:12.687 2010 (GMT-4)
System Uptime: 0 days 0:29:37.218
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff2800550d537, 2, 0, fffff88003f782e0}
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+122e0 )
Followup: MachineOwner
---------
0: 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: fffff2800550d537, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003f782e0, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc50e0
fffff2800550d537
CURRENT_IRQL: 2
FAULTING_IP:
Rt64win7+122e0
fffff880`03f782e0 44385667 cmp byte ptr [rsi+67h],r10b
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88009226960 -- (.trap 0xfffff88009226960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8005524990
rdx=fffffa800550d4d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003f782e0 rsp=fffff88009226af0 rbp=0000000000000501
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=0000000000000080 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
Rt64win7+0x122e0:
fffff880`03f782e0 44385667 cmp byte ptr [rsi+67h],r10b ds:00000000`00000067=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a8cb69 to fffff80002a8d600
STACK_TEXT:
fffff880`09226818 fffff800`02a8cb69 : 00000000`0000000a fffff280`0550d537 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09226820 fffff800`02a8b7e0 : fffffa80`05861960 00000000`00000000 00000000`00000001 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`09226960 fffff880`03f782e0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`03f6a7b4 : nt!KiPageFault+0x260
fffff880`09226af0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`03f6a7b4 fffff880`03f6a7b4 : Rt64win7+0x122e0

STACK_COMMAND: kb
FOLLOWUP_IP:
Rt64win7+122e0
fffff880`03f782e0 44385667 cmp byte ptr [rsi+67h],r10b
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: Rt64win7+122e0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rt64win7
IMAGE_NAME: Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a16bc2e
FAILURE_BUCKET_ID: X64_0xD1_Rt64win7+122e0
BUCKET_ID: X64_0xD1_Rt64win7+122e0
Followup: MachineOwner
---------

CarlTR6 · 07 Jun 2010

Both dumps report the same error, D1

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Usual causes: Device driver

BSOD Index

Opps, Richard posted while I was typing.

thewalrii · 07 Jun 2010

So that means it is probably caused by rt64win7.sys, which is the Realtec driver, correct? I'll see if updating that fixes the issue.

richc46 · 07 Jun 2010

To the best of my knowledge, yes.

thewalrii · 07 Jun 2010

I updated the Realtek drivers by having windows automatically find them from the device manager. After this, the computer has crashed two times. After the second crash, it took me 3 tries to successfully boot to windows. For some reason, only two dump files were created from all of these crashes.

richc46 · 07 Jun 2010

Try getting it from the website. If you still have problems I will check the new dumps tomorrow morning, unless someone beats me to it.

Jonathan_King · 07 Jun 2010

I suspect the cause is ASACPI.sys. See this excellent post by usasma: More BSOD - Windows 7 7600 - Tech Support Forum

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005

thewalrii · 07 Jun 2010

Should I download the AiSuite he linked to in that post? Asus does support Windows 7 for my motherboard, so should I get the AiSuite for my motherboard instead?

Jonathan_King · 07 Jun 2010

Yes, that's best.