i81xdnt5.dll

Status
Not open for further replies.
V

Valor

Posts: 65   +0
Hey all,
i had a couple of BSODs and reboots the past month and the minidumps I received from that point me to the driver i81xdnt5.dll. This is an Intel Graphics driver for my integrated video adapter....I checked to see in Windows/system32 if the driver was missing but nope...so I figure it's corrupt and downloaded i81xdnt5.dll off the web. (www.dlldump.com) How do I replace it now? When I try to do it in windows it tells me the file is being used by another program. Anyhow, here's the minidumps, maybe you guys can tell me what exactly is wrong and if my course of action would be the right one...thanks!!

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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 UP Free x86 compatible
Product: WinNt
Built by: 2600.xpclient.010817-1148
Kernel base = 0x804d0000 PsLoadedModuleList = 0x80545b28
Debug session time: Sun Jan 14 08:41:58.031 2007 (GMT-6)
System Uptime: 0 days 3:19:51.457
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
.............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {bd055588, 0, bf9d8273, 0}

Unable to load image i81xdnt5.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for i81xdnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for i81xdnt5.dll

Could not read faulting driver name
Probably caused by : i81xdnt5.dll ( i81xdnt5+20273 )

Followup: MachineOwner


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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: bd055588, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf9d8273, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: bd055588

FAULTING_IP:
i81xdnt5+20273
bf9d8273 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: explorer.exe

TRAP_FRAME: f392e170 -- (.trap fffffffff392e170)
ErrCode = 00000000
eax=00000000 ebx=bd055588 ecx=00000003 edx=0000000c esi=bd055588 edi=f4c7e2e0
eip=bf9d8273 esp=f392e1e4 ebp=f392e5e8 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
i81xdnt5+0x20273:
bf9d8273 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from 8051a00c to 804fc1bb

STACK_TEXT:
f392e10c 8051a00c 00000050 bd055588 00000000 nt!KeBugCheckEx+0x19
f392e158 804d7a5b 00000000 bd055588 00000000 nt!MmAccessFault+0x6cb
f392e158 bf9d8273 00000000 bd055588 00000000 nt!KiTrap0E+0xb8
WARNING: Stack unwind information not available. Following frames may be wrong.
f392e1e0 e1573000 f392e5e8 f392e5e8 00000003 i81xdnt5+0x20273
f392e690 bf81ddff e2b2bd08 e1140a88 00000000 0xe1573000
f392e6f0 bf81dd57 bf9bb660 f392e7ac e2b2bd08 win32k!OffBitBlt+0x95
f392e7b8 bf84c248 e2b2bd08 e1140a88 00000000 win32k!SpBitBlt+0x1e7
f392e860 804d4e91 e2b2bcf8 e2851e88 e1695140 win32k!NtGdiBitBlt+0x54b
f392e860 7ffe0304 e2b2bcf8 e2851e88 e1695140 nt!KiSystemService+0xc4
00aeedcc 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


STACK_COMMAND: kb

FOLLOWUP_IP:
i81xdnt5+20273
bf9d8273 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: i81xdnt5+20273

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: i81xdnt5

IMAGE_NAME: i81xdnt5.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3d3d7ddd

FAILURE_BUCKET_ID: 0x50_i81xdnt5+20273

BUCKET_ID: 0x50_i81xdnt5+20273

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


----------------------------------------


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 UP Free x86 compatible
Product: WinNt
Built by: 2600.xpclient.010817-1148
Kernel base = 0x804d0000 PsLoadedModuleList = 0x80545b28
Debug session time: Sun Jan 21 09:03:09.284 2007 (GMT-6)
System Uptime: 2 days 8:18:58.902
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {bd1f3f08, 0, bf9d8273, 0}

Unable to load image i81xdnt5.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for i81xdnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for i81xdnt5.dll

Could not read faulting driver name
Probably caused by : i81xdnt5.dll ( i81xdnt5+20273 )

Followup: MachineOwner


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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: bd1f3f08, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf9d8273, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: bd1f3f08

FAULTING_IP:
i81xdnt5+20273
bf9d8273 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: explorer.exe

TRAP_FRAME: f387e170 -- (.trap fffffffff387e170)
ErrCode = 00000000
eax=00000000 ebx=bd1f3f08 ecx=00000003 edx=0000000c esi=bd1f3f08 edi=f4c3f398
eip=bf9d8273 esp=f387e1e4 ebp=f387e5e8 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
i81xdnt5+0x20273:
bf9d8273 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from 8051a00c to 804fc1bb

