Support Forums

Last sunday my laptop running windows 7 gave me a blue screen error which I dismissed. After I restarted and about 20 minutes into using it I could not connect to the Internet. I verified that the problem was my computer after attempting to connect to multiple wifi networks. It does connect but returns "Limited Access" when I hover over the current network. When I check the network status it shows that 0 packets are being sent and received. It also appears that the two network adapters in use are VMware. Should that be default for my computer? I only know VMware as the virtual machine I installed some time ago. The network diagnosis found that "There might be a problem with your network adapter and it's driver." or something along those lines. Do you think the blue screen error was due to a failure in one of my wireless network drivers/adapters? How do I fix this problem? I also did memory diagnostics and startup repair from my windows 7 disk which did nothing. The sfc /scannow completed and there were no integrity violations. My active connections are Hamachi, Local area connection(Broadcom virtual wireless adapter)(X), VMware1, VMware2, Wireless Network Connection(DW1501 Wireless-N WLAN Hald-Mini Card), and Wireless Network Connection 2(Microsoft virtual Wifi Miniport Adapter)(X). The (X) means that there's a red X over the connection icon. Diagnosis for the first wireless network connection and local area connection showed that there was a problem with the driver for the adapter, which windows failed to repair. There was no diagnosis option for wireless network connection 2. It also appears that my Ethernet Controller and PCI Simple Communicatoons Controller are not installed, if that means anything. It showed that as an error when I attempted to update my network adapters(Device driver software was not successfully installed).

VMWare is an automatically connected network because it's a bridge from your main network for when you run a virtual machine. So connecting to multiple networks here is not the problem.

This could be a driver problem, which also initiated the BSOD crash.

If you require help with a BSOD you should do the following...

1. Locate your Minidumps folder:

• This is usually placed in %SystemRoot%\Minidump\. Navigate to that location and copy all of the files over into a folder on your desktop and preferrably compress them into an archive before uploading to a file host.

2. Provide your crash dumps in the next post with the download link to the .dmp files

• I will review/debug the crash dump to more accurately verify the cause of this BSOD.
  
• Note: Further instructions will be given after I have reviewed the crash dump, be patient, and don't do ANYTHING while i'm in the review process as solving BSOD's requires patience, and a logical order of operations. If you do anything that I have not asked you to do, you are only puting your own system at risk, because now you're just on your own doing trial and error.

The crash dump may be of use in solving some of your other problems here.

http://www.filedropper.com/crashdump
Sorry for the lateness xD.

Uhh :S Okay?

The archive you provided doesn't have any binary data it's 0Kb in size.

Please check it out as soon as possible, I have a flight in 6 hours.

---

That's strange, hold on a second.

I did, there's nothing in the archive, the archive itself isn't even a valid archive, and it contains no bytes.

Here, http://www.mediafire.com/?a2apkd5jzled9c9 ; I guess it was corrupted.

BSOD BUGCHECK SUMMARY

3 of them point to the NT Operating System Kernel, so those ones are virtually useless to me. Your kernel is not the culprit for this BSOD anyways.

But one of them points to the pacer.sys driver (pacer!PcFilterRequestComplete+68 )


I would recommend running System File Checker for starters. Open up an elevated command prompt, and type this command:

Reboot if necessary.

This was most likely caused by a bad driver here though, as param 3 on that BSOD dump indicates an execute operation and both 1 and 4 are 0x0. There's a number of causes for this, but all are related to the driver making a bad function call.

However the pacer.sys driver is a Windows driver for the Microsoft Windows QoS scheduler. Which is why i'm suggesting that you do a file integrity check.

You are ALSO not running SP1 -- Download and install Windows Service Pack 1.

And lastly, Remove AVG, as it's also a known cause for BSOD's. Install/Replace it with Microsoft Security Essentials and you shouldn't have any apparent problems. MSE is much better anyways for security.

(02-21-2012, 04:17 AM)AceInfinity Wrote: [ -> ]BSOD BUGCHECK SUMMARY

Code:

