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

Windows 7 Memory Dump


  • Please log in to reply

#1
redline582

redline582

    Member

  • Member
  • PipPip
  • 45 posts
I have been running Windows 7 since the release day. It's been running flawlessly until about a week ago. I do normal updates just like any other user to make sure that my computer is up to date. But for about the last week my computer has randomly gone to a BSOD and done a memory dump and restart. It does it quickly and I've been trying to decipher what it displays. All I've gotten for sure is driver_irql_less_than_or_not_equal. I've tried rolling back drivers and reseating my ram. No luck. Any help would be greatly appreciated. Thanks!

MSI P45 Platinum HC Edition
Intel Core 2 Duo E8500
4x2Gb G Skill PC6400
VisionTek HD 3870
  • 0

Advertisements


#2
Anthony19

Anthony19

    Member

  • Member
  • PipPipPip
  • 384 posts
Hello redline582 & Welcome to GTG !

Start with retrieving the correct minidump information ( this should point us in the correct direction )

Navigate to c:/windows/minidump , Zip and attach minidump log file with next reply

meanwhile...

Have you tested tour RAM modules ???

I would start there... running overnight if possible

Use memtest located @ http://www.geekstogo...t86-file11.html

Be sure to scroll down and read how to use the program correctly

Then , lets check the temp's

To check the temp's use Speed fan located @ http://www.almico.com/speedfan437.exe ( Direct Link )

Run Speedfan , then run a stessful game or application , Keep an eye on temps !

best of luck

Anthony19
  • 0

#3
redline582

redline582

    Member

  • Topic Starter
  • Member
  • PipPip
  • 45 posts
Hi Anthony19, thanks for the speedy reply! I'm attaching a zip file with a few of the most recent dmp files. I had previously run a memtest and all seemed ok. My temps are around 33-34C on my processor and 31-32C on my HDD.

Attached Files


  • 0

#4
usasma

usasma

    Member

  • Member
  • PipPipPip
  • 636 posts
  • MVP
I ran the last dump file in my debugger and I get this:

Microsoft ฎ Windows Debugger Version 6.9.0003.113 AMD64
Copyright ฉ Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\FUBAR\Downloads\Windows_7_Memory_Dump\Windows 7 Memory Dump\091108-34226-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 7 Kernel Version 7000 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Kernel base = 0xfffff800`02a1e000 PsLoadedModuleList = 0xfffff800`02c6c050
Debug session time: Thu Sep 11 05:45:11.486 2008 (GMT-4)
System Uptime: 0 days 0:08:35.373
Loading Kernel Symbols
....................................................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {b8, 2, 0, fffff8800137efc0}

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : tdx.sys ( tdx!TdxEventReceiveConnection+300 )

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: 00000000000000b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800137efc0, address which referenced memory

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cd70e0
00000000000000b8

CURRENT_IRQL: 2

