New
#11
Is your wireless a usb device?
Is your wireless a usb device?
Yes it is a TP-Link High Gain 300 MB/s USB Adapter.
Unfortunately, I have been unable to find a newer version than the one you have. The newest I can find is May 2010.
Okay do you think this is the problem?? Try a new USB device?
This is a brand new computer and I really doubt any of the hardware is failing. I did extensive test after I built and nothing was wrong. Now I get this ntoskrnl.exe file that is cuasing these BSOD's. I see some claims that it is adio driven and some that say its others.
Here are the two or three new dump files added to the previous ones.
Code:BugCheck 4E, {99, b74f6, 2, b6775} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000099, A PTE or PFN is corrupt Arg2: 00000000000b74f6, page frame number Arg3: 0000000000000002, current page state Arg4: 00000000000b6775, 0 Debugging Details: ------------------ BUGCHECK_STR: 0x4E_99 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: bf3.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff8000310ad7c to fffff80003081c40 STACK_TEXT: fffff880`0742de18 fffff800`0310ad7c : 00000000`0000004e 00000000`00000099 00000000`000b74f6 00000000`00000002 : nt!KeBugCheckEx fffff880`0742de20 fffff800`030296d0 : 00000000`00000000 fffff680`0008a2d0 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c fffff880`0742de60 fffff800`030524b3 : fffffa80`0cc01720 fffff700`00034f27 0000007f`fffffff8 fffff8a0`13f2c4f8 : nt! ?? ::FNODOBFM::`string'+0x333b8 fffff880`0742def0 fffff800`03053596 : fffffa80`0cc01720 fffffa80`00000006 fffff880`000333cd fffff800`00000011 : nt!MiDeleteAddressesInWorkingSet+0x307 fffff880`0742e7a0 fffff800`03357b1a : fffff8a0`12c5c060 fffff880`0742eae0 00000000`00000000 fffffa80`0db93b10 : nt!MmCleanProcessAddressSpace+0x96 fffff880`0742e7f0 fffff800`0333b09d : 00000000`c0000005 fffff800`03075101 00000000`dd304000 fffffa80`07382060 : nt!PspExitThread+0x56a fffff880`0742e8f0 fffff800`030753fa : 00000000`00000100 fffffa80`0db93bd0 00000000`00000001 fffff800`0308713d : nt!PsExitSpecialApc+0x1d fffff880`0742e920 fffff800`03075740 : 00000000`00000246 fffff880`0742e9a0 fffff800`0333b010 00000000`00000001 : nt!KiDeliverApc+0x2ca fffff880`0742e9a0 fffff800`03080f77 : fffffa80`0db93b10 00000000`00000844 00000000`00000000 fffffa80`0dbcde00 : nt!KiInitiateUserApc+0x70 fffff880`0742eae0 00000000`74ea2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c 00000000`0657f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74ea2e09 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiBadShareCount+4c fffff800`0310ad7c cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiBadShareCount+4c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c Followup: MachineOwner --------- BugCheck 1000007E, {ffffffffc0000005, fffff8800576faf0, fffff88006f56538, fffff88006f55d90} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::PageInAllocations+b8 ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8800576faf0, The address that the exception occurred at Arg3: fffff88006f56538, Exception Record Address Arg4: fffff88006f55d90, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: dxgmms1!VIDMM_GLOBAL::PageInAllocations+b8 fffff880`0576faf0 ff5028 call qword ptr [rax+28h] EXCEPTION_RECORD: fffff88006f56538 -- (.exr 0xfffff88006f56538) ExceptionAddress: fffff8800576faf0 (dxgmms1!VIDMM_GLOBAL::PageInAllocations+0x00000000000000b8) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000028 Attempt to read from address 0000000000000028 CONTEXT: fffff88006f55d90 -- (.cxr 0xfffff88006f55d90) rax=0000000000000000 rbx=fffffa800d8645f0 rcx=fffff8a013578500 rdx=fffff8a0156f3870 rsi=fffffa800bd36000 rdi=fffff8a0156f3870 rip=fffff8800576faf0 rsp=fffff88006f56770 rbp=0000000000000000 r8=0000000000000000 r9=fffffa800c5809c0 r10=0000000000000000 r11=00000000000002c8 r12=0000000000000000 r13=0000000000000032 r14=fffffa800d7b3190 r15=0000000000000144 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 dxgmms1!VIDMM_GLOBAL::PageInAllocations+0xb8: fffff880`0576faf0 ff5028 call qword ptr [rax+28h] ds:002b:00000000`00000028=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000028 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fb100 0000000000000028 FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::PageInAllocations+b8 fffff880`0576faf0 ff5028 call qword ptr [rax+28h] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffff8800576c763 to fffff8800576faf0 STACK_TEXT: fffff880`06f56770 fffff880`0576c763 : 00000000`00000000 fffffa80`0d7b3000 00000000`00000100 fffffa80`0c5809c0 : dxgmms1!VIDMM_GLOBAL::PageInAllocations+0xb8 fffff880`06f567d0 fffff880`0578665d : 00000000`00000000 fffff8a0`0d499480 fffffa80`00000007 fffffa80`0d528940 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xccf fffff880`06f569a0 fffff880`05786398 : fffff800`0489a080 fffff880`05785d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`06f56b90 fffff880`05785e96 : 00000000`00000000 fffffa80`07071ab0 00000000`00000080 fffffa80`0bbf8410 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`06f56bc0 fffff800`03363fee : 00000000`028320cc fffffa80`0b9cdb60 fffffa80`06d0c740 fffffa80`0b9cdb60 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`06f56c00 fffff800`030ba5e6 : fffff800`0323ee80 fffffa80`0b9cdb60 fffff800`0324ccc0 fffff880`01668cb0 : nt!PspSystemThreadStartup+0x5a fffff880`06f56c40 00000000`00000000 : fffff880`06f57000 fffff880`06f51000 fffff880`06f55da0 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::PageInAllocations+b8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1 STACK_COMMAND: .cxr 0xfffff88006f55d90 ; kb FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::PageInAllocations+b8 BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::PageInAllocations+b8 Followup: MachineOwner ---------
Still pointing to memory or DirectX/graphics card issues. You may have to wait until after you run the memory tools I gave you to find out which is causing the issues.
Well see its only happened while playing BF3, which I need that Wireless adapter to play online. But Im getting ready to do driver verify here soon.
Re-installed the game, drivers, patches. Like IVe said I never had this issue until recently. Like for a week or so.