New
#1
BSOD out of nowhere
I was just doing something with Windows 7 Homegroups and out of nowhere BSOD, I would appreciate any help.
I was just doing something with Windows 7 Homegroups and out of nowhere BSOD, I would appreciate any help.
Hello digitz.
The BSOD is caused by Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter driver.
And the driver is very old.Code:fffff880`02624508 fffff880`0147298b ndis!ndisOidRequestComplete+0xb fffff880`02624510 fffff880`04171d76Unable to load image \SystemRoot\system32\DRIVERS\rtl8187.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rtl8187.sys *** ERROR: Module load completed but symbols could not be loaded for rtl8187.sys rtl8187+0x12d76 fffff880`02624518 fffff880`01470000 ndis!IsPM62Supported <PERF> (ndis+0x0) fffff880`02624520 fffff880`014d7444 ndis!__PchSym_+0x534 fffff880`02624528 fffff880`01470000 ndis!IsPM62Supported <PERF> (ndis+0x0) fffff880`02624530 fffff880`014dc3ac ndis!__PchSym_ <PERF> (ndis+0x6c3ac) fffff880`02624538 fffff880`01470000 ndis!IsPM62Supported <PERF> (ndis+0x0) fffff880`02624540 fffff880`014de428 ndis!__PchSym_ <PERF> (ndis+0x6e428) fffff880`02624548 fffff880`0415f000 rtl8187 fffff880`02624550 fffff880`041d1120 rtl8187+0x72120 fffff880`02624558 fffff880`0415f000 rtl8187 fffff880`02624560 fffff880`041d12dc rtl8187+0x722dc fffff880`02624568 fffff880`0415f000 rtl8187 fffff880`02624570 fffff880`041d157c rtl8187+0x7257c fffff880`02624578 fffff880`0415f000 rtl8187 fffff880`02624580 fffff880`041d16e4 rtl8187+0x726e4 fffff880`02624588 fffff880`01470000 ndis!IsPM62Supported <PERF> (ndis+0x0) fffff880`02624590 fffff880`014dd4d4 ndis!__PchSym_ <PERF> (ndis+0x6d4d4) fffff880`02624598 fffff880`01470000 ndis!IsPM62Supported <PERF> (ndis+0x0) fffff880`026245a0 fffff880`014d757c ndis!__PchSym_+0x66c fffff880`026245a8 fffff880`01470000 ndis!IsPM62Supported <PERF> (ndis+0x0) fffff880`026245b0 fffff880`014d75a0 ndis!__PchSym_+0x690 fffff880`026245b8 fffff880`03edb000 vwififlt!WPP_SF_ <PERF> (vwififlt+0x0) fffff880`026245c0 fffff880`03ee91b0 vwififlt!__PchSym_ <PERF> (vwififlt+0xe1b0) fffff880`026245c8 fffff880`03edb000 vwififlt!WPP_SF_ <PERF> (vwififlt+0x0) fffff880`026245d0 fffff880`03ee93c0 vwififlt!__PchSym_ <PERF> (vwififlt+0xe3c0)
Update it from RealtekCode:fffff880`0415f000 fffff880`041d7000 rtl8187 T (no symbols) Loaded symbol image file: rtl8187.sys Image path: \SystemRoot\system32\DRIVERS\rtl8187.sys Image name: rtl8187.sys Timestamp: Wed Dec 09 14:46:39 2009 (4B1F6AF7) CheckSum: 000706D4 ImageSize: 00078000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Let us know the results.
______________________________________________________________________________
BSOD ANALYSIS:
Code:............... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff88001472a1b, fffff88002624660, 0} Probably caused by : ndis.sys ( ndis!ndisOidRequestComplete+9b ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff88001472a1b, Address of the instruction which caused the bugcheck Arg3: fffff88002624660, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: ndis!ndisOidRequestComplete+9b fffff880`01472a1b 803e05 cmp byte ptr [rsi],5 CONTEXT: fffff88002624660 -- (.cxr 0xfffff88002624660) rax=0000000000000001 rbx=fffff880031aee40 rcx=fffff880031aee40 rdx=0000000000000000 rsi=0000000000000000 rdi=fffff88002625100 rip=fffff88001472a1b rsp=fffff88002625040 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=fffffa8004406750 r11=0000000000000000 r12=fffff880031aee00 r13=0000000000000000 r14=fffff880014d3110 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 ndis!ndisOidRequestComplete+0x9b: fffff880`01472a1b 803e05 cmp byte ptr [rsi],5 ds:002b:00000000`00000000=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88001472a1b STACK_TEXT: fffff880`02625040 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisOidRequestComplete+0x9b FOLLOWUP_IP: ndis!ndisOidRequestComplete+9b fffff880`01472a1b 803e05 cmp byte ptr [rsi],5 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ndis!ndisOidRequestComplete+9b FOLLOWUP_NAME: MachineOwner MODULE_NAME: ndis IMAGE_NAME: ndis.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5034f6b2 STACK_COMMAND: .cxr 0xfffff88002624660 ; kb FAILURE_BUCKET_ID: X64_0x3B_ndis!ndisOidRequestComplete+9b BUCKET_ID: X64_0x3B_ndis!ndisOidRequestComplete+9b Followup: MachineOwner ---------
What ALFA sold you is an old Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter. As they dont have produced it, they dont have drivers, too.
No code has to be inserted here.
This old driver is causing BSOD there. And if it is there, it is possible that the BSODs will continue. As it is a realtek device (forget the brand), search for updates in relatek. It no updates are still available, change the adapter.
Yes, go for it. But seeing the update time of the driver, I am not feeling very well. The BETA drivers are so old
Anyway, get it and see how it goes.
We may check the timestamps successfully, if there are more BSODs. But better there is no more :)
Coz, in that case our next step would be to change the adapter. Get one form such a vendor who makes their devices themselves, so that the updated drivers are regularly available.