Tease

Another thing, your using the newest 186 driver on a dinosaur card. The 186 driver itself has issues even on new cards. Cards of that age often do better on a older driver as odd as that sounds. In this case though I'd first roll back to the 185s (stable) doing a clean uninstall of the current driver. This will also accomplish what TJ is suggesting.

The reason I hesitate is that it involves registry editing work. Yeah yeah I know, Microsoft is now quick to send us to poke in the registry. Guess I'm still a little old-school in my sentiment that poking in the registry is a dangerous endeavor. Something about the idea of computer illiterates playing with regedit makes me shudder, lmao!

I'm absolutely in love with win7, but then again I'm a beta-tester at heart. If code doesnt have something I can break I get bored! However now that I've patched the "driver not responding" bug (hopefully for server 2008/vista as well) my system is rock solid. Its substantially faster than my vista install as well. love love love it is all I can say. :P

Like everything in live YMMV: Your Mileage May Vary

Just an update.

I'm still on the 181x driver that was crashing and bluescreening.

However, I have achieved solid stability.

This came using the patch/workaround that I'm currently trialing for Vista 13/14 errors. Because its an ugly little workaround, and potentially risky, I'm just not ready to openly circulate it to the masses. Hopefully later this week though.

Issue currently resolved on my machine (Win7, 181x driver, 8800gt) & a VG mates (Vista Ult, 178x driver, 9800 GX2). My assumption yet untested is that it will probably work on the 2008 OS as well since its fairly band-aid style and they share the problem. Should know more this week I hope.

I'm going to try to roll to the 185 driver soon and see if my patch holds.

Thanks everyone for their feedback.

I'm looking for someone with a Vista/Win7 PC with Nvidia video card that is still fighting with the Error 13/14 and is not afraid to make some somewhat experimental levels system changes (non-hardware).

I have made the changes on my own PC, but I need to see them on other hardware/software combinations before I can call them recommended, or even suggested.

If anyone feels like contributing to testing please be in touch.

Tease

Assuming its able to boot onto the hard drive normally, the board lcd code of FF, on 99% of all boards still stands for "that fugger failed". Something has been amiss for a while if you've been getting FF as a board-code. Google for your bio type and post-code chart to verify this. (Some boards will still toss an FF if the HD is not attached and/or bootable as the bios expects to hand off to a drive.) Half a bazillion sub-steps in the POST procedure could be triggering an FF display, not all of which are hugely important.

99% odds that's an overheating and/or dying video card.

Ack, I totally missed the dual video setting houtex. Definitely take that out of the question. The video card setting needs to be in single-monitor performance (I think thats it) mode for game handling. The game also has issues with SLI compatability and although many get it to work its not supported I dont believe.

I think he rolled drivers back to the 169's hoping it was the error 13/14 bug, since thats the driver it calls for testing.

Start with the common solutions thread stickied in this forum. Then post your hijack this and cohhelper logs (link in my sig). Probably a driver issue most likely.

Bo, please go to your control panel, administrative tools, Event Viewer, Windows Logs sub-section, System subsection. Scroll back to immediately before your most recent crash and tell me what you have of interest that may be flagged Warning/Error/Critical. Also be sure that in the System Properties window (right click on my computer, select Properties), Advanced tab, Startup & Recovery button, that you have "Write an event to the system log" checked, under system failure. (Your exact verbage may be a little different but similar.)

This doesn't sound like the error 13/14 bug in general, and your also right the hotfix doesn't apply to you because your running SP2 which includes it. Since its not that error, using the 169 drivers probably arent benefiting you, and I'd upgrade to the 185s. (The 186's have some hiccups on occasion).

Also, install a copy of (free) speedfan, and keep an eye on both your CPU and GPU temps, and post them back here for us both after the system has been idle and non-gaming for some time and after you've had the system under load (gaming) a while.

