Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Win 7 BSOD error code D1


  • Please log in to reply

#1
Rafedeve

Rafedeve

    Member

  • Member
  • PipPip
  • 13 posts
Hello geeks to go!

I am getting a BSOD with error code D1 randomly during my computer usage, and the BSOD says that it has something to do with the tcipip.sys file.

After opening the .dmp file I am able to see that there are two files that are causing errors (tcipip.sys and ntoskrnl.exe). I have tried resolving the issue by inserting the Windows 7 install disk and using the repair interface to execute the chkdsk command to find and repair any corrupted or missing sectors, but this didn't resolve anything.

Attached are the .dmp files.

Thanks in advance,

Rafael

Attached Files


  • 0

Advertisements


#2
Rafedeve

Rafedeve

    Member

  • Topic Starter
  • Member
  • PipPip
  • 13 posts
As an update, I have checked my entire drive for errors again (none), run a memory test (came back 100% clean) and updated every driver on my computer but it still crashes and gives the same errors.
  • 0

#3
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program
  • 0

#4
Rafedeve

Rafedeve

    Member

  • Topic Starter
  • Member
  • PipPip
  • 13 posts
Here is the info you requested.

==================================================
Dump File : 011911-25568-01.dmp
Crash Time : 1/19/2011 3:33:50 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`01c8a7a0
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+897a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011911-25568-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,728
==================================================

==================================================
Dump File : 011911-21871-01.dmp
Crash Time : 1/19/2011 2:42:57 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`0000001c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`01c7b3ba
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+793ba
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011911-21871-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,728
==================================================

==================================================
Dump File : 011911-22729-01.dmp
Crash Time : 1/19/2011 2:31:01 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`0000001c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`01c793ba
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+793ba
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011911-22729-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,728
==================================================

==================================================
Dump File : 011911-35209-01.dmp
Crash Time : 1/19/2011 1:27:23 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`01a897a0
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+897a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011911-35209-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,728
==================================================

==================================================
Dump File : 011911-37643-01.dmp
Crash Time : 1/19/2011 12:29:16 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`0000001c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`01a7a3ba
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+793ba
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011911-37643-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,672
==================================================

==================================================
Dump File : 011911-29437-01.dmp
Crash Time : 1/19/2011 12:23:10 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`0000001c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`01c793ba
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+793ba
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011911-29437-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,728
==================================================

==================================================
Dump File : 011911-31652-01.dmp
Crash Time : 1/19/2011 12:10:43 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`0000001c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`01c7b3ba
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+793ba
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011911-31652-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,728
==================================================

==================================================
Dump File : 011811-34226-01.dmp
Crash Time : 1/18/2011 10:41:18 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`0000001c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`01c7b3ba
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+793ba
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011811-34226-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,728
==================================================

==================================================
Dump File : 011711-37908-01.dmp
Crash Time : 1/17/2011 5:34:00 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`0000001c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`01c793ba
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+793ba
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011711-37908-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,728
==================================================

==================================================
Dump File : 011711-25724-01.dmp
Crash Time : 1/17/2011 11:52:09 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`01a8c7a0
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+897a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011711-25724-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,728
==================================================

==================================================
Dump File : 011711-84958-01.dmp
Crash Time : 1/17/2011 3:51:15 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`0000001c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`01a7b3ba
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+793ba
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011711-84958-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,728
==================================================

==================================================
Dump File : 011711-87079-01.dmp
Crash Time : 1/17/2011 3:35:51 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`01c8a7a0
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+897a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011711-87079-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,728
==================================================

==================================================
Dump File : 011511-48516-01.dmp
Crash Time : 1/15/2011 11:54:14 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`01c8b7a0
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+897a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\011511-48516-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 273,840
==================================================
  • 0

#5
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Just about all are the same bug check.. The description of that bug check is as follows.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article.)
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.


First order of business is to check your memory.

If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#6
Rafedeve

Rafedeve

    Member

  • Topic Starter
  • Member
  • PipPip
  • 13 posts
I did the manual memory check and was able to boot without out errors each time.
  • 0

#7
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
So you have two memory stick then?
If so then using one memory module at a time run the memtest86 program on it.
Let me know if it finds any errors on either module then.
  • 0

#8
Rafedeve

Rafedeve

    Member

  • Topic Starter
  • Member
  • PipPip
  • 13 posts
I tried to run the memtest program, but even though my computer booted from the disk successfully, I wasn't able to get it to run.

I can't figure out how to post pictures of my screens on here, but the information given on the boot screen is as follows:


Memtest86(red blinking "+" sign) v2.11
Intel Core 2 2394 MHz
L1 Cache: 32K 33710 MB/s
L2 Cache: 3072K 15643 MB/s
L3 Cache: None
Memory : 2046M 2852 MB/s |----------------------------------------------------
Chipset : Intel PM/GM45/47 (ECC : Disabled) - FSB : 265 MHz - Type DDR-II
Settings: RAM : 398 MHz (DDR797) / CAS : 6-6-6-18 / Single Channel


257M e820-Std off


The difference between these screens is the size of the memory (2GB vs 1GB), the MHz of the memory (265 vs 266) and the RAM Settings (398MHz (DDR797) vs 399MHz (DDR798)).


I tried every combination of RAM and slot and nothing helped. Thoughts?
  • 0

#9
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hmm it's beginning to look like maybe a faulty memory slot or slots.
  • 0

#10
Rafedeve

Rafedeve

    Member

  • Topic Starter
  • Member
  • PipPip
  • 13 posts
So what does that mean I should do? Should I take my laptop in to a hardware technician if the issue becomes extremely infuriating? Should I not even bother and just go ahead and purchase a new computer?

What do you recommend as my next steps?
  • 0

Advertisements


#11
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Let me ask you. When you did the manual test did you have just one memory module in the first slot when you tested each module?
Have you tried to see if it will boot with the one module in the second slot?
  • 0

#12
Rafedeve

Rafedeve

    Member

  • Topic Starter
  • Member
  • PipPip
  • 13 posts
I was unsure so I just ran the manual check again and it was able to boot up with either RAM in either slot.
  • 0

#13
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
wow strange for sure.
OK lets try something here.
Put both modules in and boot to Safe Mode.
Does the BSOD happen then?
  • 0

#14
Rafedeve

Rafedeve

    Member

  • Topic Starter
  • Member
  • PipPip
  • 13 posts
I booted to safe mode and it was successful with no BSOD.

To clarify though, I receive the BSOD at random times during regular use, so I don't know if the BSOD might happen during safe mode after some use.

Thanks for all of your help so far by the way.
  • 0

#15
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK then try rebooting and go into Safe Mode With Networking
This will allow you to get online and hopefully post that way. If it does not egt a BSOD in Safe Mode then we will have to look at a driver as being the issue.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP