I've replaced my MB and I'm still getting bugcheck 0x100000d1...help!

[insaneoctane]

After building a system and testing for around a month, I finally gave up on the components and replaced my motherboard with a new ASUS P5K. Well, I'm still getting BSOD, followed by a reboot. This seems to only happen (so far) during burn-in testing in ORTHOS. I could really use some help with identifying where to look for these errors. I've run many, many hours of memtest86+ at current settings as well as at higher clock speeds and lower timings and it runs for hours clean, so I don't suspect my ram...but anything is possible. I've tried running my new SATA 500GB as both ACHI and legacy IDE mode, BSOD ensues either way. The system is barebones with JUST the OS and the basic drivers that came with the motherboard. The new MB I've gone to is a new chipshet board (P35), so I'm amazed that I'm still getting BSOD. If you look at the attached picture, there are some issues with the LAN a few hours before the reboot? Anyway, thanks in advance for the help.

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 6/15/2007
Time: 1:35:49 AM
User: N/A
Computer: ADAM-C2D
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000008, 0x00000002, 0x00000000, 0xba606c00). A dump was saved in: C:\WINDOWS\Minidump\Mini061507-01.dmp.

 

[insaneoctane]

I'm running dumpchk and it tells me this:

Unable to load image NDIS.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NDIS.sys
Unable to load image atl01_xp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atl01_xp.sys
*** ERROR: Module load completed but symbols could not be loaded for atl01_xp.sys

Does that mean I've got corrupt copies of NDIS.sys? It appears to be the mem address releated???

icrosoft (R) Windows Debugger Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini061507-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Jun 15 23:41:12.703 2007 (GMT-7)
System Uptime: 0 days 9:52:17.295
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.................................................................................................................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image NDIS.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NDIS.sys
Unable to load image atl01_xp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atl01_xp.sys
*** ERROR: Module load completed but symbols could not be loaded for atl01_xp.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {8, 2, 0, ba606c00}

Probably caused by : atl01_xp.sys ( atl01_xp+4593 )

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

 

[insaneoctane]

Okay, so I figured how install the symbols...
now I need help translating the debug info.
The bugcheck analysis that the dumpchk gives is that it is probably caused by "atl01_xp.sys", but if you look at the memory location of the bugcheck info it points to the NDIS module...so, anyone with any experience want to shed some light here????

Thanks.
PS- here's my bugcheck analysis:

Microsoft (R) Windows Debugger Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\WINDOWS\Minidump\Mini061507-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Jun 15 23:41:12.703 2007 (GMT-7)
System Uptime: 0 days 9:52:17.295
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.................................................................................................................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image NDIS.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NDIS.sys
Unable to load image atl01_xp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atl01_xp.sys
*** ERROR: Module load completed but symbols could not be loaded for atl01_xp.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {8, 2, 0, ba606c00}

Probably caused by : atl01_xp.sys ( atl01_xp+4593 )