I notice that several of your system drives have very little free-space, and that can make windows have hiccups. Something you may want to resolve. Also, make sure your board/chipset drivers are up-to-date. Hmm, you have a heck of a lot of stuff running at start-up that could be chewing up system resources in odd ways, I'd suggest reducing that list substantially at least temporarily and preferably permanently but thats just good system mechanics.

Fun bug!

Thanks houtex, that's actually the method I used. Basically anything that works on a Vista box works on Win7 which is essentially the difference between Win98 and Win98b. For the most part Win7 is "Vista Done Right"

If I decide to attempt to roll onto the old Vista 169 drivers, which could prove tricky, I will double-check in Driver Sweeper to see if I missed any video drivers. Pretty sure I got them all.

Appreciate all the feedback guys, please keep it coming, eventually we'll puzzle this one out!

Sadly cyber, your advice didn't help me

I finally rolled back once more to a 181 driver. Now I don't get the PREVIOUS blue screen but I'm back with the infamous "driver stopped responding" error AND if i lock up more than one account that way I may recover from it and then blue-screen (the identified file is then nvlddmkm.sys classic of that error). Somehow this is all related.

So to recap:

186 = driver has stopped responding (could also be blue-screening I honestly didn't stay there long when others noted the 186's had issues)
185 = different blue screens
181 = driver has stopped responding AND bluescreens.

At this point I'm considering taking some suggestions in the winprogger.com site, linked from nvidias site and see if by tweaking a few settings I can at least mask it in a way it doesn't produce a different crash (or heat spike). I'm still torn if I want to roll back into the 170 driver series although I may have to.

Might wanna start with the common solutions thread and also posting your cohhelper and hijack this log (see my sig).

Bright_Shadow is right, its the Captcha saying you spent too much time on the page. Your unlikely to be billed for the one that expired. Be quick on the page so the captcha doesnt fail and it should go through correctly.

Thanks cybermitheral, I will certainly give it a try. I THINK however its happened on the first close sometimes rather than the second as well, but I will certainly be keeping an eye on this.

Somethings I also found:

-------------------------------------------------------------------------
http://msdn.microsoft.com/en-us/library/ms793232.aspx

Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Parameters

The following parameters are displayed on the blue screen.
Parameter Description
1 The exception that caused the bug check
2 The address of the exception record for the exception that caused the bug check
3 The address of the context record for the exception that caused the bug check
4 0

Cause

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

-------------------------------------------------------------------------
http://support.microsoft.com/kb/923187/en-us (Win2003)

A computer that is running an x64-based version of Microsoft Windows Server 2003 may experience a Stop error in the Tcpip.sys file. When this problem occurs, you receive the following error message: Stop 0x0000003B (c0000005, fffffadca82a63d4, fffffadca35fb4f0, 0)
-------------------------------------------------------------------------
http://episteme.arstechnica.com/eve/...m/968001256931

Stack trace:

ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
8ce47ba8 947b1ba1 00000116 85939100 9401d840 nt+0xedf78
8ce47bcc 947b29be 9401d840 00000000 0000000d dxgkrnl+0x8aba1
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
....
....
....
Bugcheck:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 85939100, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 9401d840, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000d, Optional internal context dependent data.
---------------------------------------------------------------------------
Then if I follow Video_TDR_Failure, I wind up with this which is highly interesting from the standpoint that it talks about our infamous "driver as stopped responding" bug in some detail.

http://winprogger.com/?p=36 No clue how or if this relates to what I have going on here, other than its video driver issues again, but its an interesting read for those of us battling this bug.
--------------------------------------------------------------------------

Excellent piece of info as usual Mateo. Definitely. I have a bad habit of forgetting that not everyone has all four /save files already built :P

Here's a for-giggles suggestion, take it or leave it up to you...

Log into the game(s) and set all your graphic settings to minimum. Exit & Close the game.

Then grab the absolute oldest non-beta driver you can find for that card number for your OS. Yeah I'm serious.

Then do a full clean uninstall of the current driver. Some say using Add-Remove Programs stuff is enough, however most of us prefer to use driver sweeper pro from safemode to fully remove a driver.

