Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Vicious BSOD after new graphics card install


  • Please log in to reply
10 replies to this topic

#1 JonnyRocker7

JonnyRocker7

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Long Island, NY
  • Local time:07:25 PM

Posted 25 February 2009 - 04:42 PM

Where do I begin?!
I have a Dell Dimension E510 3.2g processor etc. I recently installed an ATI Radeon HD 3650 graphics card and oncome the blue screens. I updated the drivers straight from the manufacturers website and now in device manager everything looks kosher. However, it isnt. I constantly get blue screens when the pc is being used for gaming. checkin e-mail, workin on very large essays for school or even when the pc is idle for hours and goes blue. I then have to power down and reboot.
I ran the minidump file with MS 32bit debugger and here are the results-

Microsoft Windows Debugger Version 6.11.0001.402 X86
Copyright Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini021909-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are availableWARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Feb 18 22:59:37.982 2009 (GMT-5)
System Uptime: 0 days 2:25:33.702
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
...................
*** WARNING: Unable to verify timestamp for cwmtdi.sys
*** ERROR: Module load completed but symbols could not be loaded for cwmtdi.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************U
se !analyze -v to get detailed debugging information.BugCheck 1000000A, {0, 2, 1, 806e684a}*** WARNING: Unable to verify timestamp for SYMTDI.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMTDI.SYS
Unable to load image SymIM.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SymIM.sys
*** ERROR: Module load completed but symbols could not be loaded for SymIM.sys
*** WARNING: Unable to verify timestamp for bcmwl5.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl5.sys
Probably caused by : cwmtdi.sys ( cwmtdi+8c62 )Followup: MachineOwner
---------1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************I
RQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 806e684a, address which referenced memoryDebugging Details:
------------------
WRITE_ADDRESS: 00000000 CURRENT_IRQL: 2FAULTING_IP:
hal!KfAcquireSpinLock+1a
806e684a f00fba2900 lock bts dword ptr [ecx],0CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xAPROCESS_NAME: IdleLAST_CONTROL_TRANSFER: from b9020c62 to 806e684aSTACK_TEXT:
ba4d3474 b9020c62 ba4d3624 8afd89a8 ba4d35fc hal!KfAcquireSpinLock+0x1a
WARNING: Stack unwind information not available. Following frames may be wrong.
ba4d349c b9022a73 00000000 8afd89a8 00000000 cwmtdi+0x8c62
ba4d34f8 ac69afae 8afd89a8 00000016 ba4d3624 cwmtdi+0xaa73
ba4d35a4 ac6e50c2 89438028 00000016 ba4d3624 SYMTDI+0xfae
ba4d3640 ac6e5370 87a30790 0101a8c0 6401a8c0 tcpip!FindListenConn+0x305
ba4d36e4 ac6caef5 8a92b840 6401a8c0 0101a8c0 tcpip!TCPRcv+0x2ff
ba4d3744 ac6cab19 00000020 8a92b840 ac6cd0b6 tcpip!DeliverToUser+0x18e
ba4d37c0 ac6ca836 ac70a8e0 8a92b840 8aa09048 tcpip!DeliverToUserEx+0x95e
ba4d3878 ac6c9928 8a92b840 8aa0905c 00000028 tcpip!IPRcvPacket+0x6cb
ba4d38b8 ac6c9853 00000000 89659e18 8aa0903a tcpip!ARPRcvIndicationNew+0x149
ba4d38f4 b9dc3e45 8a8e3868 00000000 b8998b40 tcpip!ARPRcvPacket+0x68
ba4d3948 b899301d 00b1c550 8ad61768 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x307
ba4d395c b89931b4 8ae86910 8ad61768 00000001 psched!PsFlushReceiveQueue+0x15
ba4d3980 b89935f9 8a882c58 00000000 8ae86910 psched!PsEnqueueReceivePacket+0xda
ba4d3998 b9dc3c40 8a882c50 8aef36e8 8ae6f3d0 psched!ClReceiveComplete+0x13
ba4d39e8 ba3a0f43 00b1c550 ba4d3a14 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
ba4d3a08 b9dc3b9f 0188c398 89659e18 8ab04294 SymIM+0xf43
ba4d3a5c b8bb9f5a 00b1c550 ba4d3a8c 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1c2
ba4d3a84 b8bcd5ce 89659e18 00000000 8aa097d0 bcmwl5+0x9f5a
ba4d3aa4 b8bdda42 898b2e38 87b1c500 ba4d3c1c bcmwl5+0x1d5ce
ba4d3c30 b8bb526b 73292100 0000cd75 73292100 bcmwl5+0x2da42
ba4d3c44 b8bb4fc2 8aa029e8 00000000 8aa09040 bcmwl5+0x526b
ba4d3d10 b9db9e99 8ab04294 8055c0c0 ba3409c0 bcmwl5+0x4fc2
ba4d3d28 80545e7f 8ab0424c 8ab04238 00000000 NDIS!ndisMDpcX+0x21
ba4d3d44 80545b6c 00000000 ba342e20 80545d64 nt!KiRetireDpcList+0x61
ba4d3d50 80545d64 00000000 0000000e 00000000 nt!SwapContext+0xcc
ba4d3d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kbFOLLOWUP_IP:
cwmtdi+8c62
b9020c62 ?? ???SYMBOL_STACK_INDEX: 1SYMBOL_NAME: cwmtdi+8c62FOLLOWUP_NAME: MachineOwnerMODULE_NAME: cwmtdiIMAGE_NAME: cwmtdi.sysDEBUG_FLR_IMAGE_TIMESTAMP: 4648eb08FAILURE_BUCKET_ID: 0xA_cwmtdi+8c62BUCKET_ID: 0xA_cwmtdi+8c62Followup: MachineOwner
---------1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************I
RQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 806e684a, address which referenced memoryDebugging Details:
------------------
WRITE_ADDRESS: 00000000 CURRENT_IRQL: 2FAULTING_IP:
hal!KfAcquireSpinLock+1a
806e684a f00fba2900 lock bts dword ptr [ecx],0CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xAPROCESS_NAME: IdleLAST_CONTROL_TRANSFER: from b9020c62 to 806e684aSTACK_TEXT:
ba4d3474 b9020c62 ba4d3624 8afd89a8 ba4d35fc hal!KfAcquireSpinLock+0x1a
WARNING: Stack unwind information not available. Following frames may be wrong.
ba4d349c b9022a73 00000000 8afd89a8 00000000 cwmtdi+0x8c62
ba4d34f8 ac69afae 8afd89a8 00000016 ba4d3624 cwmtdi+0xaa73
ba4d35a4 ac6e50c2 89438028 00000016 ba4d3624 SYMTDI+0xfae
ba4d3640 ac6e5370 87a30790 0101a8c0 6401a8c0 tcpip!FindListenConn+0x305
ba4d36e4 ac6caef5 8a92b840 6401a8c0 0101a8c0 tcpip!TCPRcv+0x2ff
ba4d3744 ac6cab19 00000020 8a92b840 ac6cd0b6 tcpip!DeliverToUser+0x18e
ba4d37c0 ac6ca836 ac70a8e0 8a92b840 8aa09048 tcpip!DeliverToUserEx+0x95e
ba4d3878 ac6c9928 8a92b840 8aa0905c 00000028 tcpip!IPRcvPacket+0x6cb
ba4d38b8 ac6c9853 00000000 89659e18 8aa0903a tcpip!ARPRcvIndicationNew+0x149
ba4d38f4 b9dc3e45 8a8e3868 00000000 b8998b40 tcpip!ARPRcvPacket+0x68
ba4d3948 b899301d 00b1c550 8ad61768 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x307
ba4d395c b89931b4 8ae86910 8ad61768 00000001 psched!PsFlushReceiveQueue+0x15
ba4d3980 b89935f9 8a882c58 00000000 8ae86910 psched!PsEnqueueReceivePacket+0xda
ba4d3998 b9dc3c40 8a882c50 8aef36e8 8ae6f3d0 psched!ClReceiveComplete+0x13
ba4d39e8 ba3a0f43 00b1c550 ba4d3a14 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
ba4d3a08 b9dc3b9f 0188c398 89659e18 8ab04294 SymIM+0xf43
ba4d3a5c b8bb9f5a 00b1c550 ba4d3a8c 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1c2
ba4d3a84 b8bcd5ce 89659e18 00000000 8aa097d0 bcmwl5+0x9f5a
ba4d3aa4 b8bdda42 898b2e38 87b1c500 ba4d3c1c bcmwl5+0x1d5ce
ba4d3c30 b8bb526b 73292100 0000cd75 73292100 bcmwl5+0x2da42
ba4d3c44 b8bb4fc2 8aa029e8 00000000 8aa09040 bcmwl5+0x526b
ba4d3d10 b9db9e99 8ab04294 8055c0c0 ba3409c0 bcmwl5+0x4fc2
ba4d3d28 80545e7f 8ab0424c 8ab04238 00000000 NDIS!ndisMDpcX+0x21
ba4d3d44 80545b6c 00000000 ba342e20 80545d64 nt!KiRetireDpcList+0x61
ba4d3d50 80545d64 00000000 0000000e 00000000 nt!SwapContext+0xcc
ba4d3d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kbFOLLOWUP_IP:
cwmtdi+8c62
b9020c62 ?? ???SYMBOL_STACK_INDEX: 1SYMBOL_NAME: cwmtdi+8c62FOLLOWUP_NAME: MachineOwnerMODULE_NAME: cwmtdiIMAGE_NAME: cwmtdi.sysDEBUG_FLR_IMAGE_TIMESTAMP: 4648eb08FAILURE_BUCKET_ID: 0xA_cwmtdi+8c62BUCKET_ID: 0xA_cwmtdi+8c62Followup: MachineOwner


