- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Community.
After upgrade drivers and firmware for AC 3160 Wireless card, I've receive many BSOD on Windows 7 x64
Upgrade package used: Wireless_19.70.0_PROSet64_Win7.exe
Please find below the DUMP analysis.
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Machine Name:
Kernel base = 0xfffff800`03817000 PsLoadedModuleList = 0xfffff800`03a59750
Debug session time: Mon Jul 24 00:14:55.101 2017 (UTC - 4:00)
System Uptime: 0 days 4:55:20.944
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 00000000041d0006, Memory contents of the pool block
Arg4: fffffa800e3e0c10, Address of the block of pool being deallocated
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
POOL_ADDRESS: fffffa800e3e0c10 Nonpaged pool
FREED_POOL_TAG: NDdb
BUGCHECK_STR: 0xc2_7_NDdb
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800039bdbf9 to fffff80003887e40
STACK_TEXT:
fffff880`03259a38 fffff800`039bdbf9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`041d0006 : nt!KeBugCheckEx
fffff880`03259a40 fffff800`03e01865 : fffffa80`078d9920 00000000`00000c5c 00000000`00000000 fffffa80`0c338300 : nt!ExFreePool+0xcb1
fffff880`03259af0 fffff880`014a86c1 : fffffa80`0708ecd0 fffff880`03259c69 fffffa80`0e3e0c40 fffff880`03259c69 : hal!HalPutScatterGatherList+0x115
fffff880`03259b50 fffff880`06e5c1f1 : fffffa80`00000002 fffffa80`0e3e0c40 00000000`00000002 01d30433`678cf2e3 : ndis!NdisMFreeNetBufferSGList+0x31
fffff880`03259b90 fffffa80`00000002 : fffffa80`0e3e0c40 00000000`00000002 01d30433`678cf2e3 fffffa80`0aba5850 : Netwsw02+0x331f1
fffff880`03259b98 fffffa80`0e3e0c40 : 00000000`00000002 01d30433`678cf2e3 fffffa80`0aba5850 fffff880`06ff9289 : 0xfffffa80`00000002
fffff880`03259ba0 00000000`00000002 : 01d30433`678cf2e3 fffffa80`0aba5850 fffff880`06ff9289 fffffa80`0aba5850 : 0xfffffa80`0e3e0c40
fffff880`03259ba8 01d30433`678cf2e3 : fffffa80`0aba5850 fffff880`06ff9289 fffffa80`0aba5850 fffff880`03259c69 : 0x2
fffff880`03259bb0 fffffa80`0aba5850 : fffff880`06ff9289 fffffa80`0aba5850 fffff880`03259c69 fffffa80`0862ca01 : 0x1d30433`678cf2e3
fffff880`03259bb8 fffff880`06ff9289 : fffffa80`0aba5850 fffff880`03259c69 fffffa80`0862ca01 01d30433`678cf2e3 : 0xfffffa80`0aba5850
fffff880`03259bc0 fffffa80`0aba5850 : fffff880`03259c69 fffffa80`0862ca01 01d30433`678cf2e3 00000000`00000001 : Netwsw02+0x1d0289
fffff880`03259bc8 fffff880`03259c69 : fffffa80`0862ca01 01d30433`678cf2e3 00000000`00000001 fffff880`06f9c690 : 0xfffffa80`0aba5850
fffff880`03259bd0 fffffa80`0862ca01 : 01d30433`678cf2e3 00000000`00000001 fffff880`06f9c690 00000000`00000000 : 0xfffff880`03259c69
fffff880`03259bd8 01d30433`678cf2e3 : 00000000`00000001 fffff880`06f9c690 00000000`00000000 fffff880`06f9ca70 : 0xfffffa80`0862ca01
fffff880`03259be0 00000000`00000001 : fffff880`06f9c690 00000000`00000000 fffff880`06f9ca70 ffffffff`00000000 : 0x1d30433`678cf2e3
fffff880`03259be8 fffff880`06f9c690 : 00000000`00000000 fffff880`06f9ca70 ffffffff`00000000 00000000`00000001 : 0x1
fffff880`03259bf0 00000000`00000000 : fffff880`06f9ca70 ffffffff`00000000 00000000`00000001 fffffa80`0861e770 : Netwsw02+0x173690
STACK_COMMAND: kb
FOLLOWUP_IP:
Netwsw02+331f1
fffff880`06e5c1f1 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: Netwsw02+331f1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Netwsw02
IMAGE_NAME: Netwsw02.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 58e5265d
FAILURE_BUCKET_ID: X64_0xc2_7_NDdb_Netwsw02+331f1
BUCKET_ID: X64_0xc2_7_NDdb_Netwsw02+331f1
Followup: MachineOwner
---------
Any assistance will be very appreciated.
Regards,
Murray
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Murray1978,
We understand your system is showing BSOD's after some system updates. This can happen for different reasons, as first step, we recommend to perform a clean installation of the wireless driver:
1. As first option, we advise to use the driver obtained from the https://www.intel.com/content/www/us/en/support/topics/OEMs.html Computer Manufacturer Support, if the issue persists you can try the generic version of https://downloadcenter.intel.com/download/26929/Wireless-Intel-PROSet-Wireless-Software-and-Drivers-for-Windows-7-?product=75442 Intel® PROSet/Wireless Software and Drivers for Windows® 10 [19.70.0]
2. Go to Control Panel, Programs and Features and Uninstall "Intel® PROSet/Wireless Software", if it is installed. When prompted, choose the option to "Discard settings".
3. In Control Panel, Device Manager, Network Adapters, right click on the Intel® Dual Band Wireless-AC 3160 and Uninstall it. Make sure you mark the option to "Delete the driver software for this device".
4. Reboot the PC or scan for hardware changes, check device manager and if an older wireless driver is detected and installed, repeat the actions to uninstall and delete it as well. Repeat this process until the OS does not allow deleting the driver, or until the controller shows as Unknown Device.
5. Remove temporary files: Press the Windows Key + R to open the run box. Type Cleanmgr.exe. Press OK. Select the main drive, usually C:\. Check Temporary Files and uncheck everything else. Press OK.
6. Install the Intel Wireless driver. During the first steps of PROSet/Wireless installation, make sure to customize the installation and install all driver components.
Additionally, make sure your OS has all applicable Windows* updates.
Regards,
Regards,
Jonathan B.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Murray1978,
Please let us know if there has been any progress, or in case require further assistance.
Regards,
Jonathan B.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page