FAULTING_IP:
tdx!TdxEventReceiveConnection+300
fffff880`0137efc0 4c8b82b8000000 mov r8,qword ptr [rdx+0B8h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

TRAP_FRAME: fffff88005707460 -- (.trap 0xfffff88005707460)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=fffffa80096ec778 rcx=fffffa800978c390
rdx=0000000000000000 rsi=0000000000000004 rdi=0000000000000004
rip=fffff8800137efc0 rsp=fffff880057075f0 rbp=fffff880057078b8
r8=0000000000000000 r9=fffff88005707630 r10=fffff88003221500
r11=fffff880057075c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
tdx!TdxEventReceiveConnection+0x300:
fffff880`0137efc0 4c8b82b8000000 mov r8,qword ptr [rdx+0B8h] ds:0002:00000000`000000b8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ab8e69 to fffff80002ab9900

STACK_TEXT:
fffff880`05707318 fffff800`02ab8e69 : 00000000`0000000a 00000000`000000b8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05707320 fffff800`02ab7b1d : 00000000`00000000 00000000`000000b8 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`05707460 fffff880`0137efc0 : 00000000`c000021b fffffa80`08b00f40 fffffa80`0978c390 00000000`c0000016 : nt!KiPageFault+0x25d
fffff880`057075f0 fffff880`00e894ee : 00000000`00000006 00000000`00000000 00000000`00000000 fffff880`00e54d76 : tdx!TdxEventReceiveConnection+0x300
fffff880`05707730 fffff880`00e84310 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpIndicateData+0xfe
fffff880`05707830 fffff880`00e88545 : 00000000`00000000 fffffa80`097f8890 00000000`00000002 00000000`00000007 : tcpip!TcpDeliverDataToClient+0x370
fffff880`05707990 fffff880`00e84bb7 : fffffa80`071da040 fffff880`05707ca8 fffffa80`07b94520 fffffa80`09a91010 : tcpip!TcpDeliverReceive+0xa5
fffff880`05707a80 fffff880`00e87925 : fffff880`05707c80 fffffa80`00000000 fffffa80`0982d570 00000000`00000000 : tcpip!TcpTcbFastDatagram+0x207
fffff880`05707bd0 fffff880`00e88ef9 : fffffa80`07bd3f00 fffffa80`0982d570 fffffa80`07bd4000 00000000`00000000 : tcpip!TcpTcbReceive+0x275
fffff880`05707da0 fffff880`00e889bc : fffff880`04e7e022 fffffa80`07bd4000 00000000`00000000 fffff880`00e69501 : tcpip!TcpMatchReceive+0x1e9
fffff880`05707ee0 fffff880`00e66e6d : fffffa80`07bd3f00 fffff880`00f858b0 fffff880`057007c0 fffffa80`086677d0 : tcpip!TcpPreValidatedReceive+0x31c
fffff880`05707fc0 fffff880`00e67a69 : 00000000`00000000 00000000`00000000 ffff0000`05878dff 00000051`00000481 : tcpip!IppDeliverListToProtocol+0x4d
fffff880`05708080 fffff880`00e670f0 : fffff880`00f858b0 fffffa80`08667800 00000000`00000000 fffff880`05708140 : tcpip!IppProcessDeliverList+0x59
fffff880`057080f0 fffff880`00e687c4 : 00000000`00000000 fffffa80`07bd4000 fffff880`00f858b0 00000000`0869d001 : tcpip!IppReceiveHeaderBatch+0x231
fffff880`057081e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IpFlcReceivePackets+0x664


STACK_COMMAND: kb

FOLLOWUP_IP:
tdx!TdxEventReceiveConnection+300
fffff880`0137efc0 4c8b82b8000000 mov r8,qword ptr [rdx+0B8h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: tdx!TdxEventReceiveConnection+300

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tdx

IMAGE_NAME: tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4943190b

FAILURE_BUCKET_ID: X64_0xD1_tdx!TdxEventReceiveConnection+300

BUCKET_ID: X64_0xD1_tdx!TdxEventReceiveConnection+300

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


First, please note the line in Red above. This seems to indicate that the date on your system isn't correct. This will affect a lot of things, and it's likely to be the reason for the errors in the memory dump analysis.

Next, here's a link to a brief description of the error: http://aumha.org/a/stop.php#0xd1
In general it points to drivers, but can have a memory component (less likely).

The error occurred in tdx.sys (a Microsoft networking file named the TDI Translation Driver)
The stack trace shows that TCP/IP was also running just prior to the crash (more networking stuff).

Finally, a google for tdx.sys reveals a number of compatibility problems with network device drivers.
Your existing driver may have worked until a Windows Update came along and brought the incompatibility to the forefront.
So, the first place to start is with your networking drivers.

I'd download the latest Vista drivers from here (make sure I've selected the right one's): http://www.realtek.c...p;GetDown=false

Then I'd uninstall your networking drivers from the Control Panel...Programs...Uninstall a Program applet
Then check to make sure the device is uninstalled in Device Manager by clicking on Start and typing "devmgmt.msc" (without the quotes) and pressing Enter. Expand the + sign next to Network Adapters and right click on the RealTek device to uninstall it if it's not already uninstalled.
Reboot to ensure that everything is gone, then install the freshly downloaded drivers using compatibility mode for "Run as Windows Vista" and "Run as Administrator". Ensure that you do this for All Users.

Edited by usasma, 09 April 2009 - 09:42 AM.

  • 0

#5
redline582

redline582

    Member

  • Topic Starter
  • Member
  • PipPip
  • 45 posts
Thanks usama, and about the date, for some reason it resets the date and time to that specific date when it does the memory dump. I usually reset it when I remember it happens. But I followed all of the instructions and hopefully all will be well. Im going to play around with some network and resource intensive applications and see what comes about and post soon. Thanks again!
  • 0

#6
usasma

usasma

    Member

  • Member
  • PipPipPip
  • 636 posts
  • MVP
If the dump resets your date and time, it could be that that CMOS battery is dead/dying (or it could be other problems).
I bought an Asus motherboard a couple of years ago and had the CMOS battery die within 4 months.

It's the silver thing (about the size of a US nickel) that's shown between the 2 blue lines on the lower left of the top picture (labelled Intel P45 Chipset and Intel ICH10R Chipset).
It's usually a CR2032 battery and they're available at most places that sell batteries (WalMart, Radio Shack, BestBuy, etc):
Posted Image

Edited by usasma, 09 April 2009 - 10:16 AM.

  • 0

#7
redline582

redline582

    Member

  • Topic Starter
  • Member
  • PipPip
  • 45 posts
Ok the latest attempts have had no effect. It seems as if the dump comes from almost no cause, so maybe it possibly could be the cmos battery but Im not sure if there is an easy way to test that. I've reset the cmost multiple times either using my cmos clear or removing the battery. I've also attached the latest dmp file. (It's become frustrating enough that I feel the need to name my files in a humorous manner)

Attached Files


  • 0

#8
usasma

usasma

    Member

  • Member
  • PipPipPip
  • 636 posts
  • MVP
Same stuff, different dump :)
This dump file is essentially the same as the previous one.

You've got 3 issues:
- time changing on it's own
- crashes
- bad symbols for nt.dll (Windows may have updated nt.dll, but the symbols weren't updated on the Microsoft Symbol Server)


As it's still a STOP 0xD1 error, let's pursue that a bit more.
The other causes listed are memory issues, so let's take a look at them.

Try recreating your pagefile. To do this, follow these steps:

2) Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.


Next, I'd suggest running the built in memory diagnostic program. The instructions are similar to those in Vista, so try this link: http://www.bleepingc...utorial146.html
You should also be able to boot into the Memory diagnostic from the Safe Mode screen. When first starting the system, rapidly tap the F8 key starting just before the Windows splash screen shows up. This should get you into the Safe Mode screen - and the Memory Diagnostic choice should be down towards the bottom of the page.
  • 0

#9
redline582

redline582

    Member

  • Topic Starter
  • Member
  • PipPip
  • 45 posts
Thanks for all of your help usama, but I think I fixed it. I just determined that it must have been one of those pesky windows updates, did a system restore to before a certain update and now everything is ok so I think we can call this one resolved. Thanks again!
  • 0

#10
usasma

usasma

    Member

  • Member
  • PipPipPip
  • 636 posts
  • MVP
I'm glad to hear that you've resolved it! Thanks for letting us know!
  • 0

#11
jcgriff2

jcgriff2

    Member

  • Expert
  • 92 posts
  • MVP
Hi -

Apologies for the intrusion, but I believe this will help OP redline582.

All 8 mini kernel dumps had identical 0xd1 bugchecks, 4th parm notwithstanding.
0xd1 (0xb8, 0x2, 0x0, 0x8800138bfc0)
0xd1 (0xb8, 0x2, 0x0, 0x8800133dfc0)
0xd1 (0xb8, 0x2, 0x0, 0x8800133afc0)
0xd1 (0xb8, 0x2, 0x0, 0x88001335fc0)
0xd1 (0xb8, 0x2, 0x0, 0x88001340fc0)
0xd1 (0xb8, 0x2, 0x0, 0x88001387fc0)
0xd1 (0xb8, 0x2, 0x0, 0x88001339fc0)
0xd1 (0xb8, 0x2, 0x0, 0x8800137efc0)


0xd1 = DRIVER_IRQL_NOT_LESS_OR_EQUAL - a kernel mode app (driver) tried to access a pageable memory address - or one that was not valid -when it should not have (IRQL too high).

The parms -
0xb8 = the memory address referenced by parm #4
0x2 = IRQL
0x0 = READ (vs. WRITE)
0x880013xxxxx = memory address that attempted to access parm #1 address

The probable cause in all 8 BSODs listed as tdx.sys, timestamp = Fri Dec 12 21:08:11 2008 (4943190B), a Microsoft TDI (Transport Driver Interface) driver.
The program instruction each failed on = tdx!TdxEventReceiveConnection+300. This is network activity.

The dumps show the system time problem you mentioned. Only 1 dump has April 9 as timestamp. 7 of the 8 show system uptime between 7 - 12 minutes before another BSOD hit. 1 dump system up time = 4:54:40.269 - almost 5 hours. This is without a doubt the 1st BSOD dump file.

tdx.sys is not the cause here. A 3rd party driver is. Windows System Restore may have saved you for now, but the BSODs will return if the rogue driver is not dealt with. There are 2 options from here -

First, see if updates are availble for these drivers found in the loaded driver list -
the 1st 3 specifically -
• xusb21.sys Tue Aug 28 13:04:19 2007 - Xbox 360 wireless reciever driver
• usbaapl64.sys Fri Nov 14 16:41:10 2008 - Apple mobile USB driver
• btusbflt.sys Wed Aug 27 21:12:08 2008 - Bluetooth
• OmniTV.sys Tue Apr 29 06:27:20 2008 - Conexant AVStream video capture driver
• Rt64win7.sys Wed Aug 20 20:14:07 2008 - Realtek Ethernet NIC


These 2 are the newest drivers in your system. I think AVG was updated after phoning home and clashed with another - Xbox maybe ?
• avgtdia.sys Mon Mar 23 06:35:48 2009 - AVG a/v
• atikmdag.sys Wed Feb 25 16:54:32 2009 - ATI Radeon kernel driver

Check for the driver updates. When complete, run the Driver Verifier.
START | type cmd.exe | right-click on cmd.exe uptop under programs | Run as Administrator | type verifier & hit enter - the Verifier screen will appear | do the following:
1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -
• Special Pool 
• Pool Tracking 
• Force IRQL checking
• Deadlock Detection
• Miscellaneous Checks</blockquote>
4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where Microsoft is not the Provider
7. Click on Finish 
8. Re-boot


If the Driver Verifier (DV) finds a violation, it will result in a BSOD. After re-boot, you may not be able to log on. If so, boot into SAFEMODE (select Last Known Good Configuration or System Restore). To see the status of Verifier - type verifier - select the last option on the first screen - "Display information about the currently verified drivers..". To turn Driver Verifier off - verifier /reset then re-boot. Keep the verifier running as long as possible, even if the status screen appears clear.

If you get a BSOD, get the verifier-enabled dump file from c:\windows\minidump, zip it up & attach to next post.

A more detailed bugcheck summary is below.

Regards. . .

jcgriff2

.

Bugcheck Summary
――――――――――――――――――――――――――――――――――――――――――――――――――――――
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Debug session time: Thu Apr 9 12:17:30.115 2009 (GMT-4)
System Uptime: 0 days 0:12:03.002
BugCheck D1, {b8, 2, 0, fffff8800138bfc0}
Probably caused by : tdx.sys ( tdx!TdxEventReceiveConnection+300 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Debug session time: Thu Sep 11 06:32:06.166 2008 (GMT-4)
System Uptime: 0 days 0:08:06.053
BugCheck D1, {b8, 2, 0, fffff8800133dfc0}
Probably caused by : tdx.sys ( tdx!TdxEventReceiveConnection+300 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Debug session time: Thu Sep 11 00:22:21.358 2008 (GMT-4)
System Uptime: 0 days 0:12:25.245
BugCheck D1, {b8, 2, 0, fffff8800133afc0}
Probably caused by : tdx.sys ( tdx!TdxEventReceiveConnection+300 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Debug session time: Thu Sep 11 06:14:41.460 2008 (GMT-4)
System Uptime: 0 days 0:07:38.347
BugCheck D1, {b8, 2, 0, fffff88001335fc0}
Probably caused by : tdx.sys ( tdx!TdxEventReceiveConnection+300 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Debug session time: Thu Sep 11 06:52:05.150 2008 (GMT-4)
System Uptime: 0 days 0:08:06.036
BugCheck D1, {b8, 2, 0, fffff88001340fc0}
Probably caused by : tdx.sys ( tdx!TdxEventReceiveConnection+300 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Debug session time: Thu Sep 11 00:09:01.179 2008 (GMT-4)
System Uptime: 0 days 0:08:10.065
BugCheck D1, {b8, 2, 0, fffff88001387fc0}
Probably caused by : tdx.sys ( tdx!TdxEventReceiveConnection+300 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Debug session time: Thu Sep 11 05:18:23.382 2008 (GMT-4)
System Uptime: 0 days 4:54:40.269
BugCheck D1, {b8, 2, 0, fffff88001339fc0}
Probably caused by : tdx.sys ( tdx!TdxEventReceiveConnection+300 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Debug session time: Thu Sep 11 05:45:11.486 2008 (GMT-4)
System Uptime: 0 days 0:08:35.373
BugCheck D1, {b8, 2, 0, fffff8800137efc0}
Probably caused by : tdx.sys ( tdx!TdxEventReceiveConnection+300 )
――――――――――――――――――――――――――――――――――――――――――――――――――――――
jcgriff2
http://www.techsuppo...ers/185203.html
  • 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