blue screen of death

Coleman2247 · Oct 18, 2014

Hello
I have just experience my 3rd blue screen of death on this pc in its lifetime.The first time it was my gpu drivers and that problem has since been resolved, my 2nd time it was my security, and I have just had my 3rd one. Can any of you guys try and help me figure out what it was ?.I am running windows 7 64bit ultimate edition.

link to minidumb file-https://www.mediafire.com/?22rgz1hhgus68j1

Pc specs-
Cpu:Amd A10 7850k
Ram:8gb gskil tirdentx
Motherboard:Gigabyte GA-F2A88XM-D3H Micro ATX FM2+
Harddrive:Seagate Desktop SSHD 1TB
ST1000DX001
Os:Windows 7
Power Supply:500 watt Thermaltake
gpu-assus r7 265

here is the log

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03263000 PsLoadedModuleList = 0xfffff800`034a6890
Debug session time: Sat Oct 18 12:14:48.096 2014 (UTC - 4:00)
System Uptime: 1 days 8:46:35.283
*******************************************************************************
* *
* 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: fffff880019c4db0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff880019c4db0, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003510100
GetUlongFromAddress: unable to read from fffff800035101c0
fffff880019c4db0 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
tcpip!IPSecDetermineSecureFilterMatch+0
fffff880`019c4db0 4c8bdc mov r11,rsp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff88002ffec00 -- (.trap 0xfffff88002ffec00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002ffedf8 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880019c4db0 rsp=fffff88002ffed98 rbp=fffffa800a6702d0
r8=fffffa800a765580 r9=fffffa800a91907c r10=fffffa800a765580
r11=fffff88002ffef58 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
tcpip!IPSecDetermineSecureFilterMatch:
fffff880`019c4db0 4c8bdc mov r11,rsp
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032d8169 to fffff800032d8bc0

FAILED_INSTRUCTION_ADDRESS:
tcpip!IPSecDetermineSecureFilterMatch+0
fffff880`019c4db0 4c8bdc mov r11,rsp

STACK_TEXT:
fffff880`02ffeab8 fffff800`032d8169 : 00000000`0000000a fffff880`019c4db0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`02ffeac0 fffff800`032d6de0 : fffffa80`0a6702d0 fffffa80`07fcb2c0 00000000`0000003d fffffa80`0a919010 : nt!KiBugCheckDispatch+0x69
fffff880`02ffec00 fffff880`019c4db0 : fffff880`01871ff8 fffffa80`0a765580 fffff880`018289a1 fffffa80`09b7a6e0 : nt!KiPageFault+0x260
fffff880`02ffed98 fffff880`01871ff8 : fffffa80`0a765580 fffff880`018289a1 fffffa80`09b7a6e0 fffff880`02ffee30 : tcpip!IPSecDetermineSecureFilterMatch
fffff880`02ffeda0 fffff880`0188bbb5 : fffffa80`0a919010 00000000`00000000 fffffa80`09ba2010 fffff880`01890205 : tcpip!IpSecLookupApplicableOverheadToTcpConnection+0x128
fffff880`02ffeed0 fffff880`01871eb2 : 00000000`00000000 00000000`00000000 0000000e`00000000 fffff880`02fff050 : tcpip!InetInspectAdjustMtu+0x45
fffff880`02ffef20 fffff880`01871afd : 00000000`00000004 00000000`000005c0 fffff800`032e2aa5 fffff880`009f1180 : tcpip!TcpRecomputeMss+0x72
fffff880`02ffef60 fffff880`01868d8f : 00000000`00000001 00000000`00000000 00000000`00000001 fffff880`01808f41 : tcpip!TcpUpdatePathInfoTcb+0x1fd
fffff880`02fff050 fffff880`01888806 : 00000000`00000000 fffff880`01887b18 fffff880`01968128 00000000`00000000 : tcpip!TcpTcbSend+0x98f
fffff880`02fff2d0 fffff880`018881a6 : 00000000`00000000 00000000`00000000 00000000`00000e88 00000000`00b407cf : tcpip!TcpFlushDelay+0x316
fffff880`02fff3b0 fffff800`032e385c : fffff880`02fff4c0 00000000`00021007 00000000`00000000 00000000`00000001 : tcpip!TcpPeriodicTimeoutHandler+0x3f9
fffff880`02fff430 fffff800`032e36f6 : fffffa80`08849168 fffffa80`08849168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff880`02fff4a0 fffff800`032e35de : 00000112`baab657a fffff880`02fffb18 00000000`007369e7 fffff880`02fdb268 : nt!KiProcessExpiredTimerList+0xc6
fffff880`02fffaf0 fffff800`032e33c7 : 00000063`1484e4c4 00000063`007369e7 00000063`1484e4dd 00000000`000000e7 : nt!KiTimerExpiration+0x1be
fffff880`02fffb90 fffff800`032d08ca : fffff880`02fd7180 fffff880`02fe1fc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff880`02fffc40 00000000`00000000 : fffff880`03000000 fffff880`02ffa000 fffff880`02fffc00 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_IP:
tcpip!IPSecDetermineSecureFilterMatch+0
fffff880`019c4db0 4c8bdc mov r11,rsp

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: tcpip!IPSecDetermineSecureFilterMatch+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME: tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 533f5bd4

FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_tcpip!IPSecDetermineSecureFilterMatch+0

BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_tcpip!IPSecDetermineSecureFilterMatch+0

Followup: MachineOwner

kapitalistas · Oct 18, 2014

http://windows.microsoft.com/en-us/windows7/resolving-stop-blue-screen-errors-in-windows-7 hope this solves your problem.

Ironsounds · Oct 18, 2014

Hello... All my experience with BSOD is due to a Hardware communication, interrupting between the MB and Windows.
1) Make sure you have no un-happy hardware drivers in your "Device Manager"... No Yellow or Red icon indicators
2) Clean all card/stick edges with rubbing alcohol... And Re-insert cards.
3) Inspect and clean all DATA and Power connections... to your Hardware and MB.
4) Verify all devices CPU/GPU/MB temperatures are with in Normal operating temperatures.
5) Verify your Power Supply 12Vdc has enough current , To operate your Video Card and CPU, at the Performance setting you are using.
6) Test One Part at a time in a known Good Computer.

