The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    BSOD cause by Intel 5300

    Discussion in 'Networking and Wireless' started by dazz87, May 9, 2010.

  1. dazz87

    dazz87 Notebook Evangelist

    Reputations:
    38
    Messages:
    378
    Likes Received:
    0
    Trophy Points:
    30
    Hi, I recently got several BSOD and the cause is from my Intel 5300. BSOD will happen when I am in the middle of downloading a file. I am running windows 7 Pro 32bit on my dell xps. I updated to the latest drivers from intel v13.1.1.1 and I am still getting it. BSOD seems to be happen couple of days apart. I did a search and it apparently other people are having the same issue but no one seems to have a solution. My card is not a ES. Anyone having an issues with their 5300?

    Is what I get from Who Crashed:

    On Sat 5/8/2010 5:00:55 AM your computer crashed
    This was likely caused by the following module: netw5s32.sys
    Bugcheck code: 0xC2 (0x7, 0x1097, 0x80A0004, 0x84A1A160)
    Error: BAD_POOL_CALLER
    Dump file: C:\Windows\Minidump\050810-6458-01.dmp
    file path: C:\Windows\system32\drivers\netw5s32.sys
    product: Intel® Wireless WiFi Link Adapter
    company: Intel Corporation
    description: Intel® Wireless WiFi Link Driver
     
    dazz87, May 9, 2010
    #1
  2. gerryf19

    gerryf19 I am the walrus

    Reputations:
    2,275
    Messages:
    3,990
    Likes Received:
    0
    Trophy Points:
    105
    Completely remove the intel wireless drivers. Connect your laptop via cable, visit windows update, get Windows 7 certified drivers. I do not think those that you have are whql.

    I agree though, it is likely your driver.
     
    gerryf19, May 12, 2010
    #2