Followup: MachineOwner
....
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Jun 15 23:41:12.703 2007 (GMT-7)
System Uptime: 0 days 9:52:17.295
start end module name
...
...
b9d9b000 b9dcb100 rdpdr Tue Aug 03 23:01:10 2004 (41107BA6)
b9dcc000 b9ddce00 psched Tue Aug 03 23:04:16 2004 (41107C60)
b9ddd000 b9df3680 ndiswan Tue Aug 03 23:14:30 2004 (41107EC6)
b9df4000 b9e0ee00 dne2000 Wed Jun 29 19:42:24 2005 (42C35C10)
b9eaf000 b9ed1680 ks Tue Aug 03 23:15:20 2004 (41107EF8)
b9ed2000 b9ef4e80 USBPORT Tue Aug 03 23:08:34 2004 (41107D62)
b9ef5000 b9f08780 VIDEOPRT Tue Aug 03 23:07:04 2004 (41107D08)
b9f09000 ba5764e0 nv4_mini Fri Apr 20 06:37:06 2007 (4628C202)
ba5aa000 ba5ac280 rasacd Fri Aug 17 13:55:39 2001 (3B7D84CB)
ba5d6000 ba5f0580 Mup Tue Aug 03 23:15:20 2004 (41107EF8)
ba5f1000 ba61da80 NDIS Tue Aug 03 23:14:27 2004 (41107EC3)
ba61e000 ba6aa480 Ntfs Tue Aug 03 23:15:06 2004 (41107EEA)
ba6ab000 ba6c1780 KSecDD Tue Aug 03 22:59:45 2004 (41107B51)
ba6c2000 ba6d3f00 sr Tue Aug 03 23:06:22 2004 (41107CDE)
ba6d4000 ba6f2780 fltMgr Tue Aug 03 23:01:17 2004 (41107BAD)
ba6f3000 ba70a800 SCSIPORT Tue Aug 03 22:59:39 2004 (41107B4B)
ba70b000 ba722480 atapi Tue Aug 03 22:59:41 2004 (41107B4D)
ba723000 ba748700 dmio Tue Aug 03 23:07:13 2004 (41107D11)
ba749000 ba767880 ftdisk Fri Aug 17 13:52:41 2001 (3B7D8419)
ba768000 ba778a80 pci Tue Aug 03 23:07:45 2004 (41107D31)
ba779000 ba7a6d80 ACPI Tue Aug 03 23:07:35 2004 (41107D27)
ba8a8000 ba8b0c00 isapnp Fri Aug 17 13:58:01 2001 (3B7D8559)
ba8b8000 ba8c6e80 ohci1394 Tue Aug 03 23:10:05 2004 (41107DBD)
ba8c8000 ba8d5000 1394BUS Tue Aug 03 23:10:03 2004 (41107DBB)
ba8d8000 ba8e2500 MountMgr Tue Aug 03 22:58:29 2004 (41107B05)
ba8e8000 ba8f4c80 VolSnap Tue Aug 03 23:00:14 2004 (41107B6E)
ba8f8000 ba903480 jraid Fri Mar 23 19:20:24 2007 (460498F8)
ba908000 ba910e00 disk Tue Aug 03 22:59:53 2004 (41107B59)
ba918000 ba924200 CLASSPNP Tue Aug 03 23:14:26 2004 (41107EC2)
ba988000 ba996d80 arp1394 Tue Aug 03 22:58:28 2004 (41107B04)
ba9c8000 ba9d0d00 intelppm Tue Aug 03 22:59:19 2004 (41107B37)
ba9d8000 ba9e2380 imapi Tue Aug 03 23:00:12 2004 (41107B6C)
ba9e8000 ba9f4180 cdrom Tue Aug 03 22:59:52 2004 (41107B58)
ba9f8000 baa06080 redbook Tue Aug 03 22:59:34 2004 (41107B46)
baa08000 baa11700 atl01_xp Wed Mar 14 22:12:02 2007 (45F8E3B2)
baa18000 baa27180 nic1394 Tue Aug 03 22:58:28 2004 (41107B04)
baa28000 baa37d80 serial Tue Aug 03 23:15:51 2004 (41107F17)
baa38000 baa44e00 i8042prt Tue Aug 03 23:14:36 2004 (41107ECC)
baa48000 baa54880 rasl2tp Tue Aug 03 23:14:21 2004 (41107EBD)
baa58000 baa62200 raspppoe Tue Aug 03 23:05:06 2004 (41107C92)
baa68000 baa73d00 raspptp Tue Aug 03 23:14:26 2004 (41107EC2)
baa78000 baa80900 msgpc Tue Aug 03 23:04:11 2004 (41107C5B)
baa88000 baa91f00 termdd Tue Aug 03 22:58:52 2004 (41107B1C)
baa98000 baaa1480 NDProxy Fri Aug 17 13:55:30 2001 (3B7D84C2)
baab8000 baac6100 usbhub Tue Aug 03 23:08:40 2004 (41107D68)
baad8000 baae0700 netbios Tue Aug 03 23:03:19 2004 (41107C27)
baae8000 baaf0880 Fips Fri Aug 17 18:31:49 2001 (3B7DC585)
bab08000 bab10d80 HIDCLASS Tue Aug 03 23:08:18 2004 (41107D52)
bab18000 bab20700 wanarp Tue Aug 03 23:04:57 2004 (41107C89)
bab28000 bab2e200 PCIIDEX Tue Aug 03 22:59:40 2004 (41107B4C)
bab30000 bab34900 PartMgr Fri Aug 17 18:32:23 2001 (3B7DC5A7)
bab90000 bab95000 usbuhci Tue Aug 03 23:08:34 2004 (41107D62)
bab98000 bab9e800 usbehci Tue Aug 03 23:08:34 2004 (41107D62)
baba0000 baba6000 kbdclass Tue Aug 03 22:58:32 2004 (41107B08)
baba8000 babac880 TDI Tue Aug 03 23:07:47 2004 (41107D33)
babb0000 babb4580 ptilink Fri Aug 17 13:49:53 2001 (3B7D8371)
babb8000 babbc080 raspti Fri Aug 17 13:55:32 2001 (3B7D84C4)
babc0000 babc5a00 mouclass Tue Aug 03 22:58:32 2004 (41107B08)
babe8000 babed200 vga Tue Aug 03 23:07:06 2004 (41107D0A)
babf0000 babf4a80 Msfs Tue Aug 03 23:00:37 2004 (41107B85)
babf8000 babff880 Npfs Tue Aug 03 23:00:38 2004 (41107B86)
bac08000 bac0fb80 usbccgp Tue Aug 03 23:08:45 2004 (41107D6D)
bac10000 bac16180 HIDPARSE Tue Aug 03 23:08:15 2004 (41107D4F)
bac18000 bac1e780 USBSTOR Tue Aug 03 23:08:44 2004 (41107D6C)
bac20000 bac24500 watchdog Tue Aug 03 23:07:32 2004 (41107D24)
bac38000 bac40000 kerneld Thu Dec 14 14:42:15 2006 (4581D347)
bacb8000 bacbb000 BOOTVID Fri Aug 17 13:49:09 2001 (3B7D8345)
bad48000 bad4bc80 serenum Tue Aug 03 22:59:06 2004 (41107B2A)
bad50000 bad52580 ndistapi Fri Aug 17 13:55:29 2001 (3B7D84C1)
bad68000 bad6bc80 mssmbios Tue Aug 03 23:07:47 2004 (41107D33)
bada8000 bada9b80 kdcom Fri Aug 17 13:49:10 2001 (3B7D8346)
badaa000 badab100 WMILIB Fri Aug 17 14:07:23 2001 (3B7D878B)
badac000 badad700 dmload Fri Aug 17 13:58:15 2001 (3B7D8567)
badae000 badaf480 speedfan Sun Sep 24 06:28:47 2006 (4516880F)
badb0000 badb1b00 JGOGO Tue Feb 07 03:52:58 2006 (43E88A1A)
badba000 badbb420 ASACPI Thu Aug 12 19:52:52 2004 (411C2D04)
badbc000 badbd100 swenum Tue Aug 03 22:58:41 2004 (41107B11)
badbe000 badbf280 USBD Fri Aug 17 14:02:58 2001 (3B7D8682)
badc4000 badc5f00 Fs_Rec Fri Aug 17 13:49:37 2001 (3B7D8361)
badc6000 badc7080 Beep Fri Aug 17 13:47:33 2001 (3B7D82E5)
badc8000 badc9080 mnmdd Fri Aug 17 13:57:28 2001 (3B7D8538)
badca000 badcb080 RDPCDD Fri Aug 17 13:46:56 2001 (3B7D82C0)
badd8000 badd9100 dump_WMILIB Fri Aug 17 14:07:23 2001 (3B7D878B)
bae1a000 bae1b400 tat Mon May 30 23:30:08 2005 (429C0470)
bae5c000 bae5d980 cpuz Tue Feb 20 06:18:35 2007 (45DB033B)
bae70000 bae70d00 pciide Fri Aug 17 13:51:49 2001 (3B7D83E5)
bae71000 bae71680 giveio Wed Apr 03 18:33:25 1996 (316334F5)
baeb6000 baeb6c00 audstub Fri Aug 17 13:59:40 2001 (3B7D85BC)
baf5f000 baf5fb80 Null Fri Aug 17 13:47:39 2001 (3B7D82EB)
bafc2000 bafc2d00 dxgthk Fri Aug 17 13:53:12 2001 (3B7D8438)
bf800000 bf9c0380 win32k Tue Aug 03 23:17:30 2004 (41107F7A)
bf9c1000 bf9d2580 dxg Tue Aug 03 23:00:51 2004 (41107B93)
bf9d3000 bff01e00 nv4_disp Fri Apr 20 06:33:39 2007 (4628C133)

