Specas Posted October 14, 2007 Share Posted October 14, 2007 need your help ty The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000008, 0x00000002, 0x00000000, 0xf6bd4220). A dump was saved in: C:\WINDOWS\Minidump\Mini101407-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000008, 0x00000002, 0x00000000, 0xf6bd4220). A dump was saved in: C:\WINDOWS\Minidump\Mini101407-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000004, 0x00000002, 0x00000001, 0xf6bd7eda). A dump was saved in: C:\WINDOWS\Minidump\Mini101307-02.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0xe06c0018, 0x00000002, 0x00000001, 0xf6bd991e). A dump was saved in: C:\WINDOWS\Minidump\Mini101307-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x30929eb6, 0x00000002, 0x00000001, 0xf6bd991e). A dump was saved in: C:\WINDOWS\Minidump\Mini101207-02.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000004, 0x00000002, 0x00000001, 0xf6bd7eda). A dump was saved in: C:\WINDOWS\Minidump\Mini101207-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00001d9d, 0x00000002, 0x00000000, 0xf6bd991c). A dump was saved in: C:\WINDOWS\Minidump\Mini101107-02.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x006b0073, 0x00000002, 0x00000000, 0xf6bd991c). A dump was saved in: C:\WINDOWS\Minidump\Mini101107-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x00000007, 0x00000cd4, 0x81e8f968, 0x8055a940). A dump was saved in: C:\WINDOWS\Minidump\Mini101007-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x000001d9, 0x00000002, 0x00000000, 0xf6bd4d5c). A dump was saved in: C:\WINDOWS\Minidump\Mini100907-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x03750363, 0x00000002, 0x00000000, 0xf6bd7057). A dump was saved in: C:\WINDOWS\Minidump\Mini100807-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000004, 0x00000002, 0x00000001, 0xf6bd7eda). A dump was saved in: C:\WINDOWS\Minidump\Mini100707-03.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000218, 0x00000002, 0x00000000, 0xf67f8d5c). A dump was saved in: C:\WINDOWS\Minidump\Mini100707-02.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000004, 0x00000002, 0x00000001, 0xf6bd7eda). A dump was saved in: C:\WINDOWS\Minidump\Mini100707-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000004, 0x00000002, 0x00000001, 0xf6653eda). A dump was saved in: C:\WINDOWS\Minidump\Mini100607-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x00000007, 0x00000cd4, 0x824475d8, 0x821a7d08). A dump was saved in: C:\WINDOWS\Minidump\Mini100507-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000004, 0x00000002, 0x00000001, 0xf662beda). A dump was saved in: C:\WINDOWS\Minidump\Mini093007-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000a18, 0x00000002, 0x00000000, 0xf669cd5c). A dump was saved in: C:\WINDOWS\Minidump\Mini092107-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00630081, 0x00000002, 0x00000001, 0xf6bd4d7d). A dump was saved in: C:\WINDOWS\Minidump\Mini092007-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00001448, 0x00000002, 0x00000000, 0xf65dd91c). A dump was saved in: C:\WINDOWS\Minidump\Mini091807-02.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x00000007, 0x00000cd4, 0x82583ab0, 0x8203c980). A dump was saved in: C:\WINDOWS\Minidump\Mini091807-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000004, 0x00000002, 0x00000001, 0xf66b0eda). A dump was saved in: C:\WINDOWS\Minidump\Mini091607-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x2134c48a, 0x00000002, 0x00000000, 0xf6bd4d5c). A dump was saved in: C:\WINDOWS\Minidump\Mini091407-01.dmp.The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000004, 0x00000002, 0x00000001, 0xf6701eda). A dump was saved in: C:\WINDOWS\Minidump\Mini090907-01.dmp. Link to comment Share on other sites More sharing options...
PC_LOAD_LETTER Posted October 14, 2007 Share Posted October 14, 2007 Those are errors are never fun really you have 3 choices:load the debugging tools and see if the minidump left any clues (thats a longshot)http://support.microsoft.com/default.aspx/kb/315263these type of errors are almost always a hardware issue. If you've recently added hardware, remove it.Have hardware in you system that has really old or uncertified drivers, try updating the drivers or removing the device (if it cant be removed but the system will function without it, disable it in the device manager)If you have you CPU or GPU overclocked, undo thatdownload a liveCD OS to test the system (ubuntu has memtest86 on the liveCD)[*]reload windows (not recommended because it is more likely to be a hardware problem) If you have an extra hard drive with at 5-10 GB space, you might remove your current drive and install a fresh(temporary) version of windows to it to see if the problem goes away Link to comment Share on other sites More sharing options...
DigeratiPrime Posted October 14, 2007 Share Posted October 14, 2007 zip up those minidump files and upload them somewhere so we can look at them.http://www.mediafire.com/http://mihd.net/ Link to comment Share on other sites More sharing options...
Specas Posted October 15, 2007 Author Share Posted October 15, 2007 zip up those minidump files and upload them somewhere so we can look at them.http://www.mediafire.com/http://mihd.net/http://www.mediafire.com/?7dbnt0j9zwt Link to comment Share on other sites More sharing options...
cluberti Posted October 15, 2007 Share Posted October 15, 2007 Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUALThe DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.In all of the dumps generated, the faulting driver causing this is nltdi.sys:// The stack of the failure always looks similar to this:kd> kbChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong.f8c3e4c4 f6bd4ded 00000000 f8c3e8b7 82489f99 nltdi+0x5220f8c3e820 f6bd51a5 f8c3e864 00000003 f8c3e920 nltdi+0x5dedf8c3e830 f6bd25e3 f8c3e864 824a7e98 81ce6bf8 nltdi+0x61a5f8c3e920 f6bfe092 82489ec4 00000016 f8c3e9a0 nltdi+0x35e3f8c3e9bc f6bfe340 824a7e98 2d963a4e 64c43a4e tcpip!FindListenConn+0x305f8c3ea60 f6be3ef5 820d2970 64c43a4e 2d963a4e tcpip!TCPRcv+0x2fff8c3eac0 f6be3b19 00000020 820d2970 f6be6076 tcpip!DeliverToUser+0x18ef8c3eb3c f6be3836 f6c233f0 820d2970 824d86da tcpip!DeliverToUserEx+0x95ef8c3ebf4 f89a4232 820d2970 824d86ee 0000001c tcpip!IPRcvPacket+0x6cbf8c3ec38 f89a42cc 0cabb1e5 824298c8 824d86cc wanarp!WanReceiveCommon+0x164f8c3ec70 f8496c9f 0cabb1e5 00000000 f7ecfb40 wanarp!WanNdisReceivePacket+0x60f8c3ecc4 f7eca01d 0066d9c8 8201d9f0 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1c2f8c3ecd8 f7eca1b4 824458c0 8201d9f0 00000001 psched!PsFlushReceiveQueue+0x15f8c3ecfc f7eca5f9 825cddc0 00000000 824458c0 psched!PsEnqueueReceivePacket+0xdaf8c3ed14 f8496d40 825cddb8 8210cdc0 81ffc888 psched!ClReceiveComplete+0x13f8c3ed64 f7ee0c59 0066d9c8 f8c3eda4 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4f8c3ed98 f7ee0f15 02ffc888 824298c8 81ffc888 ndiswan!IndicateRecvPacket+0x2aff8c3edcc f7ee13c2 81ffc888 824d8670 00000032 ndiswan!ProcessPPPFrame+0x193f8c3ede8 f7edee51 82002a08 824d8670 8260ecc8 ndiswan!ReceivePPP+0x76f8c3ee0c f84918f5 00000001 81da5644 00000032 ndiswan!ProtoWanReceiveIndication+0x106f8c3ee30 f88a0979 f8c3ee58 024b9900 00000001 NDIS!NdisMWanIndicateReceive+0x54f8c3ee68 f88a5e9d 82018d50 82018ac8 00000000 raspppoe!MpIndicateReceivedPackets+0x93f8c3ee88 804ff400 f88a8028 f88a7fe0 db258352 raspppoe!TimerEvent+0x7ff8c3efa4 804ff517 99ff4489 0000001a ffdff000 nt!KiTimerListExpire+0x122f8c3efd0 80540f7d 80552180 00000000 000b2851 nt!KiTimerExpiration+0xaff8c3eff4 80540c4a b9a54d44 00000000 00000000 nt!KiRetireDpcList+0x46f8c3eff8 b9a54d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a80540c4a 00000000 00000009 bb835675 00000128 0xb9a54d44// Looks like netlimiter's driver:kd> lmvm nltdistart end module namef6bcf000 f6be1980 nltdi T (no symbols) Loaded symbol image file: nltdi.sys Image path: nltdi.sys Image name: nltdi.sys Timestamp: Wed Sep 13 18:01:41 2006 (45087FC5) CheckSum: 000144A5 ImageSize: 00012980 Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0// The function being attempted at the time of the bugcheck// (I don't have symbols for this, obviously, so I've resorted// to unassembling the function itself to find the culprit):kd> uf nltdi+0x5220nltdi+0x5220:f6bd4220 8b4904 mov ecx,dword ptr [ecx+4] // failure is heref6bd4223 40 inc eaxf6bd4224 85c9 test ecx,ecxf6bd4226 75f8 jne nltdi+0x5220 (f6bd4220)nltdi+0x5228:f6bd4228 5d pop ebpf6bd4229 c20400 ret 4// Registers showing the failure (trying to read from address// 0x00000008, which will always cause a bugcheck):kd> reax=00000000 ebx=f8c3e864 ecx=00000004 edx=00000000 esi=81f88158 edi=00000003eip=f6bd4220 esp=f8c3e4c4 ebp=f8c3e4c4 iopl=0 nv up ei pl nz na po nccs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202nltdi+0x5220:f6bd4220 8b4904 mov ecx,dword ptr [ecx+4] ds:0023:00000008=????????// Here's why, in assembly math:ecx = 0x00000004dword ptr [ecx+4] = 0x00000008...thus...mov ecx,dword ptr [ecx+4]... is placing 0x00000008 in the ecx register, and then calling it as the read address.Thus, an attempt to read from memory address 0x00000008, which is in the first 64k of process space and any attempt to read or write from the first 64k causes an access violation. When this happens in kernel mode, the box bugchecks (as it does in your case). Link to comment Share on other sites More sharing options...
cluberti Posted October 15, 2007 Share Posted October 15, 2007 these type of errors are almost always a hardware issue.Incorrect - a stop 0xD1 is almost always a driver issue, as seen above. Link to comment Share on other sites More sharing options...
PC_LOAD_LETTER Posted October 15, 2007 Share Posted October 15, 2007 these type of errors are almost always a hardware issue.Incorrect - a stop 0xD1 is almost always a driver issue, as seen above.my bad. I was just going off the top of my head Link to comment Share on other sites More sharing options...
cluberti Posted October 15, 2007 Share Posted October 15, 2007 No problem - maybe Specas can tell us if removing / upgrading / doing something to the driver in question fixes things. Link to comment Share on other sites More sharing options...
Specas Posted October 15, 2007 Author Share Posted October 15, 2007 No problem - maybe Specas can tell us if removing / upgrading / doing something to the driver in question fixes things. removed netlimiter. now ill wait ty for your help Link to comment Share on other sites More sharing options...
cluberti Posted October 15, 2007 Share Posted October 15, 2007 Cool - keep us posted. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now