BSOD's since computer was built

[btc138]

Onboard I believe, I apologize for being a noob to computers.
Just to make sure the NIC I dl'ed last night I went to Realtek website-> Went to NIC -> 10/100/1000M Gigabit Internet -> PCI Express.

Did I install the correct driver? Because I was a little bit confused.

Download driver from here http://www.msi.com/product/mb/P67A-GD65--B3-.html#/?div=Driver&os=Win7 32
This is ur motherboard website.

Will do will let you know results.

I uninstalled the old driver, and used CCleaner to make sure everything was gone, then downloaded the driver from the site you specified. I got a BlueScreen after install, then the computer ran fine for about an hour and a half, then another BlueScreen.

Have no clue what is going on...

 

[btc138]

Experienced two more BSODs. They are def becoming more frequent now. Whenever I first got the system, they would occur weekly or like every 10 days. Now basically every time I turn on my computer, I know I am going to get one.

I just want to finally solve this.

 

[panais]

Experienced two more BSODs. They are def becoming more frequent now. Whenever I first got the system, they would occur weekly or like every 10 days. Now basically every time I turn on my computer, I know I am going to get one.

I just want to finally solve this.

Please upload the new minidump.

 

[btc138]

Here are the latest dumps, experienced another today...

 

[panais]

Here are the latest dumps, experienced another today...

THe same Rt64win7.sys error.
Try with MSI Global - Live Update Online
Update chipset,bios,drivers,everything.

 

[yowanvista]

Same issue, the Realtek driver
Uninstall current version and download the generic version
Realtek

Here is the direct link Realtek

As a last solution RMA the board, the Realtek LAN 10/100/1000 8111E is on-board. It may have defects

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800638e000, 2, 0, fffff8800f261ce6}

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+61ce6 )

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

4: 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: fffff8800638e000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800f261ce6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bc100
 fffff8800638e000 

CURRENT_IRQL:  2

FAULTING_IP: 
Rt64win7+61ce6
fffff880`0f261ce6 410fb609        movzx   ecx,byte ptr [r9]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800b885540 -- (.trap 0xfffff8800b885540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000007ae13f4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f261ce6 rsp=fffff8800b8856d8 rbp=00000000000009b7
 r8=000000000000136f  r9=fffff8800638e000 r10=0000000000000000
r11=fffff88006388fda r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
Rt64win7+0x61ce6:
fffff880`0f261ce6 410fb609        movzx   ecx,byte ptr [r9] ds:fffff880`0638e000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000308c2a9 to fffff8000308cd00

STACK_TEXT:  
fffff880`0b8853f8 fffff800`0308c2a9 : 00000000`0000000a fffff880`0638e000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b885400 fffff800`0308af20 : fffff880`009b3180 fffff800`03098fb8 fffff880`009b3180 00000000`0000f2a3 : nt!KiBugCheckDispatch+0x69
fffff880`0b885540 fffff880`0f261ce6 : 00000000`00000000 00000000`0000352d 00000000`000002af fffff880`06388fc0 : nt!KiPageFault+0x260
fffff880`0b8856d8 00000000`00000000 : 00000000`0000352d 00000000`000002af fffff880`06388fc0 00000000`00000008 : Rt64win7+0x61ce6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+61ce6
fffff880`0f261ce6 410fb609        movzx   ecx,byte ptr [r9]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Rt64win7+61ce6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8750a0

FAILURE_BUCKET_ID:  X64_0xD1_Rt64win7+61ce6

BUCKET_ID:  X64_0xD1_Rt64win7+61ce6

Followup: MachineOwner

 

[panais]

Same issue, the Realtek driver
Uninstall current version and download the generic version
Realtek

Here is the direct link Realtek

As a last solution RMA the board, the Realtek LAN 10/100/1000 8111E is on-board. It may have defects

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800638e000, 2, 0, fffff8800f261ce6}

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+61ce6 )

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

4: 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: fffff8800638e000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800f261ce6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bc100
 fffff8800638e000 

CURRENT_IRQL:  2

FAULTING_IP: 
Rt64win7+61ce6
fffff880`0f261ce6 410fb609        movzx   ecx,byte ptr [r9]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800b885540 -- (.trap 0xfffff8800b885540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000007ae13f4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f261ce6 rsp=fffff8800b8856d8 rbp=00000000000009b7
 r8=000000000000136f  r9=fffff8800638e000 r10=0000000000000000
r11=fffff88006388fda r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
Rt64win7+0x61ce6:
fffff880`0f261ce6 410fb609        movzx   ecx,byte ptr [r9] ds:fffff880`0638e000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000308c2a9 to fffff8000308cd00

STACK_TEXT:  
fffff880`0b8853f8 fffff800`0308c2a9 : 00000000`0000000a fffff880`0638e000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b885400 fffff800`0308af20 : fffff880`009b3180 fffff800`03098fb8 fffff880`009b3180 00000000`0000f2a3 : nt!KiBugCheckDispatch+0x69
fffff880`0b885540 fffff880`0f261ce6 : 00000000`00000000 00000000`0000352d 00000000`000002af fffff880`06388fc0 : nt!KiPageFault+0x260
fffff880`0b8856d8 00000000`00000000 : 00000000`0000352d 00000000`000002af fffff880`06388fc0 00000000`00000008 : Rt64win7+0x61ce6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+61ce6
fffff880`0f261ce6 410fb609        movzx   ecx,byte ptr [r9]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Rt64win7+61ce6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8750a0

FAILURE_BUCKET_ID:  X64_0xD1_Rt64win7+61ce6

BUCKET_ID:  X64_0xD1_Rt64win7+61ce6

Followup: MachineOwner

Yes,exactly,the same issue,we have tried almost everything but i believe is not only a driver issue but also a hardware damage.

 

[btc138]

I will try to install that generic driver as a last attempt...
Question for you guys, if it ends up coming back, what do you think would be my best option? A gentleman from another forum I posted the problem on also suggested having to RMA the board, but he said another option would be to purchase a network card to see if that solves the issue.

What do you think is a better solution?

 

[btc138]

Just realized that the generic drivers were the ones I had installed earlier, and I still had the problems. Must mean hardware issue then?

Let me know opinions about RMA'ing the board or purchasing a network card.

 

[panais]

Just realized that the generic drivers were the ones I had installed earlier, and I still had the problems. Must mean hardware issue then?

Let me know opinions about RMA'ing the board or purchasing a network card.

You mean motherboard?
Go with RMA,why?with new board you take also a new onboard network card

 

[hjonesMCT]

I will try to install that generic driver as a last attempt...
Question for you guys, if it ends up coming back, what do you think would be my best option? A gentleman from another forum I posted the problem on also suggested having to RMA the board, but he said another option would be to purchase a network card to see if that solves the issue.

What do you think is a better solution?

Okay, just for fun... can you try running Prime95 (Free Software - GIMPS) torture test to stress-test your processor? Sometimes, you can get a proc with a dead core, and when processes try to run on that core it can cause a bluescreen. Crazy, I know, but I have experience with this--and it happens.