Then install the new-to-you old driver.

Log into the game and play a while. (Yeah I know minimum isn't pretty, do some WW/BM work or something if you think its too ugly.)

Post your results. Odds are no-change, minor chance of a variant. I suggest this because I've seen something vaguely similar before from a driver even though it shouldn't happen.

Take with 2 grains of salt and call me in the morning :P

Update:

The BSOD includes dxgmms1.sys. That's a different file than was being listed by vista although I've lost my notebook that told me which one THAT was. Whats interesting to note is that sometimes under vista I got a BSOD that was IRQL_NOT_LESS_OR_EQUAL (I don't think it said driver before it, could be wrong though) and much much more rarely "PAGE_FAULT_IN_NONPAGED_AREA" and googling shows that dxgmms1.sys is related to the error "DRIVER_IRQL_NOT_LESS_OR_EQUAL"

So, that may tie both BSOD variants I was getting under Vista into this single BSOD variant I'm getting now.

I probably need to dig through the minidumps produced by the BSOD but I dont know how to do that... hmmmm. Off to do more reading...

One other thing to note is that under VISTA I seemed to be hitting BSOD more while actually actively gaming for prolonged periods. Now I seem to hit it more after having gamed for a period and then trying to close the second account window.

For example tonight I had left 2 accounts logged in and zoned into base. When I came home both had at some point lost connection to server (not uncommon my isp is less than perfect) leaving both at the login screen. I closed the first one with no problem and the instant I closed the second one, BSOD. This sounds like something isn't going right in freeing up resources maybe? I don't really know. I also cant say FOR SURE that it wouldn't happen under extensive gaming (without closing the game) as frankly since I got back from being mostly gone from the game, I don't have as much game time available to me as I did. I'm certainly going to test the theory over double-xp weekend but I'd REALLY love to have this solved before then.

Edited to add: There's only a single (forum) page I'm finding that includes system_service_exception 0x3b and dxgmm1.sys and it requires translation, here it is if you care to have a look and I dont find a whole lot useful out of it sadly.

web page

This started under Vista and has now re-arrived on my Win7 RC1 installation (same machine and hardware).

While gaming, usually multi-account, windowed-style, after I've been gaming a bit, I throw a BSOD. Oddly I havent had this happen outside of using COX and it took me away from the game for a while due to frustration.

memtest86+ v2.11 says the memory (8 gigs matched GEIL ram) tests clean on 6 passes.

I originally thought under Win7 the problem was gone, although I had returned to having the "driver stopped responding error" under the 186 driver. The driver stopped error happened fairly early and I'm unable to say for sure whether or not this BSOD would have appeared if the game had run longer. I tried uninstallling it directly twice and finally broke out Driver Cleaner Pro to remove it from safemode. Installed the 185 driver and the "driver stopped" error vanished. Infact I thought the system looked really good till I ran some SF's last night, and my system had been in dual-logged mode for a couple hours. I logged out and closed the second account successfully, but as I repeated that with the first account, here came my good ole friend the BSOD.

I've just turned off auto-restart after BSOD so I can more fully capture the error code, but theres what I have from the system logs.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8800553d986, 0xfffff880090dff70, 0x0000000000000000). A dump was saved in: G:\Windows\MEMORY.DMP. Report Id: 071309-24336-01.

I also have several entries of the next error, but they dont directly correspond to the crash. I do think they may be related based on the usual cause though.

The Peer Name Resolution Protocol cloud did not start because the creation of the default identity failed with error code: 0x80630801.

The Peer Name Resolution Protocol service terminated with the following error:
%%-2140993535

Everything I've read on both errors says "ram or video drivers". I have a hard time thinking its ram after that many laps through memtest. If someone has a different utility they'd prefer to see the ram tested with please suggest it! I also think the candidate is most likely video drivers as the only thing I use that stresses the video drivers is COX. Its the only game I play. I could roll back once more, to the 181's, but that's what my Vista installation was on before the reformat with this same error set.

Under the Vista installation the GPU was running closer to 78C which concerned me, but under this new installation, I've been unable to fully stress it higher than 75C. EVGA when called said to keep an eye on it but that it didnt warrant an RMA. It's averaging more like 72C now. The case has loads of airflow and a dual-slot fan sits below the video card to assist. (Some of that heat is the fault of the board which has a northbridge fan that blows right on the video card... bad idea.. EVGA 750i SLI board). CPU runs about 42C under full load and about 30C from minimal load. I hate the stock heatsink and hope to replace it soon, it has a nasty habit of one of the four turn-lockdowns vibrating lose.

Okay specs:

Logfile of Trend Micro HijackThis v2.0.2
Scan saved at 5:44:44 PM, on 7/14/2009
Platform: Unknown Windows (WinNT 6.01.3004)
MSIE: Internet Explorer v8.00 (8.00.7100.0000)
Boot mode: Normal

Running processes:
G:\Program Files (x86)\Yahoo!\Messenger\YahooMessenger.exe
G:\Program Files (x86)\Switcher\Switcher.exe
C:\Program Files (x86)\Moonphase\moon.exe
G:\Program Files (x86)\Avira\AntiVir Desktop\avgnt.exe
G:\Program Files (x86)\Mozilla Firefox\firefox.exe
E:\City of Heroes\CityOfHeroes.exe
E:\City of Heroes\CityOfHeroes.exe
G:\Program Files (x86)\Trend Micro\HijackThis\HijackThis.exe

R1 - HKCU\Software\Microsoft\Internet Explorer\Main,Search Page = http://go.microsoft.com/fwlink/?LinkId=54896
R0 - HKCU\Software\Microsoft\Internet Explorer\Main,Start Page = http://pandora.com/#/
R1 - HKLM\Software\Microsoft\Internet Explorer\Main,Default_Page_URL = http://go.microsoft.com/fwlink/?LinkId=69157
R1 - HKLM\Software\Microsoft\Internet Explorer\Main,Default_Search_URL = http://go.microsoft.com/fwlink/?LinkId=54896
R1 - HKLM\Software\Microsoft\Internet Explorer\Main,Search Page = http://go.microsoft.com/fwlink/?LinkId=54896
R0 - HKLM\Software\Microsoft\Internet Explorer\Main,Start Page = http://go.microsoft.com/fwlink/?LinkId=69157
R0 - HKLM\Software\Microsoft\Internet Explorer\Search,SearchAssistant =
R0 - HKLM\Software\Microsoft\Internet Explorer\Search,CustomizeSearch =
R0 - HKLM\Software\Microsoft\Internet Explorer\Main,Local Page = G:\Windows\SysWOW64\blank.htm
R0 - HKCU\Software\Microsoft\Internet Explorer\Toolbar,LinksFolderName =
F2 - REG:system.ini: UserInit=userinit.exe
O2 - BHO: Groove GFS Browser Helper - {72853161-30C5-4D22-B7F9-0BBC1D38A37E} - G:\PROGRA~2\MICROS~1\Office12\GR469A~1.DLL
O4 - HKLM\..\Run: [avgnt] "G:\Program Files (x86)\Avira\AntiVir Desktop\avgnt.exe" /min
O4 - HKCU\..\Run: [Messenger (Yahoo!)] "G:\PROGRA~2\Yahoo!\MESSEN~1\YAHOOM~1.EXE" -quiet
O4 - HKCU\..\Run: [Switcher] "G:\Program Files (x86)\Switcher\Switcher.exe" /quiet
O4 - HKCU\..\Run: [RESTART_STICKY_NOTES] G:\Windows\System32\StikyNot.exe
O4 - HKUS\S-1-5-19\..\Run: [Sidebar] %ProgramFiles%\Windows Sidebar\Sidebar.exe /autoRun (User 'LOCAL SERVICE')
O4 - HKUS\S-1-5-19\..\RunOnce: [mctadmin] G:\Windows\System32\mctadmin.exe (User 'LOCAL SERVICE')
O4 - HKUS\S-1-5-20\..\Run: [Sidebar] %ProgramFiles%\Windows Sidebar\Sidebar.exe /autoRun (User 'NETWORK SERVICE')
O4 - HKUS\S-1-5-20\..\RunOnce: [mctadmin] G:\Windows\System32\mctadmin.exe (User 'NETWORK SERVICE')
O4 - Startup: MoonPhase.lnk = C:\Program Files (x86)\Moonphase\moon.exe
O8 - Extra context menu item: E&xport to Microsoft Excel - res://G:\PROGRA~2\MICROS~1\Office12\EXCEL.EXE/3000
O9 - Extra button: Send to OneNote - {2670000A-7350-4f3c-8081-5663EE0C6C49} - G:\PROGRA~2\MICROS~1\Office12\ONBttnIE.dll
O9 - Extra 'Tools' menuitem: S&end to OneNote - {2670000A-7350-4f3c-8081-5663EE0C6C49} - G:\PROGRA~2\MICROS~1\Office12\ONBttnIE.dll
O9 - Extra button: Research - {92780B25-18CC-41C8-B9BE-3C9C571A8263} - G:\PROGRA~2\MICROS~1\Office12\REFIEBAR.DLL
O13 - Gopher Prefix:
O18 - Protocol: grooveLocalGWS - {88FED34C-F0CA-4636-A375-3CB6248B04CD} - G:\PROGRA~2\MICROS~1\Office12\GRA32A~1.DLL
O23 - Service: @%SystemRoot%\system32\Alg.exe,-112 (ALG) - Unknown owner - G:\Windows\System32\alg.exe (file missing)
O23 - Service: Avira AntiVir Scheduler (AntiVirSchedulerService) - Avira GmbH - G:\Program Files (x86)\Avira\AntiVir Desktop\sched.exe
O23 - Service: Avira AntiVir Guard (AntiVirService) - Avira GmbH - G:\Program Files (x86)\Avira\AntiVir Desktop\avguard.exe
O23 - Service: Apple Mobile Device - Apple Inc. - G:\Program Files (x86)\Common Files\Apple\Mobile Device Support\bin\AppleMobileDeviceService.exe
O23 - Service: Bonjour Service - Apple Inc. - G:\Program Files (x86)\Bonjour\mDNSResponder.exe
O23 - Service: @%SystemRoot%\system32\efssvc.dll,-100 (EFS) - Unknown owner - G:\Windows\System32\lsass.exe (file missing)
O23 - Service: @%systemroot%\system32\fxsresm.dll,-118 (Fax) - Unknown owner - G:\Windows\system32\fxssvc.exe (file missing)
O23 - Service: iPod Service - Apple Inc. - G:\Program Files (x86)\iPod\bin\iPodService.exe
O23 - Service: @keyiso.dll,-100 (KeyIso) - Unknown owner - G:\Windows\system32\lsass.exe (file missing)
O23 - Service: @comres.dll,-2797 (MSDTC) - Unknown owner - G:\Windows\System32\msdtc.exe (file missing)
O23 - Service: @%SystemRoot%\System32\netlogon.dll,-102 (Netlogon) - Unknown owner - G:\Windows\system32\lsass.exe (file missing)
O23 - Service: NVIDIA Display Driver Service (nvsvc) - Unknown owner - G:\Windows\system32\nvvsvc.exe (file missing)
O23 - Service: @%systemroot%\system32\psbase.dll,-300 (ProtectedStorage) - Unknown owner - G:\Windows\system32\lsass.exe (file missing)
O23 - Service: @%systemroot%\system32\Locator.exe,-2 (RpcLocator) - Unknown owner - G:\Windows\system32\locator.exe (file missing)
O23 - Service: @%SystemRoot%\system32\samsrv.dll,-1 (SamSs) - Unknown owner - G:\Windows\system32\lsass.exe (file missing)
O23 - Service: @%SystemRoot%\system32\snmptrap.exe,-3 (SNMPTRAP) - Unknown owner - G:\Windows\System32\snmptrap.exe (file missing)
O23 - Service: @%systemroot%\system32\spoolsv.exe,-1 (Spooler) - Unknown owner - G:\Windows\System32\spoolsv.exe (file missing)
O23 - Service: @%SystemRoot%\system32\sppsvc.exe,-101 (sppsvc) - Unknown owner - G:\Windows\system32\sppsvc.exe (file missing)
O23 - Service: @%SystemRoot%\system32\ui0detect.exe,-101 (UI0Detect) - Unknown owner - G:\Windows\system32\UI0Detect.exe (file missing)
O23 - Service: @%SystemRoot%\system32\vaultsvc.dll,-1003 (VaultSvc) - Unknown owner - G:\Windows\system32\lsass.exe (file missing)
O23 - Service: @%SystemRoot%\system32\vds.exe,-100 (vds) - Unknown owner - G:\Windows\System32\vds.exe (file missing)
O23 - Service: @%systemroot%\system32\vssvc.exe,-102 (VSS) - Unknown owner - G:\Windows\system32\vssvc.exe (file missing)
O23 - Service: @%systemroot%\system32\wbengine.exe,-104 (wbengine) - Unknown owner - G:\Windows\system32\wbengine.exe (file missing)
O23 - Service: @%Systemroot%\system32\wbem\wmiapsrv.exe,-110 (wmiApSrv) - Unknown owner - G:\Windows\system32\wbem\WmiApSrv.exe (file missing)
O23 - Service: @%PROGRAMFILES%\Windows Media Player\wmpnetwk.exe,-101 (WMPNetworkSvc) - Unknown owner - G:\Program Files (x86)\Windows Media Player\wmpnetwk.exe (file missing)

--
End of file - 6419 bytes



---System information gathered by CoH Helper version 0.1.1.7---

DxDiag gathered at July 14, 2009 18:02 (-05:00)
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7100) (7100.winmain_win7rc.090421-1700)
System Manufacturer: EVGA__
System Model: nForce 750i SLI
BIOS: Phoenix - AwardBIOS v6.00PG
Central Processor: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz (2 CPUs), ~3.0GHz
Memory: 8192MB
.Net Memory Report: 5234MB out of 8190MB available
Page File: 12911MB (3467MB currently in use)
C Drive: (ST350032 0AS SCSI Disk Device) 80421MB out of 102614MB (78%) free
E Drive: (ST350032 0AS SCSI Disk Device) 13130MB out of 21034MB (62%) free
F Drive: (ST350032 0AS SCSI Disk Device) 236350MB out of 250796MB (94%) free
G Drive: (ST350032 0AS SCSI Disk Device) 68370MB out of 102494MB (66%) free
D Drive: (ATAPI iHAS120 6 SCSI CdRom Device) zero-size drive
H Drive: (ELBY CLONEDRIVE SCSI CdRom Device) zero-size drive
Windows directory location: G:\Windows
DirectX: DirectX 11
DirectX Diag version: 6.01.7100.0000 (64-bit version)

Display Notes: No problems found.
Sound Notes: No problems found.

No problems found.
Input Notes: No problems found.

Monitor:
Monitor's Max Resolution: (blank)
Video Device Name: NVIDIA GeForce 8800 GT
Manufacturer / Chip: NVIDIA / GeForce 8800 GT
Video Memory: 4080 MB
Driver Version: 8.15.11.8585
Driver Date: 4/30/2009 10:02:00 PM
Driver Language: English

Sound Device Description: Digital Audio (HDMI) (High Definition Audio Device)
Driver File: HdAudio.sys
Driver Version: 6.01.7100.0000
Driver Date: 4/21/2009 11:15:37 PM

Sound Device Description: Digital Audio (S/PDIF) (High Definition Audio Device)
Driver File: HdAudio.sys
Driver Version: 6.01.7100.0000
Driver Date: 4/21/2009 11:15:37 PM


WMI Information
Motherboard Manufacturer: EVGA
Motherboard Model: (empty)
Motherboard Product: nForce 750i SLI
Motherboard Version: 1
BIOS Manufacturer: Phoenix Technologies, LTD
BIOS Name: Phoenix - AwardBIOS v6.00PG
BIOS Version: EVGA - 42302e31
BIOS Release: 20080324000000.000000+000

Registry Information for Current User
Resolution: 1440x838
3D Resolution: 1440x838 (Not using renderscale)
Full Screen: No
Maximized: Yes
Screen Position: 0, 0
Refresh Rate: 60Hz
Vertical Sync Enabled: Yes

Physics Quality: None
Maximum Particles: 100
Max Particle Fill? 10.000
Physics Card Enabled: No

Anti-aliasing: None
Anisotropic Filtering: None
Texture LOD Bias: Crisp
Water Effects: None
Bloom: 1.000 (turned off)
Depth of Field Enabled: No
Desaturation Effects (Sepia) Enabled: No
Shader Detail: Lowest

World Texture Level: Low
Character Texture Level: Medium
World Detail Level (Vis_Scale): 0.500
Entity Detail Level: 0.500
Shadows Enabled: No
Gamma Correction: 1.000
Geometry Buffers (VBOs) Enabled: Yes
Suppression of Extra Player FX Enabled: No
Suppression of FX When Camera Close Enabled: Yes
Close Suppression Range: 3.000
Show Advertisements: Yes

Audio Mode: Performance
3D Audio: No
FX Sound Volume: 0.000
Music Sound Volume: 0.000

Show Advanced Graphics Options: Yes
Overall Graphics Quality: 0.000
Reverse Mouse Buttons: No
Save Login Username: Yes
Transfer Rate: Unknown bytes/second
Current Game Version: 19.20090619.5T2
Installation Directory: E:\City of Heroes

Mod files in the Data directory
.\texture_library\GUI\Icons\Powers has 120 files
.\texture_library\MAPS\city has 1 file
.\texture_library\MAPS\Safeguard has 9 files
.\texture_library\MAPS\sewers has 44 files
.\texture_library\MAPS\static has 33 files
.\texture_library\V_MAPS\Outdoor_Missions has 9 files
.\texture_library\V_MAPS\Static has 14 files
.\texture_library\WORLD\V_COV\Bases\Details\Functi onal\base_tele_arc_aux has 28 files
.\texture_library\WORLD\V_COV\Bases\Details\Functi onal\base_tele_aux has 28 files

So, suggestions on my next course of action in diagnosing this?

Just a note that while on the earliest win7 beta driver, on win7 beta, I was not getting this bug.... it has returned to me on win7 RC1 (with all current updates) under 186.18. Same rig as previous that I had gotten fully stable in vista with after SP2. However I see that I had not come up past the 185's on vista, and that the 186's have known issues, so a driver swap is definitely in order. (Yes, I'm planning to start working backwards on drivers, etc etc, but wanted to post.)

Edited to add: 185 driver solved it.

Vill side...

MM Aggro Control method requires a near-full zone, so 45'ish for success. This is the method we used for success on freedom.

Brute tank method with a skilled team can run a few less people but requires more consistency in team comp, toon builds, and requirements.

http://totalevil.guildportal.com Hope to see you there!

I've been trying to copy my troller to test since yesterday without success. 6/27-6/28

This is a 9xxx series card that hasnt done a driver rollback. On many of the 9xxxx I clearly stated in the guide that even with BOTH the hotfix and the driver rollback sometimes we dont get a clean behavior. Welcome to 9xxx series cards, enjoy your stay :P

Please finish working through the guide, and then post back.

And Zloths right, heck this isnt even vista's issue its a card/driver/game/os combo issue. Ton of variables. My Vista box is solid.

Tease