Solved Windows BSOD 0xC2 ndis.sys

[Hexagon12]

Hi all,

When i have shutdowned the computer, the BSOD has showed.
It says:
BAD_POOL_CALLER



0x000000C2
ndis.sys
What is the problem here? NDIS is something with the network, I guess?

Sorry for my bad english( i am from lithuania.)

My computer specs:
Hp Compaq 6000 SFF PC
Intel Q45/Q43 Graphics Chipset
D-Link DWA-125 Wi-fi adapter
4GB RAM
Sorry, this is my first post
Here's the minidump:

 

[Arc]

Hi Hexagon12. It is better you supply some more info which will give us a better view about what is going on.

Click on the button below ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[Hexagon12]

Here's the zip file.

 

[essenbe]

This is all I can get from your dump file

lmvm ndis
start             end                 module name
fffff880`01618000 fffff880`0170a000   ndis       (pdb symbols)          c:\symcache\ndis.pdb\7F2704456B8949D6BD0D97D90F00DB912\ndis.pdb
    Loaded symbol image file: ndis.sys
    Mapped memory image file: c:\symcache\ndis.sys\5034F6B2f2000\ndis.sys
    Image path: \SystemRoot\system32\drivers\ndis.sys
    Image name: ndis.sys
    Timestamp:        Wed Aug 22 10:11:46 2012 (5034F6B2)
    CheckSum:         000E8B11
    ImageSize:        000F2000
    File version:     6.1.7601.17939
    Product version:  6.1.7601.17939
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     [COLOR=red]NDIS.SYS[/COLOR]
    OriginalFilename: NDIS.SYS
    ProductVersion:   6.1.7601.17939
    FileVersion:      6.1.7601.17939 (win7sp1_gdr.120822-0331)
    FileDescription:  NDIS 6.20 driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

This is a Microsoft system file and is not likely to be the real cause. If you would, please run all the Windows Updates Then open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[Hexagon12]

Ok. Back with the results.
I checked Windows Update. No updates.

Microsoft Windows [Version 6.1.7601]
(c) Microsoft Corporation, 2009. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log

BTW, you don't have to say the instructions. I am computer pro. I often go to VMware Workstation, VBox or Virtual PC 2007 to do some VM'ing

 

[essenbe]

Run it again to be sure and see if you can get a result of no integrity violations. Have you had any BSODs since you ran it?

 

[Hexagon12]

I had one time when i booted my computer. But it like flashed away. Checked Minidump folder. No Minidump of that BSOD. I think it was 0x50.

YES!!!!!


Microsoft Windows [Version 6.1.7601]
(c) Microsoft Corporation, 2009. Visos teisės ginamos.

C:\Users\NAMAI>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Users\NAMAI>

 

[essenbe]

Let's see if it is any better now. If you get a BSOD attach the file again. Those looked like a lot of errors.