BSOD nearly everyday - apparently random

paulama · Jan 29, 2013

Hi,

My name is Paula and this is my first post here.
I am not sure I followed all the steps correctly, but I am attaching my zip file I created following instructions found here. Hope someone will have an idea of what is happening.

Please let me know if there is something I forgot, I am not lazy, just not very computer savvy, not yet

Thank you,
Paula

koolkat77 · Jan 29, 2013

Hello and welcome to SevenForums.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 44, {fffffa8003ff5c20, 1d7b, 0, 0}

*** WARNING: Unable to verify timestamp for avgtdia.sys
*** ERROR: Module load completed but symbols could not be loaded for avgtdia.sys
Probably caused by : mrxsmb.sys ( mrxsmb!RxCeCompleteConnectRequest+367 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: fffffa8003ff5c20, Address of the IRP
Arg2: 0000000000001d7b
Arg3: 0000000000000000
Arg4: 0000000000000000

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


IRP_ADDRESS:  fffffa8003ff5c20

FOLLOWUP_IP: 
mrxsmb!RxCeCompleteConnectRequest+367
fffff880`0636a7c7 33d2            xor     edx,edx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002a3d4fc to fffff80002a99fc0

STACK_TEXT:  
fffff880`091b2068 fffff800`02a3d4fc : 00000000`00000044 fffffa80`03ff5c20 00000000`00001d7b 00000000`00000000 : nt!KeBugCheckEx
fffff880`091b2070 fffff880`0636a7c7 : fffffa80`058503b0 fffffa80`058503b0 fffffa80`057010d0 fffffa80`058503b0 : nt! ?? ::FNODOBFM::`string'+0x31cac
fffff880`091b20b0 fffff880`0636c49e : fffffa80`05521200 00000000`00000702 fffffa80`0584d0d8 fffff880`00000000 : mrxsmb!RxCeCompleteConnectRequest+0x367
fffff880`091b2130 fffff880`0636c37c : 00000000`00000000 fffffa80`0584d0d8 fffff880`63437852 fffffa80`00000706 : mrxsmb!SmbWskAsynchronousConnectCompletionWorker+0x106
fffff880`091b21d0 fffff800`02a9d9c1 : fffffa80`03e865c3 00000000`00000000 00000000`00000000 fffff880`091b2218 : mrxsmb!SmbWskAsynchronousConnectCompletion+0xb8
fffff880`091b2220 fffff880`02cd49a5 : 00000000`00000000 00000000`00000002 fffffa80`03e864f0 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`091b2310 fffff880`02d3db2e : 00000000`00000003 00000000`00000000 fffffa80`05281710 00000000`00000000 : afd!WskProTLConnectComplete+0x105
fffff880`091b23d0 fffff880`02d3dc5b : fffffa80`057d1400 00000000`00000003 00000000`00000000 00000000`00000000 : afd!WskTdiConnectFinish+0x3e
fffff880`091b2400 fffff800`02a9d9c1 : fffffa80`05d5c6bb 00000000`00000000 00000000`00000000 00000000`e0000001 : afd!WskTdiCOMPConnect+0x1b
fffff880`091b2430 fffff880`01002f26 : fffffa80`05a2e410 fffff880`011bb502 00000000`00000014 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`091b2520 fffffa80`05a2e410 : fffff880`011bb502 00000000`00000014 00000000`00000000 fffffa80`03fdde13 : avgtdia+0x2f26
fffff880`091b2528 fffff880`011bb502 : 00000000`00000014 00000000`00000000 fffffa80`03fdde13 fffff800`02a9d9c1 : 0xfffffa80`05a2e410
fffff880`091b2530 00000000`00000014 : 00000000`00000000 fffffa80`03fdde13 fffff800`02a9d9c1 fffff880`091b2720 : tdx! ?? ::FNODOBFM::`string'+0x22
fffff880`091b2538 00000000`00000000 : fffffa80`03fdde13 fffff800`02a9d9c1 fffff880`091b2720 00000000`00000030 : 0x14


STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  mrxsmb!RxCeCompleteConnectRequest+367

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mrxsmb

IMAGE_NAME:  mrxsmb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4db78226

FAILURE_BUCKET_ID:  X64_0x44_mrxsmb!RxCeCompleteConnectRequest+367

BUCKET_ID:  X64_0x44_mrxsmb!RxCeCompleteConnectRequest+367

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

0: kd> lmvm mrxsmb
start             end                 module name
fffff880`06362000 fffff880`0638f000   mrxsmb     (pdb symbols)          c:\symbols\mrxsmb.pdb\F2AF218C70AA47C5BBEF9D82E48EA8D82\mrxsmb.pdb
    Loaded symbol image file: mrxsmb.sys
    Mapped memory image file: c:\symbols\mrxsmb.sys\4DB782262d000\mrxsmb.sys
    Image path: \SystemRoot\system32\DRIVERS\mrxsmb.sys
    Image name: mrxsmb.sys
    Timestamp:        Wed Apr 27 08:40:38 2011 (4DB78226)
    CheckSum:         00030225
    ImageSize:        0002D000
    File version:     6.1.7601.17605
    Product version:  6.1.7601.17605
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     MRxSmb.sys
    OriginalFilename: MRXSMB.Sys
    ProductVersion:   6.1.7601.17605
    FileVersion:      6.1.7601.17605 (win7sp1_gdr.110426-1503)
    FileDescription:  Windows NT SMB Minirdr
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

AVG is causing your BSOD-s, please remove it.

AVG | Download tools and utilities

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

Microsoft Security Essentials - Free Antivirus for Windows
- Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
  - http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html
  - How to Scan Your Computer With Multiple Antivirus Programs - How-To Geek

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.

Perform a System File Check:

Click on the start rb:
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Disk Check on your hard drive for file system errors and bad sectors on it:

http://www.sevenforums.com/tutorials/433-disk-check.html

Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.

Go to this link: Intel® Driver Update Utility check the system for latest updates, download and install them one by one.

Let us know the results.

paulama · Feb 6, 2013

It happened twice again

Hi Koolkat,

Thanks a lot for helping.
I am still getting the error though, although not as frequent.
I think I had 2 BSOD after the fixes you suggested.

I am attaching the file again.

Thank you,
Paula

koolkat77 · Feb 6, 2013

No new dumps files after 29-Jan-2013, please configure the system to collect small memory dump following this tutorial: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Is the firmware for your SSD up to date?

Please follow this:

writhziden said:
If you have an SSD, make sure the following are up to date:

SSD firmware

BIOS Version

Chipset Drivers

Hard disk controller drivers/SATA drivers

If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

paulama · Feb 25, 2013

happened again...

Hi KoolKat,

It finally happened again, twice just now.
Sending you the file.

Thank you!
Paula

koolkat77 said:
No new dumps files after 29-Jan-2013, please configure the system to collect small memory dump following this tutorial: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Is the firmware for your SSD up to date?

Please follow this:

writhziden said:

If you have an SSD, make sure the following are up to date:

SSD firmware

BIOS Version

Chipset Drivers

Hard disk controller drivers/SATA drivers

If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Click to expand...

koolkat77 · Feb 25, 2013

Looks like network drivers are corrupted. Please perform a clean install of these drivers.

Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC as well as your graphic drivers.

Code:

lmvm atikmdag
start             end                 module name
fffff880`0487c000 fffff880`0529d000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Sat Jul 28 07:48:09 2012 (501344D9)
    CheckSum:         009DA146
    ImageSize:        00A21000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

lmvm Rt64win7
start             end                 module name
fffff880`0424c000 fffff880`042ec000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Tue Sep 27 20:50:33 2011 (4E81E2B9)
    CheckSum:         0009FB77
    ImageSize:        000A0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:

How to Clean Left Over Driver Files with Driver Sweeper

Link to update:

Driver Reference Table - Rt64win7.sys

Don't worry about the title ATI Catalyst 'Vista'. These drivers are meant for Win Vis, Win 7 and Win 8 as well. Or go with the ATI automatic detection tool if you prefer.

Perform a System File Check to check the integrity of all protected Windows 7 :

Click on the start rb:
Type CMD on Search
Left click and Run as Administrator
Type
Code:
```
SFC /scannow
```

Full tutorial here:

SFC /Scannow Command - System File Checker

Let us know the results.

BSOD nearly everyday - apparently random

paulama

New member

My Computer

koolkat77

New member

My Computer

paulama

New member

My Computer

koolkat77

New member

My Computer

paulama

New member

My Computer

koolkat77

New member

My Computer

Similar threads