Unloaded modules:
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {8, 2, 0, ba606c00}

Probably caused by : atl01_xp.sys ( atl01_xp+4593 )

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

Finished dump check

 

[peterdiva]

From what I can find out atl01_xp.sys belongs to Attansic L1 Gigabit Ethernet 10/100/1000Base-T Adapter. It's quite new, dated March 14 2007. Try going back to an older driver.

NDIS.sys isn't the problem. It belongs to Windows, it's in the mix because it's a network driver.

 

[Ph30nIX]

Find correct and stable drivers and do a clean install of windows, I assume you did this after installing new mobo?

 

[insaneoctane]

Yes, this is a fresh install. I'm waiting for my next minidump occurance (so, of course, it hasn't happened in over 2 days!). And I'll post to look for consistancy, but ABSOLUTELY, new MB, fresh install!

From what I can find out atl01_xp.sys belongs to Attansic L1 Gigabit Ethernet 10/100/1000Base-T Adapter. It's quite new, dated March 14 2007. Try going back to an older driver.

NDIS.sys isn't the problem. It belongs to Windows, it's in the mix because it's a network driver.

Thanks for the input. Do I just trust the bugcheck analysis that says that it's probably at01_xp.sys? Did you see that yourself, or just use the analysis' advice?? Lastly, would you be concerned about the sections that say:
Unable to load image atl01_xp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atl01_xp.sys
*** ERROR: Module load completed but symbols could not be loaded for atl01_xp.sys

I will start to hunt down an older atl01_xp.sys driver, as you suggested.

 

[carlson2525]

Side question: What did you do to properly install symbols?
" Unable to load image NDIS.sys, Win32 error 0n2"
<next reply>
"Okay, so I figured how install the symbols..."
WHat did you do? I have the same error on a different app I'm debugging.