Share via

0x000000D1 ndis.sys

Anonymous
2013-09-24T04:02:50+00:00

I am running a Windows 7 x86 VM on VMware Workstation 9 running on Windows 8 x64.

I did a P2V on the Windows 7 x86 when I received the laptop from my company and I put my own HDD in the company laptop and am running the company image(Win7x86) on a VM.

When I initially did the P2V I had a lot of issues but ended up getting it working.

I have intermittently been having BSOD issues.

I am getting a BSOD with 0x000000D1 ndis.sys and am not sure what it means or what I should do.

Here is a screen shot: https://skydrive.live.com/redir?resid=227FA60180F17BE4!488&authkey=!ABJLC3ZlWyw-8pY&v=3

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2013-09-24T18:58:57+00:00

    Hi,

    All of the attached DMP files are of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bugcheck.

    This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

    A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

    MODULE_NAME: teefer2

    IMAGE_NAME:  teefer2.sys

    FAILURE_BUCKET_ID:  0xD1_teefer2+24ec

    Probably caused by : teefer2.sys ( teefer2+24ec )

    teefer2.sys = Symantec Endpoint Protection 11 firewall.

    Remove and replace Norton with Microsoft Security Essentials for temporary troubleshooting purposes:

    Norton removal tool -https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

    MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments

5 additional answers

Sort by: Most helpful
  1. Anonymous
    2013-09-24T12:36:12+00:00

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-09-24T12:24:22+00:00

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-09-24T04:23:33+00:00

    Hi,

    As JMH said, once we have the crash dumps we will be able to properly evaluate your crashes.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-09-24T04:16:43+00:00

    We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.


    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.


    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont know what it is you probably are not overclocking.

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    If you are overclocking stop.  (chances are if you dont know if you are, you are not)

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.

    * Zip up the copy (compress them)

    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.

    Link for how to  upload below.

    http://www.wikihow.com/Use-SkyDrive

    To ensure minidumps are enabled:

    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.

    * Under the Advanced tab, click on the Startup and Recovery Settings... button.

    * Ensure that Automatically restart is unchecked.

    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).

    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.

    * OK your way out.

    * Reboot if changes have been made.

    Please also run MSinfo32 and upload the output as well.

    To run MSinfo32 please go to start>run>MSinfo32

    Go to "file" "save" and upload the saved file with the DMPS

    System specs are extremely useful so please include whatever you know.


    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...


    Basic troubleshooting WIndows/hardware here

    You can read more about BSODS here

    You can learn how to test your memory here

    Asking an effective question gets help faster read how here



    Team Zigzag3143.com

    Was this answer helpful?

    0 comments No comments