BSOD while on Facebook, BCCode: d1

10schick

New member
Local time
4:39 PM
Messages
1
I've gotten several BSODs recently while playing games on Facebook (Farmtown, Castle Age, CA HOD, Scrabble, and Bubble Witch Saga). The number of open tabs doesn't seem to make a difference. Any help to fix the problem would be greatly appreciated. Thanks. :)

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000044
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880040888C1
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
 

My Computer

OS
Windows Home Premium 64 bit
Welcome to SevenForums.

Please remove AVG:

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-
   Warning
:ar: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {44, 2, 0, fffff88002cfe8c1}

*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+5c8c1 )

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfa100
GetUlongFromAddress: unable to read from fffff80002cfa1c0
 0000000000000044 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
athrx+5c8c1
fffff880`02cfe8c1 8b4044          mov     eax,dword ptr [rax+44h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  chrome.exe

TAG_NOT_DEFINED_c000000f:  FFFFF88002F22FB0

TRAP_FRAME:  fffff88002f22650 -- (.trap 0xfffff88002f22650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004545998
rdx=fffffa8004545998 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002cfe8c1 rsp=fffff88002f227e0 rbp=0000000000000000
 r8=0000000000000000  r9=fffffa8004b4c0e8 r10=fffffa80049d9340
r11=fffffa8004545998 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
athrx+0x5c8c1:
fffff880`02cfe8c1 8b4044          mov     eax,dword ptr [rax+44h] ds:00000000`00000044=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002aca569 to fffff80002acafc0

STACK_TEXT:  
fffff880`02f22508 fffff800`02aca569 : 00000000`0000000a 00000000`00000044 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f22510 fffff800`02ac91e0 : fffffa80`04ac3210 00000000`00000000 fffffa80`049d9040 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f22650 fffff880`02cfe8c1 : fffffa80`04545998 fffff880`02f22860 fffffa80`049171a0 fffffa80`04a0d030 : nt!KiPageFault+0x260
fffff880`02f227e0 fffffa80`04545998 : fffff880`02f22860 fffffa80`049171a0 fffffa80`04a0d030 fffffa80`0000001a : athrx+0x5c8c1
fffff880`02f227e8 fffff880`02f22860 : fffffa80`049171a0 fffffa80`04a0d030 fffffa80`0000001a fffffa80`0472e270 : 0xfffffa80`04545998
fffff880`02f227f0 fffffa80`049171a0 : fffffa80`04a0d030 fffffa80`0000001a fffffa80`0472e270 fffffa80`058b9120 : 0xfffff880`02f22860
fffff880`02f227f8 fffffa80`04a0d030 : fffffa80`0000001a fffffa80`0472e270 fffffa80`058b9120 fffff880`02cfbf5e : 0xfffffa80`049171a0
fffff880`02f22800 fffffa80`0000001a : fffffa80`0472e270 fffffa80`058b9120 fffff880`02cfbf5e 00000000`00000000 : 0xfffffa80`04a0d030
fffff880`02f22808 fffffa80`0472e270 : fffffa80`058b9120 fffff880`02cfbf5e 00000000`00000000 fffffa80`04545998 : 0xfffffa80`0000001a
fffff880`02f22810 fffffa80`058b9120 : fffff880`02cfbf5e 00000000`00000000 fffffa80`04545998 fffff880`04826000 : 0xfffffa80`0472e270
fffff880`02f22818 fffff880`02cfbf5e : 00000000`00000000 fffffa80`04545998 fffff880`04826000 fffff880`02cfba84 : 0xfffffa80`058b9120
fffff880`02f22820 00000000`00000000 : fffffa80`04545998 fffff880`04826000 fffff880`02cfba84 fffffa80`04545998 : athrx+0x59f5e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+5c8c1
fffff880`02cfe8c1 8b4044          mov     eax,dword ptr [rax+44h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrx+5c8c1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4acea2b7

FAILURE_BUCKET_ID:  X64_0xD1_athrx+5c8c1

BUCKET_ID:  X64_0xD1_athrx+5c8c1

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

1: kd> lmvm athrx
start             end                 module name
fffff880`02ca2000 fffff880`02dfa000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Fri Oct 09 08:40:55 2009 (4ACEA2B7)
    CheckSum:         0015580F
    ImageSize:        00158000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If its wireless, match your device from here:
If its not a wireless, match your device from here:
Disk Check on your hard drive for file system errors and bad sectors on it:
Perform a System File Check:

  1. Click on the start :orb:
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type SFC /scannow
Full tutorial here:
Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.


Let us know the results.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self assembled
OS
Windows 10 Home 64Bit
CPU
Intel Core i5 10400 @ 2.90GHz
Motherboard
Intel Corporation DG41WV (PROCESSOR)
Memory
8.00GB Single-Channel Unknown @ 1329MHz (16-20-20-38)
Sound Card
Realtek High Definition Audio
Monitor(s) Displays
DELL E170S
Screen Resolution
1280x1024 pixels
Hard Drives
931GB TOSHIBA DT01ACA100 (SATA)
238GB TEAM TM8PS7256G (SATA SSD)
Case
Nothing Fancy
Cooling
Fans
Keyboard
A4 Tech Co LTD
Mouse
A4 Tech Co Ltd/Logitech
Internet Speed
25 Mbps

My Computer

Computer type
PC/Desktop
OS
Windows 7 Professional 64bit
CPU
AMD Athlon (tm) X2 5200+ Dual Core 2712 Mhz
Motherboard
Asus
Memory
4GB
Graphics Card(s)
Nividia GeForce 8600 GTS- DIED 25/7/2013 R.I.P
Sound Card
None
Monitor(s) Displays
22" Yuraku LCD (Dont ask)
Screen Resolution
1280x960
Hard Drives
2TB WD Caviar green
PSU
Windy up type
Case
Scout cm Storm
Cooling
Hair dryer on full cool power ;-)
Keyboard
QWERTY
Mouse
Microsoft Special
Internet Speed
BT Infinity 9.38Mb/s Wheeeeeeeeeeeeeeee!!
Antivirus
MSE
Browser
Internet Explore 10 and Chrome
Other Info
Don't shout...I've got a Hangover!
Back
Top