Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD out of nowhere

28 Jul 2013   #1
digitz

Windows 7 Ultimate x64
 
 
BSOD out of nowhere

I was just doing something with Windows 7 Homegroups and out of nowhere BSOD, I would appreciate any help.


My System SpecsSystem Spec
.
28 Jul 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hello digitz.

The BSOD is caused by Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter driver.
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)
And the driver is very old.
Code:
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
Update it from Realtek

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
---------
My System SpecsSystem Spec
28 Jul 2013   #3
digitz

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by Arc View Post
Hello digitz.
Thank you very much but, I have ALFA Wireless device and I downloaded newest drivers from ALFA site, I know it says its 2009 but its not. And two days ago Windows update downloaded update for my wireless card.
My System SpecsSystem Spec
.

28 Jul 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.

ITEMVALUE
Name [00000007] Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter
Adapter Type Ethernet 802.3
Product Type Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter
Installed Yes
PNP Device ID USB\VID_0BDA&PID_8187\00C0CA6D9D25
Last Reset 28.7.2013. 16:47
Index 7
Service Name RTL8187
IP Address 192.168.1.22, fe80::b110:c925:811a:c0b0
IP Subnet 255.255.255.0, 64
Default IP Gateway 192.168.1.1
DHCP Enabled Yes
DHCP Server 192.168.1.1
DHCP Lease Expires 29.7.2013. 17:01
DHCP Lease Obtained 28.7.2013. 17:01
MAC Address 00:C0:CA:6D:9D:25
Driver c:\windows\system32\drivers\rtl8187.sys

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.
My System SpecsSystem Spec
28 Jul 2013   #5
YoYo155

Windows 10
 
 

Quote   Quote: Originally Posted by Arc View Post
Hello digitz.

The BSOD is caused by Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter driver.
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)

I just have to ask...

how did you get that stack?!
My System SpecsSystem Spec
28 Jul 2013   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

You can ask me via a PM ..... so that the thread doesnt loss its track.
My System SpecsSystem Spec
28 Jul 2013   #7
digitz

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by Arc View Post
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.

ITEMVALUE
Name [00000007] Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter
Adapter Type Ethernet 802.3
Product Type Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter
Installed Yes
PNP Device ID USB\VID_0BDA&PID_8187\00C0CA6D9D25
Last Reset 28.7.2013. 16:47
Index 7
Service Name RTL8187
IP Address 192.168.1.22, fe80::b110:c925:811a:c0b0
IP Subnet 255.255.255.0, 64
Default IP Gateway 192.168.1.1
DHCP Enabled Yes
DHCP Server 192.168.1.1
DHCP Lease Expires 29.7.2013. 17:01
DHCP Lease Obtained 28.7.2013. 17:01
MAC Address 00:C0:CA:6D:9D:25
Driver c:\windows\system32\drivers\rtl8187.sys

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.

I'm downloading this Windows 7 InstallPackage (Beta) - (RTL8187L!) Am I downloading correct one?
My System SpecsSystem Spec
28 Jul 2013   #8
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
28 Jul 2013   #9
digitz

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by Arc View Post
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.
Downloaded it, uninstalled old one, restarted computer, installed new one via Device Manager, still says its from 2009.
My System SpecsSystem Spec
28 Jul 2013   #10
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
Reply

 BSOD out of nowhere




Thread Tools Search this Thread
Search this Thread:

Advanced Search



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 23:10.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App