STACK_TEXT:
f387e10c 8051a00c 00000050 bd1f3f08 00000000 nt!KeBugCheckEx+0x19
f387e158 804d7a5b 00000000 bd1f3f08 00000000 nt!MmAccessFault+0x6cb
f387e158 bf9d8273 00000000 bd1f3f08 00000000 nt!KiTrap0E+0xb8
WARNING: Stack unwind information not available. Following frames may be wrong.
f387e1e0 e155e000 f387e5e8 f387e5e8 00000003 i81xdnt5+0x20273
f387e690 bf81ddff e30f9b58 e2b22438 00000000 0xe155e000
f387e6f0 bf81dd57 bf9bb660 f387e7ac e30f9b58 win32k!OffBitBlt+0x95
f387e7b8 bf84c248 e30f9b58 e2b22438 00000000 win32k!SpBitBlt+0x1e7
f387e860 804d4e91 e30f9b48 e11c79e8 e16ab008 win32k!NtGdiBitBlt+0x54b
f387e860 7ffe0304 e30f9b48 e11c79e8 e16ab008 nt!KiSystemService+0xc4
009cedcc 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


STACK_COMMAND: kb

FOLLOWUP_IP:
i81xdnt5+20273
bf9d8273 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: i81xdnt5+20273

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: i81xdnt5

IMAGE_NAME: i81xdnt5.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3d3d7ddd

FAILURE_BUCKET_ID: 0x50_i81xdnt5+20273

BUCKET_ID: 0x50_i81xdnt5+20273

Followup: MachineOwner
 
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 UP Free x86 compatible
Product: WinNt
Built by: 2600.xpclient.010817-1148
Kernel base = 0x804d0000 PsLoadedModuleList = 0x80545b28
Debug session time: Sun Jan 21 09:13:50.288 2007 (GMT-6)
System Uptime: 0 days 0:12:37.078
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {bcaa3608, 0, bf9d8273, 0}

Unable to load image i81xdnt5.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for i81xdnt5.dll
*** ERROR: Module load completed but symbols could not be loaded for i81xdnt5.dll

Could not read faulting driver name
Probably caused by : i81xdnt5.dll ( i81xdnt5+20273 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: bcaa3608, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf9d8273, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: bcaa3608

FAULTING_IP:
i81xdnt5+20273
bf9d8273 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: explorer.exe

TRAP_FRAME: f33fe170 -- (.trap fffffffff33fe170)
ErrCode = 00000000
eax=00000000 ebx=bcaa3608 ecx=00000003 edx=0000000c esi=bcaa3608 edi=f4c11258
eip=bf9d8273 esp=f33fe1e4 ebp=f33fe5e8 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
i81xdnt5+0x20273:
bf9d8273 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from 8051a00c to 804fc1bb

STACK_TEXT:
f33fe10c 8051a00c 00000050 bcaa3608 00000000 nt!KeBugCheckEx+0x19
f33fe158 804d7a5b 00000000 bcaa3608 00000000 nt!MmAccessFault+0x6cb
f33fe158 bf9d8273 00000000 bcaa3608 00000000 nt!KiTrap0E+0xb8
WARNING: Stack unwind information not available. Following frames may be wrong.
f33fe1e0 e1553000 f33fe5e8 f33fe5e8 00000003 i81xdnt5+0x20273
f33fe690 bf81ddff e1103488 e11832c0 00000000 0xe1553000
f33fe6f0 bf81dd57 bf9bb660 f33fe7ac e1103488 win32k!OffBitBlt+0x95
f33fe7b8 bf84c248 e1103488 e11832c0 00000000 win32k!SpBitBlt+0x1e7
f33fe860 804d4e91 e1103478 e11b3630 e16985e0 win32k!NtGdiBitBlt+0x54b
f33fe860 7ffe0304 e1103478 e11b3630 e16985e0 nt!KiSystemService+0xc4
00b1e3b4 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


STACK_COMMAND: kb

FOLLOWUP_IP:
i81xdnt5+20273
bf9d8273 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: i81xdnt5+20273

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: i81xdnt5

IMAGE_NAME: i81xdnt5.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3d3d7ddd

FAILURE_BUCKET_ID: 0x50_i81xdnt5+20273

BUCKET_ID: 0x50_i81xdnt5+20273

Followup: MachineOwner
---------
 
Try a different approach. Maybe you shouldn't try to download a .dll file to replace your current one, instead you should download a new driver as a whole. Download the latest driver for your graphics device from Intel. Remove the old driver and install the new one. See if the problem goes away after that.

Also, you might get more help with BSODs if you start a thread in the Windows OS board. Most minidumps are analyzed there.

Good luck.
 
I installed the newest driver for the adapter as well as for my network card. But I still get reboots. I will post my minidumps in the windows sections like you suggested, hopefully I'll get more help there.
 
Minidumps - i81xdnt5.dll

Hello,
I had posted my minidumps in the audio/video section but it was suggested I should try this place to get more detailed help. Here's the link to the original thread and minidumps:
https://www.techspot.com/vb/topic69396.html
I have done everything as recommended in the 'before you post minidumps' section and RAM, overheating etc. all seem to be fine. I've just finished doing the pagefile sys and defragmenting but already I experienced a sudden reboot. I did as instructed, set the size at 768 (I have 512 RAM) and restarted. Strange thing is that my pagefile.sys is not to be found on my hard drive now...where should it be? Anyway, please look at the minidumps and let me know what I can do. Thank you!!
 
Threads merged and original thread moved.

If updating your graphics drivers doesn`t help. See this thread HERE. If that doesn`t help attach 5 or 6 of your latest minidumps here.

Regards Howard :)

