Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD randomly occuring with error 0x000000d1

04 Sep 2012   #1

Windows 7 Professional x64
 
 
BSOD randomly occuring with error 0x000000d1

After moving into a new apartment a few days ago I seem to be randomly getting a BSOD every few hours. The only change I can think of is that I am now using a Linksys SE1500 switch instead of a wireless connection, I attached the needed files but have no idea what the issue might be.

Thanks for your time!


My System SpecsSystem Spec
.

05 Sep 2012   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome

BSOD Analyse

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa800b3fc000, 2, 0, fffff880016c8fe7}

Probably caused by : tcpip.sys ( tcpip!Ipv6AddressType+27 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa800b3fc000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880016c8fe7, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003ec4100
 fffffa800b3fc000 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!Ipv6AddressType+27
fffff880`016c8fe7 664439410a      cmp     word ptr [rcx+0Ah],r8w

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  cmdagent.exe

TRAP_FRAME:  fffff88002f21770 -- (.trap 0xfffff88002f21770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000c0fe rbx=0000000000000000 rcx=fffffa800b3fbff6
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016c8fe7 rsp=fffff88002f21900 rbp=fffffa80066bcc90
 r8=000000000000fe5e  r9=fffffa800b3fbff6 r10=0000000000000010
r11=fffff88002f21aa8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
tcpip!Ipv6AddressType+0x27:
fffff880`016c8fe7 664439410a      cmp     word ptr [rcx+0Ah],r8w ds:6160:fffffa80`0b3fc000=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003c94769 to fffff80003c951c0

STACK_TEXT:  
fffff880`02f21628 fffff800`03c94769 : 00000000`0000000a fffffa80`0b3fc000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f21630 fffff800`03c933e0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`04921b40 : nt!KiBugCheckDispatch+0x69
fffff880`02f21770 fffff880`016c8fe7 : 00000000`00000000 00000000`00000000 fffff880`017b7800 fffffa80`066bcc90 : nt!KiPageFault+0x260
fffff880`02f21900 fffff880`0166ea6c : fffff880`02f21ba0 fffffa80`066bcc90 fffff880`017b7800 00000000`00000000 : tcpip!Ipv6AddressType+0x27
fffff880`02f21930 fffff880`016582b1 : 00000000`000012ca fffff880`0178a214 00000000`004f1a00 00000000`00000000 : tcpip!IppValidateSetAllRouteParameters+0x8c
fffff880`02f21a30 fffff880`01661c52 : fffffa80`04921b40 fffffa80`04b77150 fffffa80`066bcc90 fffffa80`056c6160 : tcpip!IppUpdateUnicastRouteUnderLock+0x81
fffff880`02f21ab0 fffff880`0176640c : fffffa80`068fb900 fffffa80`0b3fbf4e fffffa80`0b3fbff6 00000000`ffffffff : tcpip!IppUpdateUnicastRoute+0xb2
fffff880`02f21b50 fffff880`0178cd99 : fffffa80`0b3f0080 00000000`00000e10 fffffa80`066bcc90 fffffa80`06901a40 : tcpip!IppUpdateAutoConfiguredRoute+0xac
fffff880`02f21bd0 fffff880`0178d43f : fffffa80`04a04000 fffffa80`068bd170 00000000`00000086 00000000`00000000 : tcpip!Ipv6pHandleRouterAdvertisement+0x6a9
fffff880`02f21d30 fffff880`016a398e : fffffa80`066beba0 00000000`00000000 fffff880`017b7800 00000000`0000ffff : tcpip!Icmpv6ReceiveDatagrams+0x34f
fffff880`02f21dd0 fffff880`016a349a : 00000000`00000000 00000000`00000000 fffff880`017b7800 fffffa80`06901910 : tcpip!IppDeliverListToProtocol+0xfe
fffff880`02f21e90 fffff880`016a2a99 : fffffa80`04a04000 00000000`00000000 fffff880`02f21f00 fffff880`02f21f80 : tcpip!IppProcessDeliverList+0x5a
fffff880`02f21f30 fffff880`016a07ff : 00000000`00000000 00000000`066beb01 fffff880`017b7800 fffff880`017b7800 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`02f22010 fffff880`0169fdf2 : fffffa80`056c6160 00000000`00000000 fffffa80`066beb01 fffffa80`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`02f22210 fffff880`0169f28a : fffffa80`066beba0 fffff880`02f22340 fffffa80`066beba0 fffffa80`04780001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`02f222f0 fffff800`03ca0e48 : fffffa80`06901910 00000000`00004800 fffffa80`046d5060 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`02f22340 fffff880`0169f952 : fffff880`0169f1b0 00000000`00000201 fffffa80`0a500a02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`02f22420 fffff880`015b10eb : fffffa80`066c08d0 00000000`00000000 fffffa80`0588b1a0 fffffa80`0588b1a0 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`02f22490 fffff880`0157aad6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`02f22500 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!Ipv6AddressType+27
fffff880`016c8fe7 664439410a      cmp     word ptr [rcx+0Ah],r8w

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tcpip!Ipv6AddressType+27

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f757012

FAILURE_BUCKET_ID:  X64_0xD1_tcpip!Ipv6AddressType+27

BUCKET_ID:  X64_0xD1_tcpip!Ipv6AddressType+27

Followup: MachineOwner
---------

1: kd> lmvm tcpip
start             end                 module name
fffff880`0164c000 fffff880`0184f000   tcpip      (pdb symbols)          c:\symbols\tcpip.pdb\DBCCEC823BEB4616BE270138781E51122\tcpip.pdb
    Loaded symbol image file: tcpip.sys
    Mapped memory image file: c:\symbols\tcpip.sys\4F757012203000\tcpip.sys
    Image path: \SystemRoot\System32\drivers\tcpip.sys
    Image name: tcpip.sys
    Timestamp:        Fri Mar 30 14:34:26 2012 (4F757012)
    CheckSum:         001D8A32
    ImageSize:        00203000
    File version:     6.1.7601.17802
    Product version:  6.1.7601.17802
    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:     tcpip.sys
    OriginalFilename: tcpip.sys
    ProductVersion:   6.1.7601.17802
    FileVersion:      6.1.7601.17802 (win7sp1_gdr.120329-2050)
    FileDescription:  TCP/IP Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
BSOD Index STOP 0x100000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Do the following:
TCpip.sys= network related. Driver Reference Table

Next, pay attention to upgrade the network driver.

1] download the network card driver from manufactuer's website.
2] Then reinstall the driver:
3] Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
4] Double click to expand "Network adaptors".
5] Right click your network card and click Uninstall.
6] Check "Delete driver software for this device" check box, click OK.
7] Restart the computer

If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

Post back
My System SpecsSystem Spec
05 Sep 2012   #3

Windows 7 Professional x64
 
 

Drivers are up to date, hopefully there aren't any more issues.

Thanks again!
My System SpecsSystem Spec
.


05 Sep 2012   #4

Windows 7 Professional x64
 
 

Well, that didn't last long.
Just got another BSOD with the same error.
My System SpecsSystem Spec
05 Sep 2012   #5

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Shows the same cause

Lets run driver verifier to rule out buggy drivers
Driver Verifier - Enable and Disable
My System SpecsSystem Spec
05 Sep 2012   #6

Windows 7 Professional x64
 
 

My computer was running a bit slow (I assume because of the driver verifier?) but otherwise no had no problems until I shut down my computer for the night at which point I got another BSOD, with a different error message:

Edit - shut down again, crashed with same error, then got a different error on restart, started in safe mode with networking to get the needed files successfully and disabled driver verifier for now. Only the most recent files are attached.
My System SpecsSystem Spec
05 Sep 2012   #7

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

gdrv.sys

Gigabyte Easy Saver - mobo power utility driver

GIGABYTE - Motherboard, Graphics Card, Notebook, Slate, Server, PC Peripherals and more
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff98062b46ff0, fffff98062b46ffc, 75000c, 24}

Unable to load image \??\C:\Windows\gdrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+30c7 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff98062b46ff0, address trying to free
Arg2: fffff98062b46ffc, address where bits are corrupted
Arg3: 000000000075000c, (reserved)
Arg4: 0000000000000024, caller is freeing an address where bytes after the end of the allocation have been overwritten

Debugging Details:
------------------


BUGCHECK_STR:  0xC1_24

SPECIAL_POOL_CORRUPTION_TYPE:  24

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  essvr.exe

CURRENT_IRQL:  1

IRP_ADDRESS:  fffff9804dc50f3b

LAST_CONTROL_TRANSFER:  from fffff80003dda144 to fffff80003cdb1c0

STACK_TEXT:  
fffff880`088964d8 fffff800`03dda144 : 00000000`000000c1 fffff980`62b46ff0 fffff980`62b46ffc 00000000`0075000c : nt!KeBugCheckEx
fffff880`088964e0 fffff800`03e0593b : fffff800`03c5c000 00000000`20206f49 ffffffff`ffbdfef7 fffffa80`077ec800 : nt!MmFreeSpecialPool+0x374
fffff880`08896620 fffff800`03cefade : 00000000`00000000 fffff980`4dc50fb0 fffff980`01650ce0 fffffa80`07b50010 : nt!ExDeferredFreePool+0xf33
fffff880`088966d0 fffff800`03cdeeea : fffff980`4dc50fb3 00000000`00000001 00000000`00000001 fffff800`03d94df3 : nt!IopCompleteRequest+0x5ce
fffff880`088967a0 fffff800`0417719f : fffff980`4dc50ee0 fffffa80`0812c000 fffff980`4dc50f00 00000000`00000000 : nt!IopfCompleteRequest+0x66a
fffff880`08896890 fffff880`09ac20c7 : fffff880`09ac2a50 00000000`00000008 00000000`00000000 fffff980`4dc50fb0 : nt!IovCompleteRequest+0x19f
fffff880`08896960 fffff880`09ac2a50 : 00000000`00000008 00000000`00000000 fffff980`4dc50fb0 00000000`00000001 : gdrv+0x30c7
fffff880`08896968 00000000`00000008 : 00000000`00000000 fffff980`4dc50fb0 00000000`00000001 00000000`00000000 : gdrv+0x3a50
fffff880`08896970 00000000`00000000 : fffff980`4dc50fb0 00000000`00000001 00000000`00000000 00000000`00000001 : 0x8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
gdrv+30c7
fffff880`09ac20c7 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  gdrv+30c7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: gdrv

IMAGE_NAME:  gdrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49b9d175

FAILURE_BUCKET_ID:  X64_0xC1_24_VRF_gdrv+30c7

BUCKET_ID:  X64_0xC1_24_VRF_gdrv+30c7

Followup: MachineOwner
---------

0: kd> lmvm gdrv
start             end                 module name
fffff880`09abf000 fffff880`09ac8000   gdrv     T (no symbols)           
    Loaded symbol image file: gdrv.sys
    Image path: \??\C:\Windows\gdrv.sys
    Image name: gdrv.sys
    Timestamp:        Fri Mar 13 09:22:29 2009 (49B9D175)
    CheckSum:         000105CE
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Go to the manufacturers website and get an update for the above driver
My System SpecsSystem Spec
06 Sep 2012   #8

Windows 7 Professional x64
 
 

Alright, updated that, should I have the driver verifier running still?
My System SpecsSystem Spec
07 Sep 2012   #9

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Are you getting any BSOD?
My System SpecsSystem Spec
07 Sep 2012   #10

Windows 7 Professional x64
 
 

Just got another BSOD
My System SpecsSystem Spec
Reply

 BSOD randomly occuring with error 0x000000d1




Thread Tools



Similar help and support threads for2: BSOD randomly occuring with error 0x000000d1
Thread Forum
BSOD randomly occuring after +/- 40 to 45 minutes. Error 0x00000109 BSOD Help and Support
Solved BSOD playing games and randomly at idle error 0x000000d1 mostly BSOD Help and Support
Solved BSOD recurring randomly, error 0x000000d1 BSOD Help and Support
BSOD randomly, error 0x000000d1 BSOD Help and Support
BSOD randomly each half a hour, error 0x000000d1 BSOD Help and Support
BSOD occuring randomly error 0x000124 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 06:00 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33