The fan on the video card seems to be working. The pc doesn't seem to be overheating either.. I am out of ideas, please help!

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,106 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:25 PM

Posted 25 February 2009 - 05:30 PM

FWIW: http://www.file.net/process/cwmtdi.sys.html AND http://forums.techguy.org/windows-nt-2000-...lue-screen.html

You might post in the BleepingComputer.com - Am I infected What do I do - http://www.bleepingcomputer.com/forums/f/103/am-i-infected-what-do-i-do/ for opinions that are more substantial than mine.

If it's a valid anti-malware file...what's the parent program and how did it install on your system? If you have an AV program already installed...this driver/file (it's in the drivers folder) would only conflict with it, IMO.

http://www.file.net/process/symtdi.sys.html

http://www.file.net/process/bcmwl5.sys.html

Louis

#3 teacup61

teacup61

    Bleepin' Texan!


  • Malware Response Team
  • 17,075 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Wills Point, Texas
  • Local time:06:25 PM

Posted 25 February 2009 - 07:05 PM

Please be advised the user has posted a HijackThis log. I don't see any malware present, but am having him try a couple of things. No need to close this thread yet, but I wanted you to know I am working with him elsewhere. :thumbsup:

tea
Please make a donation so I can keep helping people just like you.
Every little bit helps! :)
You can even use your credit card! Thank you!