Edit: I`ve just read your post properly. Did you try uninstalling your graphics drivers, then updating them?
 
I'll try that though I think I did that before and it didn't make a difference...I'm more concerned about the pagefile.sys. I tried finding it again with 'include hidden files and folders' checked but no success...where is it?? How do I succesfully create a pagefile.sys?
 
I just found my pagefile.sys by unchecking 'hide protected system files'. It is 768 MB like it should be. Now my question is this: Would it be recommended to also have a pagefile on my second hard disk which is the non-system one? Thanks
 
Why isn't anyone responding to me? I've actually put a pagefile.sys on both disk now and it improved the performance a little bit...wouldn't it be a better idea to put the pagefile on a partition solely dedicated to it? I would like to know other people's experiences on pagefiles, thanks!
 
The pagefile should be on the same drive as the OS. I have 1GB of RAM and I turned the pagefile off... My system "likes" it turned off
 
Actually I've read that moving the pagefile to it's own disk can help performance.
Should the file be left on Drive C:?

The slowest aspect of getting at a file on a hard disk is in head movement (‘seeking’). If you have only one physical drive then the file is best left where the heads are most likely to be, so where most activity is going on — on drive C:. If you have a second physical drive, it is in principle better to put the file there, because it is then less likely that the heads will have moved away from it. If, though, you have a modern large size of RAM, actual traffic on the file is likely to be low, even if programs are rolled out to it, inactive, so the point becomes an academic one. If you do put the file elsewhere, you should leave a small amount on C: — an initial size of 2MB with a Maximum of 50 is suitable — so it can be used in emergency. Without this, the system is inclined to ignore the settings and either have no page file at all (and complain) or make a very large one indeed on C:

In relocating the page file, it must be on a ‘basic’ drive. Windows XP appears not to be willing to accept page files on ‘dynamic’ drives.

NOTE: If you are debugging crashes and wish the error reporting to make a kernel or full dump, then you will need an initial size set on C: of either 200 MB (for a kernel dump) or the size of RAM (for a full memory dump). If you are not doing so, it is best to make the setting to no more than a ‘Small Dump’, at Control Panel | System | Advanced, click Settings in the ‘Startup and Recovery’ section, and select in the ‘Write Debug information to’ panel
Click to expand...

You should always have a pagefile, even with 1GB of RAM.
Can the Virtual Memory be turned off on a really large machine?

Strictly speaking Virtual Memory is always in operation and cannot be “turned off.” What is meant by such wording is “set the system to use no page file space at all.”

Doing this would waste a lot of the RAM. The reason is that when programs ask for an allocation of Virtual memory space, they may ask for a great deal more than they ever actually bring into use — the total may easily run to hundreds of megabytes. These addresses have to be assigned to somewhere by the system. If there is a page file available, the system can assign them to it — if there is not, they have to be assigned to RAM, locking it out from any actual use.
Click to expand...

http://www.aumha.org/win5/a/xpvm.php
 
I've experimented with and without a page file, and I have noticed a slight performance gain without one. I guess this is a system by system choice
 
Status
Not open for further replies.

Similar threads

R
Windows 2008 R2 BSOD
Replies
1
Views
2K
Cycloid Torus
Cycloid Torus
Purple Flame
BSoD - UNEXPECTED_KERNEL_MODE_TRAP (7f)
Replies
14
Views
2K
Purple Flame
Purple Flame
MaxFfm
BOSD irql_not_less_or_equal ntoskrnl.exe
Replies
1
Views
4K
Tmagic650
Tmagic650

Latest posts

Back