BSOD opening facebook video, error 0x000000d1 (0xfffff880071....

[bettingtime]

It was really random, I formatted my computer in December, and had no problems since then! and today running a simple video, I had it crashed, error was :
0x000000d1 (0xfffff8800718f000, 0x0000000000000002, 0x0000000000000000, 0xfffff88004fe8242).

You can find the log files attached! Thank you so much for your time!!



My computer
CPU Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
MotherBoard ASRock Z77 Pro4
BIOS Date: 07/11/13 19:00:52 Ver: 04.06.05
15,89 GB
(1) M4-CT128M4SSD2 ATA Device (2) PLEXTOR PX-128M5Pro ATA Device
(1) ASUS Xonar DG Audio Device (2) AMD High Definition Audio Device (3) HD Webcam C270
(1) AMD Radeon HD 6800 Series (2) Intel(R) HD Graphics 3000
Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1

 

[Arc]

Hi bettingtime.

Update the network driver from http://www.realtek.com.tw/downloads...d=5&Level=5&Conn=4&DownTypeID=3&GetDown=false .... download the second item from the list (that is the "Win7 and Server 2008 R2 Auto Installation Program" one) and install it.

Report us for any further BSOD after doing it.
____________________________________

BugCheck D1, {fffff8800718f000, 2, 0, fffff88004fe8242}

*** 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+7b242 )

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecc100
GetUlongFromAddress: unable to read from fffff80002ecc1c0
 fffff8800718f000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
Rt64win7+7b242
fffff880`04fe8242 410fb609        movzx   ecx,byte ptr [r9]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  fffff8800d9fb530 -- (.trap 0xfffff8800d9fb530)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000f28017f rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004fe8242 rsp=fffff8800d9fb6c8 rbp=00000000000034a3
 r8=0000000000006947  r9=fffff8800718f000 r10=0000000000000000
r11=fffff88007189fda r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
Rt64win7+0x7b242:
fffff880`04fe8242 410fb609        movzx   ecx,byte ptr [r9] ds:fffff880`0718f000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c92469 to fffff80002c92ec0

STACK_TEXT:  
fffff880`0d9fb3e8 fffff800`02c92469 : 00000000`0000000a fffff880`0718f000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0d9fb3f0 fffff800`02c910e0 : 00000000`c120f000 4e9394ac`d1c0bb01 f0001050`ee0bb2e2 00000000`00008f83 : nt!KiBugCheckDispatch+0x69
fffff880`0d9fb530 fffff880`04fe8242 : 00000000`00000000 00000000`0000352b 00000000`00000236 fffff880`07189fc0 : nt!KiPageFault+0x260
fffff880`0d9fb6c8 00000000`00000000 : 00000000`0000352b 00000000`00000236 fffff880`07189fc0 00000000`00000008 : Rt64win7+0x7b242


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+7b242
fffff880`04fe8242 410fb609        movzx   ecx,byte ptr [r9]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Rt64win7+7b242

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e53b15d

FAILURE_BUCKET_ID:  X64_0xD1_Rt64win7+7b242

BUCKET_ID:  X64_0xD1_Rt64win7+7b242

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_rt64win7+7b242

FAILURE_ID_HASH:  {e4d59a9d-e839-0bbb-3cb6-ffb96cd89dd9}

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

4: kd> lmvm Rt64win7
start             end                 module name
fffff880`04f6d000 fffff880`04ffa000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Tue Aug 23 19:25:41 2011 (4E53B15D)
    CheckSum:         00097338
    ImageSize:        0008D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[bettingtime]

The most common approach of most computer stores to BSOD is to computer format, this has a lot of costs, and time cost also. While you guys provide ''a perfect solution'', this is awsome, I really can't thank you enough

If there's some place I can make a donation, let me know

Cheers,

 

[Arc]

We dont have any donation system.

If at any point of time you think that your issue is over, please mark this thread as solved. That will be enough, because it will be helpful for forum indexing.