New
#1
BSOD For the first time...
Happend while playing a game. I did windows update today and one of the updates failed, i was thinking thats what caused it.. any help would be great thanks...
Happend while playing a game. I did windows update today and one of the updates failed, i was thinking thats what caused it.. any help would be great thanks...
Welcome to the forum Benjameanos,
Pretty straight forward, you need to remove AVG;
Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stabilityCode:Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\admin\Downloads\BENJY-PC-Sat_07_12_2014_200624_76\071214-29234-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0xfffff800`03050000 PsLoadedModuleList = 0xfffff800`032936d0 Debug session time: Sun Jul 13 08:07:32.267 2014 (UTC + 6:00) System Uptime: 0 days 9:08:48.031 Loading Kernel Symbols ............................................................... ................................................................ ................................................ Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 44, {fffffa800c8bfdb0, 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: fffffa800c8bfdb0, Address of the IRP Arg2: 0000000000001d7b Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ IRP_ADDRESS: fffffa800c8bfdb0 FOLLOWUP_IP: mrxsmb!RxCeCompleteConnectRequest+367 fffff880`0416c7c7 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 fffff800030717fc to fffff800030c5bc0 STACK_TEXT: fffff880`0dcc0fc8 fffff800`030717fc : 00000000`00000044 fffffa80`0c8bfdb0 00000000`00001d7b 00000000`00000000 : nt!KeBugCheckEx fffff880`0dcc0fd0 fffff880`0416c7c7 : fffffa80`0f914b80 fffffa80`0f914b80 fffffa80`11fc72b0 fffffa80`0f914b80 : nt! ?? ::FNODOBFM::`string'+0x31cdc fffff880`0dcc1010 fffff880`0416e49e : fffffa80`0f433700 00000000`00000702 fffffa80`0cd40448 fffff880`00000000 : mrxsmb!RxCeCompleteConnectRequest+0x367 fffff880`0dcc1090 fffff880`0416e37c : 00000000`00000000 fffffa80`0cd40448 fffff880`63437852 00000000`00000706 : mrxsmb!SmbWskAsynchronousConnectCompletionWorker+0x106 fffff880`0dcc1130 fffff800`030c95d1 : fffffa80`0f17eb33 fffffa80`0d8ca9f0 00000000`00000000 fffff880`0dcc1178 : mrxsmb!SmbWskAsynchronousConnectCompletion+0xb8 fffff880`0dcc1180 fffff880`03e059b5 : 00000000`00000000 00000000`00000002 fffffa80`0f17ea60 00000000`00000000 : nt!IopfCompleteRequest+0x341 fffff880`0dcc1270 fffff880`03e6eb2e : 00000000`00000003 00000000`00000000 fffffa80`0fd75710 00000000`00000000 : afd!WskProTLConnectComplete+0x105 fffff880`0dcc1330 fffff880`03e6ec5b : fffffa80`0fb5dc10 00000000`00000003 00000000`00000000 00000000`00000000 : afd!WskTdiConnectFinish+0x3e fffff880`0dcc1360 fffff800`030c95d1 : fffffa80`0ce0db4b 00000000`00000000 00000000`00000000 00000000`e0000001 : afd!WskTdiCOMPConnect+0x1b fffff880`0dcc1390 fffff880`03f46365 : fffffa80`0cca2010 fffff880`03f10502 00000000`00000014 00000000`00000000 : nt!IopfCompleteRequest+0x341 fffff880`0dcc1480 fffffa80`0cca2010 : fffff880`03f10502 00000000`00000014 00000000`00000000 fffffa80`0f25f313 : avgtdia+0x9365 fffff880`0dcc1488 fffff880`03f10502 : 00000000`00000014 00000000`00000000 fffffa80`0f25f313 fffff800`030c95d1 : 0xfffffa80`0cca2010 fffff880`0dcc1490 00000000`00000014 : 00000000`00000000 fffffa80`0f25f313 fffff800`030c95d1 fffff880`0dcc1680 : tdx! ?? ::FNODOBFM::`string'+0x22 fffff880`0dcc1498 00000000`00000000 : fffffa80`0f25f313 fffff800`030c95d1 fffff880`0dcc1680 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`04164000 fffff880`04191000 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.
compared to other antivirus or internet security software. It is free and lightweight:-
- Microsoft Security Essentials - Free Antivirus for Windows
- Malwarebytes: Removes malware including viruses, spyware, worms and trojans, plus it protects your computer
- Good and Free system security combination.
WarningDo not start the free trial of Malware Bytes; remember to deselect that option when prompted.
Perform a Clean boot:Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-
Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:
Run Disk Check on your Hard Drive for file system errors and bad sectors on it:
Good luck.
What anti virus should i get? this one always seemed to work great for me
What anti virus should i get? this one always seemed to work great for me