New
#21
If it fixes the problem for you be sure and post back here and let us know how it went. I have a feeling this problem will become more widespread as time goes on.
If it fixes the problem for you be sure and post back here and let us know how it went. I have a feeling this problem will become more widespread as time goes on.
notinf
from this minidump i can see that the file tdx.sys is causing the issue..
as per you can see here...
it seems you are using a broadcom chip
it looks that like this is almost the same issue...
tdx.sys causing BSOD - Fixed!
if you can find a updated drivers for your chip (vista drivers should work fine...)
you should be able to solve the issue...
Code:MODULE_NAME: tdx FAULTING_MODULE: 82a3c000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4943153f READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 00000060 CURRENT_IRQL: 0 FAULTING_IP: tdx+7b93 91407b93 ff7060 push dword ptr [eax+60h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 LAST_CONTROL_TRANSFER: from 91407b93 to 82a969eb STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 8059c2a8 91407b93 badb0d00 00000002 00000000 nt+0x5a9eb 8059c3d8 8c27e58e 858ece68 8059c444 8059c538 tdx+0x7b93 8059c468 8c27d42b 860ff0f4 00006dc2 8059c538 tcpip+0x7358e 8059c4fc 8c27d87e 858deae0 858debd8 8059c538 tcpip+0x7242b 8059c550 8c27b06d 858deae0 858debd8 891a7330 tcpip+0x7287e 8059c580 8c27ac3b d39e2de9 8059c5a4 8059c5d4 tcpip+0x7006d 8059c5dc 8c27b33f 860e2588 858deae0 0059c650 tcpip+0x6fc3b 8059c644 8c27babc 860bea30 860e3000 00000000 tcpip+0x7033f 8059c694 8c261bc9 860e2588 860e3000 0000bd01 tcpip+0x70abc 8059c6b0 8c261def 860e2588 860e3000 8059c6ec tcpip+0x56bc9 8059c6c0 8c298cae 8059c6d4 c000023e 00000000 tcpip+0x56def 8059c6ec 8c298e57 8c302f58 8059c740 c000023e tcpip+0x8dcae 8059c70c 8c299284 8c302d68 00000006 8059c740 tcpip+0x8de57 8059c764 8c2981a5 8c302d68 00000006 00000000 tcpip+0x8e284 8059c7f4 8c293824 89151960 00000000 00000001 tcpip+0x8d1a5 8059c870 8c2f404a 89151470 891a7330 00000000 tcpip+0x88824 8059c8a4 82af4587 891a7330 a8973760 860f08d8 tcpip+0xe904a 8059c90c 8c2938fe 8c2f3f2d 8059c934 00000000 nt+0xb8587 8059c948 8c0db170 89151402 891a7300 00000000 tcpip+0x888fe 8059c980 8c0c97f6 89152008 891a7330 00000000 ndis+0x67170 8059c9a8 8c0c976d 00000000 891a7330 86ace878 ndis+0x557f6 8059cb24 8c075585 860d20e0 00000000 00000000 ndis+0x5576d 8059cb40 8c0a4f57 860d20e0 891a7330 00000000 ndis+0x1585 8059cb5c 8c0a4f17 8914d008 891a7330 00000000 ndis+0x30f57 8059cb78 8d6e54b5 8914d008 891a7330 00000000 ndis+0x30f17 8059cba0 8d6e9109 8914d008 914e29a8 866bb008 nwifi+0x44b5 8059cbc0 8c0a4f57 8914d360 891a7330 00000000 nwifi+0x8109 8059cbdc 8c0a4f17 865ab830 891b4328 00000000 ndis+0x30f57 8059cbf8 914dd7dd 865ab830 891b4328 00000000 ndis+0x30f17 8059cc20 8c0c99a2 00000001 891b4328 866bb980 vwififlt+0x27dd 8059cc44 8c0755e0 860d20e0 891b4328 00000000 ndis+0x559a2 8059cc6c 919259b4 860d20e0 891b4328 00000000 ndis+0x15e0 8059cc94 91926b80 ffffffff 891bd008 866a17ac bcmwl6+0x509b4 8059cd04 918eb447 865ac000 00000001 00000000 bcmwl6+0x51b80 8059cd34 918ec908 8534a000 891bd008 00000000 bcmwl6+0x16447 8059cde0 918f3e0c 8534a000 891bd008 8059ce20 bcmwl6+0x17908 8059cea0 918f61a3 8534a000 86519810 866a10a4 bcmwl6+0x1ee0c 8059ced0 918f73a1 ffffffff 8059cf38 8654d818 bcmwl6+0x211a3 8059ceec 9192c018 00008000 00000000 00000001 bcmwl6+0x223a1 8059cf0c 8c0c9228 8654d9d8 00000000 8059cf38 bcmwl6+0x57018 8059cf48 8c0754a4 86581adc 00581ac8 00000000 ndis+0x55228 8059cf70 82ad0e03 86581adc 86581ac8 00000000 ndis+0x14a4 8059cff4 82ad04cc 8d2aece0 00000000 00000000 nt+0x94e03 8059cff8 8d2aece0 00000000 00000000 00000000 nt+0x944cc 82ad04cc 00000000 00000000 00000000 00000000 0x8d2aece0 STACK_COMMAND: kb FOLLOWUP_IP: tdx+7b93 91407b93 ff7060 push dword ptr [eax+60h] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: tdx+7b93 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: tdx.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- 0: kd> lmvm tdx start end module name 91400000 91416000 tdx T (no symbols) Loaded symbol image file: tdx.sys Image path: \SystemRoot\system32\DRIVERS\tdx.sys Image name: tdx.sys Timestamp: Fri Dec 12 17:51:59 2008 (4943153F) CheckSum: 00020FEE ImageSize: 00016000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 0: kd> .reload Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ...... 0: kd> lmvm tdx start end module name 91400000 91416000 tdx (deferred) Mapped memory image file: c:\symbols\tdx.sys\4943153F16000\tdx.sys Image path: \SystemRoot\system32\DRIVERS\tdx.sys Image name: tdx.sys Timestamp: Fri Dec 12 17:51:59 2008 (4943153F) CheckSum: 00020FEE ImageSize: 00016000 File version: 6.1.7000.0 Product version: 6.1.7000.0 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: tdx.sys OriginalFilename: tdx.sys ProductVersion: 6.1.7000.0 FileVersion: 6.1.7000.0 (winmain_win7beta.081212-1400) FileDescription: TDI Translation Driver LegalCopyright: © Microsoft Corporation. All rights reserved. 0: kd> lmvm tdx start end module name 91400000 91416000 tdx (deferred) Mapped memory image file: c:\symbols\tdx.sys\4943153F16000\tdx.sys Image path: \SystemRoot\system32\DRIVERS\tdx.sys Image name: tdx.sys Timestamp: Fri Dec 12 17:51:59 2008 (4943153F) CheckSum: 00020FEE ImageSize: 00016000 File version: 6.1.7000.0 Product version: 6.1.7000.0 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: tdx.sys OriginalFilename: tdx.sys ProductVersion: 6.1.7000.0 FileVersion: 6.1.7000.0 (winmain_win7beta.081212-1400) FileDescription: TDI Translation Driver LegalCopyright: © Microsoft Corporation. All rights reserved.
Was just browsing through.. I have been looking for a fix for unpredictable but consistent bluescreens for a week since installing Win7 64 bit. Been trying driver after driver and config after config and FINALLY upping voltages in bios seemed to resolve the problems. Running Nforce 7 chipset on a shuttle mobo with amd athlon 2.4 4800.
Thanks very very much!!
Firstly - great forum - I've been browsing in here since I installed 7 (7100 64 bit)a week or two ago, moving form Vista 32bit.
Initially everything seemed to be fine but then I started blue screening with the error code as described above. Seemed to blue screen when I was browsing on Firefox or whilst I was afk. Last night I updated my BIOS and changed my power settings to stop the machine from hibernating. No crashes as yet but when it inevitably does crash Ill up my voltages in BIOS and see what happens.
One concern i do have though is that even though it never seems to Blue Screen while Im gaming it randomly closes Warhammer Online down. I dont get any error messages - it just switches back to windows. Could this be caused by the same power kernal problems that have been showing from the event manager? I cant see the application listed in there as being problematic - although AVG seems to show on a regular basis.
I see that this thread was a bit old - sorry for resurrecting it. Is this still a known issue or is there some other fix or confirmation that upping the voltages resolves these kind of problems?
Sorry for being a bit disjointed - Im certainly no expert, hence I thoguht I'd post here!
hi
i have the same problem and at first i tought it was the video card but i think it is another problem what could it be please can you help me because it is crashing when transfering data from a partition to another and even when i am browsing the internet or trying to watch a video clip please what can i do
thanks![]()
Hi ganni and welcome to sevenforums.
Thanks for filling out yous sytem specs, not many ppl do and it helps alot. Could you tell us more abt the problem, and are you runnning 32 bit or 64?
One other thing you can do is to go into event viewer (type eventvwr in search) and see if there are any errors in the application tab.
Ken
I feel your pain ganni LOL, I had the exact same type of problem when I moved from Vista to Win7. Crashing would mostly occur when moving larger files accross the network but also was just unstable in general.
I only needed to bump up the SPP "northbridge" voltage one notch and problem solved.
It was simple as that.
It's hard to say if that is your exact problem because so many things can cause crashing.
Using the older Vista drivers for your graphics card might also help, some are having bad luck with the newer Win7 drivers.
hi
ken i am running 64 bit and sometimes it does not start too after system is shut down it fails to boot too and this is the event i found and it crashes sometimes after 1 - 8 -10 minutes or even less
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 17/08/2009 07:53:51
Event ID: 6
Task Category: (6)
Level: Error
Keywords:
User: SYSTEM
Computer: Jonathan-PC
Description:
Some processor performance power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Processor-Power" Guid="{0F67E49F-FE51-4E9F-B490-6F2948CC6027}" />
<EventID>6</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>6</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2009-08-17T05:53:51.359375000Z" />
<EventRecordID>6826</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="64" />
<Channel>System</Channel>
<Computer>Jonathan-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
</EventData>
</Event>
this is the event for crashing and this is the event for failing to boot
Log Name: System
Source: Service Control Manager
Date: 17/08/2009 07:40:19
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Jonathan-PC
Description:
The TBPanel service failed to start due to the following error:
The system cannot find the file specified.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2009-08-17T05:40:19.250976500Z" />
<EventRecordID>6679</EventRecordID>
<Correlation />
<Execution ProcessID="480" ThreadID="484" />
<Channel>System</Channel>
<Computer>Jonathan-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">TBPanel</Data>
<Data Name="param2">%%2</Data>
</EventData>
</Event>
Last edited by ganni76; 17 Aug 2009 at 01:16. Reason: more information
What if I have a laptop and I cant overclock how I fix this problem?