BSOD are tuff problems too solve... and sometimes takes all those steps I listed to get rid of them... Sometimes it can be simple fix by a BIO Setting/Driver/Software Removal/Preference Settings.

TO PROVE it is the Hardware ( FOR ME ) means installing a Fresh WIN 7 SP1 RAW ISO ( NO UPDATES ) install on a spare Hardrive with just Device Drivers will verify this... If you Blue screen with this, your hardware has a problem communicating with the MB. http://www.w7forums.com/threads/official-windows-7-sp1-...

Coleman2247 · Oct 19, 2014

I think it may be my avast security...

johnbl · Oct 19, 2014

update this file Rt64win7.sys Tue Sep 27 07:50:33 2011
from here:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
------------------
the bugcheck was in TCPIP
the problem will be caused by the Ethernet driver or a virus scanner.

Sometimes the virus scanner gets messed up because of a bug in a Ethernet driver.
Sometimes a virus scanner messes up the Ethernet driver by changing the timing of the driver as it tries to protect you by scanning.
This type of problem can also occur if you have more than one virus scanner scanning at the same time.

I would start with a updated Ethernet driver, reboot and see if you still get the problem. Then disable the scanner and retry.

Coleman2247 · Oct 19, 2014

johnbl :

update this file Rt64win7.sys Tue Sep 27 07:50:33 2011
from here:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
------------------
the bugcheck was in TCPIP
the problem will be caused by the Ethernet driver or a virus scanner.

Sometimes the virus scanner gets messed up because of a bug in a Ethernet driver.
Sometimes a virus scanner messes up the Ethernet driver by changing the timing of the driver as it tries to protect you by scanning.
This type of problem can also occur if you have more than one virus scanner scanning at the same time.

I would start with a updated Ethernet driver, reboot and see if you still get the problem. Then disable the scanner and retry.

I was connecting to a vpn when it crashed,so I suspect it was the Ethernet drivers

johnbl · Oct 19, 2014

I think so also. try the update it is dated 9-24-2014

Coleman2247 :

johnbl :

I was connecting to a vpn when it crashed,so I suspect it was the Ethernet drivers

Search

blue screen of death

Coleman2247

Reputable

johnbl

kapitalistas

Honorable

Ironsounds

Champion

Coleman2247

Reputable

johnbl

Polypheme

Coleman2247

Reputable

johnbl

Polypheme

TRENDING THREADS

Latest posts

Moderators online

Share this page