Loading Dump File [C:\Users\Infinity\_jcgriff2_\dbug\__Kernel__\011412-74006-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Jan 14 18:55:20.507 2012 (GMT-7)
System Uptime: 0 days 22:17:22.067
BugCheck D1, {0, 2, 8, 0}
*** WARNING: Unable to verify timestamp for HssDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for HssDrv.sys
Probably caused by : pacer.sys ( pacer!PcFilterRequestComplete+68 )
PROCESS_NAME:  System
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_pacer!PcFilterRequestComplete+68
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000008 00000000`00000000
BiosVersion = A06
BiosReleaseDate = 07/19/2010
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron N4010
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\Infinity\_jcgriff2_\dbug\__Kernel__\011312-35693-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jan 13 20:37:05.002 2012 (GMT-7)
System Uptime: 2 days 5:49:30.562
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_nt!KiSwapContext+7a
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`03b64040 fffff800`00b9c510
BiosVersion = A06
BiosReleaseDate = 07/19/2010
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron N4010
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\Infinity\_jcgriff2_\dbug\__Kernel__\010512-34647-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Jan  5 14:17:02.156 2012 (GMT-7)
System Uptime: 1 days 4:37:48.717
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_nt!KiSwapContext+7a
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`045da040 fffff800`00b9c510
BiosVersion = A06
BiosReleaseDate = 07/19/2010
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron N4010
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\Infinity\_jcgriff2_\dbug\__Kernel__\010412-42245-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Jan  4 09:38:18.153 2012 (GMT-7)
System Uptime: 3 days 21:41:30.324
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_nt!KiSwapContext+7a
Bugcheck code 1000009F
Arguments 00000000`00000004 00000000`00000258 fffffa80`03b74040 fffff800`00b9c510
BiosVersion = A06
BiosReleaseDate = 07/19/2010
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron N4010
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3 of them point to the NT Operating System Kernel, so those ones are virtually useless to me. Your kernel is not the culprit for this BSOD anyways.

But one of them points to the pacer.sys driver (pacer!PcFilterRequestComplete+68 )

Code:

0: kd> u pacer!PcFilterRequestComplete+68
pacer!PcFilterRequestComplete+0x68:
fffff880`02d51078 f0834564ff      lock add dword ptr [rbp+64h],0FFFFFFFFh
fffff880`02d5107d 0f846f180000    je      pacer! ?? ::FNODOBFM::`string'+0x1c2 (fffff880`02d528f2)
fffff880`02d51083 488b6c2430      mov     rbp,qword ptr [rsp+30h]
fffff880`02d51088 488b5c2438      mov     rbx,qword ptr [rsp+38h]
fffff880`02d5108d 488b742440      mov     rsi,qword ptr [rsp+40h]
fffff880`02d51092 4883c420        add     rsp,20h
fffff880`02d51096 5f              pop     rdi
fffff880`02d51097 c3              ret

I would recommend running System File Checker for starters. Open up an elevated command prompt, and type this command:

Code:

sfc /scannow

Reboot if necessary.

This was most likely caused by a bad driver here though, as param 3 on that BSOD dump indicates an execute operation and both 1 and 4 are 0x0. There's a number of causes for this, but all are related to the driver making a bad function call.

However the pacer.sys driver is a Windows driver for the Microsoft Windows QoS scheduler. Which is why i'm suggesting that you do a file integrity check.

You are ALSO not running SP1 -- Download and install Windows Service Pack 1.

Code:

0: kd> vertarget
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e50e70
Debug session time: Sat Jan 14 18:55:20.507 2012 (GMT-7)
System Uptime: 0 days 22:17:22.067

And lastly, Remove AVG, as it's also a known cause for BSOD's. Install/Replace it with Microsoft Security Essentials and you shouldn't have any apparent problems. MSE is much better anyways for security.

I did most of that(the scan which found problems and repaired, and the removal of AVG). I'm still having the same internet connection issues. "Signal Strength: Excellent" but still Limited Access(cannot connect). It is not my router as I've already tried with my phone and this laptop and it works.

---

Other details are in the Topic post.

I wasn't here to fix the internet connection issues, although that could be anything, I was here to take a look at your BSOD dump though, so hopefully that's all fixed now on the plus side.

I'm not good with networking, but if I had your computer, it's something that I can definitely solve if I have the computer hands on. That's just the way I am, i'm much better if I get to look at things myself. But that's not the case when dealing with problems over the internet.

Check your Device Manager for any errors though.