Posted Image


Error reading poptart in Drive A: Delete kids y/n?

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,106 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:25 PM

Posted 25 February 2009 - 07:22 PM

Appreciated, thanks :thumbsup:.

Louis

#5 teacup61

teacup61

    Bleepin' Texan!


  • Malware Response Team
  • 17,075 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Wills Point, Texas
  • Local time:06:25 PM

Posted 01 March 2009 - 06:19 PM

Update to this.....the user never responded, so I closed the topic in the HJT forum.
Please make a donation so I can keep helping people just like you.
Every little bit helps! :)
You can even use your credit card! Thank you!

Posted Image


Error reading poptart in Drive A: Delete kids y/n?

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,106 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:25 PM

Posted 01 March 2009 - 06:37 PM

Again...thanks for keeping us posted :thumbsup:.

Louis

#7 JonnyRocker7

JonnyRocker7
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Long Island, NY
  • Local time:07:25 PM

Posted 01 March 2009 - 08:46 PM

Sorry I didnt know the post required a reply from me.

#8 tg1911

tg1911

    Lord Spam Magnet


  • Members
  • 19,274 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:SW Louisiana
  • Local time:05:25 PM

Posted 01 March 2009 - 10:28 PM

Send teacup61 a PM, asking that she re-open the topic.
MOBO: GIGABYTE GA-MA790X-UD4P, CPU: Phenom II X4 955 Deneb BE, HS/F: CoolerMaster V8, RAM: 2 x 1G Kingston HyperX DDR2 800, VGA: ECS GeForce Black GTX 560, PSU: Antec TruePower Modular 750W, Soundcard: Asus Xonar D1, Case: CoolerMaster COSMOS 1000, Storage: Internal - 2 x Seagate 250GB SATA, 2 x WD 1TB SATA; External - Seagate 500GB USB, WD 640GB eSATA, 3 x WD 1TB eSATA

Become a BleepingComputer fan: Facebook

#9 JonnyRocker7

JonnyRocker7
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Long Island, NY
  • Local time:07:25 PM

Posted 04 March 2009 - 12:21 PM

The error on my pc "Probably caused by : cwmtdi.sys ( cwmtdi+8c62 )Followup: MachineOwner
---------1: kd> !analyze -v" I think is from my Internet Filter K9 blue coat protection. I do not want to unistall this, is this where the blue screen is coming from? I hope not.

Edited by JonnyRocker7, 04 March 2009 - 12:21 PM.


#10 teacup61

teacup61

    Bleepin' Texan!


  • Malware Response Team
  • 17,075 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Wills Point, Texas
  • Local time:06:25 PM

Posted 15 March 2009 - 09:29 AM

Thread has been closed again in HJT forum due to lack of response....again. :thumbsup:
Please make a donation so I can keep helping people just like you.
Every little bit helps! :)
You can even use your credit card! Thank you!

Posted Image


Error reading poptart in Drive A: Delete kids y/n?

#11 DaChew

DaChew

    Visiting Alien


  • Members
  • 10,317 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:millenium falcon and rockytop
  • Local time:07:25 PM

Posted 15 March 2009 - 09:44 AM

DC power supply:

Wattage
305 W


Power Supply : 300 Watt or greater power supply.


cutting it awfully close
Chewy

No. Try not. Do... or do not. There is no try.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users