|
I would like some help from people who are savvy with computer parts
|
|
Topic Started: Nov 15 2015, 10:47 PM (7,223 Views)
|
|
Axiomatically Prodigious
|
Dec 3 2015, 12:31 AM
Post #151
|
- Posts:
- 2,433
- Group:
- Saiyan Elite
- Member
- #8,939
- Joined:
- January 29, 2013
- Gender
- Male
- Favourite Anime
- DragonBall [Z, S, GT], Cowboy Bebop, Trigun, Gangsta, Steins;Gate, Berserk, Tokyo Ghoul
- What Browser do you use?
- Google Chrome
- Favourite Manga
- DragonBall [Z, S], Legend of Zelda
|
Here is what that log states. Please note that it's somewhat lengthy. I also deleted that experience file thing.
Spoiler: click to toggle 030201 (0844) - winsat\logging.cpp:0815: --- START 2009\7\13 22:08:30 PM --- 030232 (0844) - winsat\main.cpp:4301: Command Line = "D:\Windows\system32\winsat.exe" moobe -cancelevent 849bd0b4-8fa1-4e71-8c56-8fdbbf2e34d1 -moobegoevent 27423f94-1309-49e2-9e93-e31a7cd77d2f 030232 (0844) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured 030357 (0844) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=TRUE. 030420 (0844) - winsat\main.cpp:4585: Watch dog system enabled 030420 (0844) - winsat\main.cpp:4592: Main watch dog timer set to 60.0 seconds 030638 (0844) - winsat\main.cpp:2505: > DWM not running. 031746 (0844) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e' 031761 (0844) - winsat\main.cpp:2793: > power policy saved. 031886 (0844) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c' 031902 (0844) - winsat\main.cpp:2814: > power policy set to maximum. 032307 (0844) - d3d\dx9misc.cpp:1030: HRESULT = 8876086a 032323 (0844) - d3d\dx9misc.cpp:1030: Error: Unable to create the D3D device 032323 (0844) - d3d\dx9misc.cpp:1030: Error: Unable to check the capabilities of the video card because a d3d device could not be created 032463 (0844) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance 032463 (0844) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=TRUE RanOverTs=FALSE RanOnbatteries=FALSE 032479 (0844) - winsat\main.cpp:1775: > Run Assessment features 033009 (0844) - winsat\main.cpp:1775: > Run Assessment dwm -aname DWM -time 10 -fbc 10 -disp off -normalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock 033150 (0844) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment. 033446 (0844) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0 033462 (0844) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS 033524 (0844) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0 033540 (0844) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability 033540 (0844) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0 033571 (0844) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=TRUE RanOverTs=FALSE RanOnbatteries=FALSE 033680 (0844) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability 033696 (0844) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0 033696 (0844) - common\winsatutilities.cpp:1382: cannot access the winast API registry key; 2 The system cannot find the file specified. 033789 (0844) - winsat\main.cpp:2339: > Finalized MOOBE key 033836 (0844) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e' 033836 (0844) - winsat\main.cpp:2855: > Power state restored. 033852 (0844) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache. 033945 (0844) - winsat\main.cpp:2899: INFO: DwmpRestartComposition() did not return OK! 033961 (0844) - winsat\watchdog.cpp:0311: Watch dog system shutdown 033977 (0844) - winsat\main.cpp:4909: > exit value = 0.
014820 (0836) - winsat\logging.cpp:0815: --- START 2015\12\1 21:30:37 PM --- 014820 (0836) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" moobe -cancelevent aa712c63-1811-49d1-bd64-2dd097702b3c -moobegoevent 94914432-a0d3-4a90-a6dc-86d185df455e 014835 (0836) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured 014835 (0836) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=TRUE. 014882 (0836) - winsat\main.cpp:4585: Watch dog system enabled 014882 (0836) - winsat\main.cpp:4592: Main watch dog timer set to 60.0 seconds 014882 (0836) - winsat\main.cpp:2505: > DWM not running. 015100 (0836) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e' 015100 (0836) - winsat\main.cpp:2793: > power policy saved. 015116 (0836) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c' 015116 (0836) - winsat\main.cpp:2814: > power policy set to maximum. 015381 (0836) - d3d\dx9misc.cpp:1030: HRESULT = 8876086a 015381 (0836) - d3d\dx9misc.cpp:1030: Error: Unable to create the D3D device 015381 (0836) - d3d\dx9misc.cpp:1030: Error: Unable to check the capabilities of the video card because a d3d device could not be created 015381 (0836) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance 015381 (0836) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=TRUE RanOverTs=FALSE RanOnbatteries=FALSE 015381 (0836) - winsat\main.cpp:1775: > Run Assessment features 015459 (0836) - winsat\main.cpp:1775: > Run Assessment dwm -aname DWM -time 10 -fbc 10 -disp off -normalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock 015522 (0836) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment. 015646 (0836) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0 015646 (0836) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS 015662 (0836) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0 015662 (0836) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability 015662 (0836) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0 015662 (0836) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=TRUE RanOverTs=FALSE RanOnbatteries=FALSE 015693 (0836) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability 015693 (0836) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0 015693 (0836) - common\winsatutilities.cpp:1388: The error count is zero becuase the TaskErrorCount value does not exist. 015693 (0836) - winsat\main.cpp:2339: > Finalized MOOBE key 015709 (0836) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e' 015709 (0836) - winsat\main.cpp:2855: > Power state restored. 015709 (0836) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache. 015709 (0836) - winsat\main.cpp:2899: INFO: DwmpRestartComposition() did not return OK! 015709 (0836) - winsat\watchdog.cpp:0311: Watch dog system shutdown 015709 (0836) - winsat\main.cpp:4909: > exit value = 0.
533024 (3532) - winsat\logging.cpp:0815: --- START 2015\12\2 17:03:03 PM --- 533024 (3532) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" formal -cancelevent 13acb8f3-9910-4f0c-8ee9-b02cc47570fd 533024 (3532) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured 533024 (3532) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=FALSE. 533071 (3532) - winsat\main.cpp:4585: Watch dog system enabled 533071 (3532) - winsat\main.cpp:4600: Main watch dog timer set to 600.0 seconds 533164 (3532) - winsat\main.cpp:2505: > DWM not running. 533164 (3532) - winsat\main.cpp:2470: > EMD service will be restored on exit. 533180 (3532) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e' 533180 (3532) - winsat\main.cpp:2793: > power policy saved. 533195 (3532) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c' 533195 (3532) - winsat\main.cpp:2814: > power policy set to maximum. 534007 (3532) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance 534007 (3532) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE 534007 (3532) - winsat\main.cpp:1775: > Run Assessment features 534069 (3532) - winsat\main.cpp:1775: > Run Assessment dwm -aname DWM -time 10 -fbc 10 -disp off -normalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock 546377 (3532) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 115972000 546377 (3532) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS 546377 (3532) - winsat\main.cpp:1775: > Run Assessment d3d -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1) 552134 (3532) - winsat\main.cpp:1775: > Run Assessment d3d -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1) 557890 (3532) - winsat\main.cpp:1775: > Run Assessment d3d -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3 565160 (3532) - winsat\main.cpp:1775: > Run Assessment d3d -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3 571166 (3532) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
497393 (3864) - winsat\logging.cpp:0815: --- START 2015\12\2 17:19:40 PM --- 497393 (3864) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\WinSat.exe" features -xml features.xml 497393 (3864) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured 497393 (3864) - winsat\main.cpp:2505: > DWM not running. 497409 (3864) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e' 497409 (3864) - winsat\main.cpp:2793: > power policy saved. 497424 (3864) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c' 497424 (3864) - winsat\main.cpp:2814: > power policy set to maximum. 497721 (3864) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance 497721 (3864) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=FALSE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE 497721 (3864) - winsat\main.cpp:1775: > Run Assessment features 497799 (3864) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0 497799 (3864) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e' 497799 (3864) - winsat\main.cpp:2855: > Power state restored. 497799 (3864) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache. 497814 (3864) - winsat\main.cpp:4909: > exit value = 0.
497861 (1816) - winsat\logging.cpp:0815: --- START 2015\12\2 17:19:40 PM --- 497861 (1816) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\WinSat.exe" features -xml features.xml 497861 (1816) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured 497861 (1816) - winsat\main.cpp:2505: > DWM not running. 498235 (1816) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e' 498235 (1816) - winsat\main.cpp:2793: > power policy saved. 498251 (1816) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c' 498251 (1816) - winsat\main.cpp:2814: > power policy set to maximum. 498516 (1816) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance 498516 (1816) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=FALSE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE 498516 (1816) - winsat\main.cpp:1775: > Run Assessment features 498579 (1816) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0 498594 (1816) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e' 498594 (1816) - winsat\main.cpp:2855: > Power state restored. 498594 (1816) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache. 498594 (1816) - winsat\main.cpp:4909: > exit value = 0.
682597 (3672) - winsat\logging.cpp:0815: --- START 2015\12\2 17:22:45 PM --- 682597 (3672) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" formal -cancelevent f92b2721-4b2b-4b8e-9530-a41375f86b49 682613 (3672) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured 682613 (3672) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=FALSE. 682660 (3672) - winsat\main.cpp:4585: Watch dog system enabled 682660 (3672) - winsat\main.cpp:4600: Main watch dog timer set to 600.0 seconds 682769 (3672) - winsat\main.cpp:2505: > DWM not running. 682769 (3672) - winsat\main.cpp:2470: > EMD service will be restored on exit. 682878 (3672) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e' 682894 (3672) - winsat\main.cpp:2793: > power policy saved. 682894 (3672) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c' 682894 (3672) - winsat\main.cpp:2814: > power policy set to maximum. 683721 (3672) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance 683721 (3672) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE 683721 (3672) - winsat\main.cpp:1775: > Run Assessment features 683767 (3672) - winsat\main.cpp:1775: > Run Assessment dwm -aname DWM -time 10 -fbc 10 -disp off -normalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock 695124 (3672) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 116177000 695124 (3672) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS 695124 (3672) - winsat\main.cpp:1775: > Run Assessment d3d -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1) 700818 (3672) - winsat\main.cpp:1775: > Run Assessment d3d -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1) 706559 (3672) - winsat\main.cpp:1775: > Run Assessment d3d -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3 712425 (3672) - winsat\main.cpp:1775: > Run Assessment d3d -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3 718369 (3672) - winsat\main.cpp:1775: > Run Assessment d3d -dx10 -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)
Windows System Assessment Tool has stopped working
Problem signature: Problem Event Name: APPCRASH Application Name: winsat.exe Application Version: 6.1.7600.16385 Application Timestamp: 4a5bc551 Fault Module Name: nvwgf2umx.dll Fault Module Version: 10.18.13.5906 Fault Module Timestamp: 5654a5c9 Exception Code: c000001d Exception Offset: 0000000000a7c6b5 OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Additional Information 1: 56cc Additional Information 2: 56cc85c9c1d4b8d04a12ac0f6367654f Additional Information 3: 7cdf Additional Information 4: 7cdfa4eec1a325a35aaea71cab58d1cf
|

Super Saiyan Rose Many thanks to LNC! <3
See you Space Cowboy...
The Humanoid Typhoon
Not Justin Cook
|
| |
|
FutureProtagonist
|
Dec 3 2015, 12:39 AM
Post #152
|
Quwrof Wrlccywrlir
- Posts:
- 2,545
- Group:
- Member
- Member
- #11,890
- Joined:
- December 5, 2014
- Gender
- Male
- Country
- United States
- Favourite Anime
- FMA: Brotherhood
- What Browser do you use?
- Waterfox
- Favourite Manga
- Soul Eater
|
Well, I'm honestly not sure. You could try doing a clean install of your display drivers. NVIDIA offers that option during the installation. Did you get the drivers from Windows update or from NVIDIA's website?
It might be a good idea to run a different graphics benchmark, because the problem could be on Windows's side.
This is a small, free benchmark that will stress the GPU and reveal and problems on that end, I use it all the time: http://www.guru3d.com/files-details/download-unigine-heaven-benchmark.html
For a full system stress test, run prime95 at the same time, which is an even smaller application that I use all the time: http://www.mersenne.org/download/#stresstest
|
I love building PCs. If you have any questions about it feel free to ask. I can help you with almost any kind of PC you'd want to build.
Join DBZeta
|
| |
|
Axiomatically Prodigious
|
Dec 3 2015, 12:40 AM
Post #153
|
- Posts:
- 2,433
- Group:
- Saiyan Elite
- Member
- #8,939
- Joined:
- January 29, 2013
- Gender
- Male
- Favourite Anime
- DragonBall [Z, S, GT], Cowboy Bebop, Trigun, Gangsta, Steins;Gate, Berserk, Tokyo Ghoul
- What Browser do you use?
- Google Chrome
- Favourite Manga
- DragonBall [Z, S], Legend of Zelda
|
I installed the GPU drivers straight from Nvidia. I opted for the restore everything to default before installation and update. I'll go ahead and do that test now.
|

Super Saiyan Rose Many thanks to LNC! <3
See you Space Cowboy...
The Humanoid Typhoon
Not Justin Cook
|
| |
|
FutureProtagonist
|
Dec 3 2015, 12:49 AM
Post #154
|
Quwrof Wrlccywrlir
- Posts:
- 2,545
- Group:
- Member
- Member
- #11,890
- Joined:
- December 5, 2014
- Gender
- Male
- Country
- United States
- Favourite Anime
- FMA: Brotherhood
- What Browser do you use?
- Waterfox
- Favourite Manga
- Soul Eater
|
You could also try installing some older drivers, sometimes updates can break things.
Just enter your specs, and a list of drivers old and new will appear:
http://www.geforce.com/drivers
|
I love building PCs. If you have any questions about it feel free to ask. I can help you with almost any kind of PC you'd want to build.
Join DBZeta
|
| |
|
Axiomatically Prodigious
|
Dec 3 2015, 12:53 AM
Post #155
|
- Posts:
- 2,433
- Group:
- Saiyan Elite
- Member
- #8,939
- Joined:
- January 29, 2013
- Gender
- Male
- Favourite Anime
- DragonBall [Z, S, GT], Cowboy Bebop, Trigun, Gangsta, Steins;Gate, Berserk, Tokyo Ghoul
- What Browser do you use?
- Google Chrome
- Favourite Manga
- DragonBall [Z, S], Legend of Zelda
|
On Extreme, these were my results:
FPS: 69.4 Score: 1748 Min FPS: 8.7 Max FPS: 159.3
What does this indicate? Is that good?
Also, no issues arose from Windows. Does this mean everything is working correctly?
|

Super Saiyan Rose Many thanks to LNC! <3
See you Space Cowboy...
The Humanoid Typhoon
Not Justin Cook
|
| |
|
FutureProtagonist
|
Dec 3 2015, 12:58 AM
Post #156
|
Quwrof Wrlccywrlir
- Posts:
- 2,545
- Group:
- Member
- Member
- #11,890
- Joined:
- December 5, 2014
- Gender
- Male
- Country
- United States
- Favourite Anime
- FMA: Brotherhood
- What Browser do you use?
- Waterfox
- Favourite Manga
- Soul Eater
|
Looks right for a 970, and the fact that it made it all the way through the test is the important part (means the PSU and GPU are almost certainly working fine). I'd say, besides those few issues you mentioned, you should be good to go.
Generally GPU issues will result in a driver crash "display driver has stopped responding", and PSUs will generally shut down the computer if they're stressed too much.
If you really want to do a full acid test, turn on heaven (no need to actually run the benchmark, just let the scenes run) and run the prime95 torture test, both for a decent amount of time (30 minutes, couple of hours). If that passes, without anything crashing that should rule out any hardware issues, but I'd say you're probably in the clear for that by now.
|
I love building PCs. If you have any questions about it feel free to ask. I can help you with almost any kind of PC you'd want to build.
Join DBZeta
|
| |
|
Axiomatically Prodigious
|
Dec 3 2015, 01:05 AM
Post #157
|
- Posts:
- 2,433
- Group:
- Saiyan Elite
- Member
- #8,939
- Joined:
- January 29, 2013
- Gender
- Male
- Favourite Anime
- DragonBall [Z, S, GT], Cowboy Bebop, Trigun, Gangsta, Steins;Gate, Berserk, Tokyo Ghoul
- What Browser do you use?
- Google Chrome
- Favourite Manga
- DragonBall [Z, S], Legend of Zelda
|
The fact that I can watch a stream on source quality, do both of those tests, and still be able to browse the forum is insane. Lol....
Ok, I ran the test for 15 minutes. Nothing crashed. Now what?
Actually, I'll run the index thing again.
-It crashed at the Direct3D batch assessment.
-I rolled back the GPU driver and installed another one from 11/9/15. Same thing keeps happening with that Windows whatever crap error.
|

Super Saiyan Rose Many thanks to LNC! <3
See you Space Cowboy...
The Humanoid Typhoon
Not Justin Cook
|
| |
|
FutureProtagonist
|
Dec 3 2015, 01:35 AM
Post #158
|
Quwrof Wrlccywrlir
- Posts:
- 2,545
- Group:
- Member
- Member
- #11,890
- Joined:
- December 5, 2014
- Gender
- Male
- Country
- United States
- Favourite Anime
- FMA: Brotherhood
- What Browser do you use?
- Waterfox
- Favourite Manga
- Soul Eater
|
Windows desktop manager is still crashing?
Try this, see if you get the same error as before: http://www.microsoft.com/en-us/download/details.aspx?id=35&wt.mc_id=mscom_en_us_search_mssuggests_131z4enus22051
Another possible solution is to try and disable aero, see if the crashes persist.
You could also try running chkdsk: CHKDSK /R through command prompt.
Or booting into safe mode, and seeing if crashes then.
|
I love building PCs. If you have any questions about it feel free to ask. I can help you with almost any kind of PC you'd want to build.
Join DBZeta
|
| |
|
Axiomatically Prodigious
|
Dec 3 2015, 01:54 AM
Post #159
|
- Posts:
- 2,433
- Group:
- Saiyan Elite
- Member
- #8,939
- Joined:
- January 29, 2013
- Gender
- Male
- Favourite Anime
- DragonBall [Z, S, GT], Cowboy Bebop, Trigun, Gangsta, Steins;Gate, Berserk, Tokyo Ghoul
- What Browser do you use?
- Google Chrome
- Favourite Manga
- DragonBall [Z, S], Legend of Zelda
|
The installer determined that I'm on the latest version. :/
Tell me how to disable aero.
I did the chkdsk earlier with the rf scannow. It gave me some sort of error.
I'll try the safe mode in a bit.
(Watching a movie real quick... I know, I know... priorities....lol!)
|

Super Saiyan Rose Many thanks to LNC! <3
See you Space Cowboy...
The Humanoid Typhoon
Not Justin Cook
|
| |
|
FutureProtagonist
|
Dec 3 2015, 02:11 AM
Post #160
|
Quwrof Wrlccywrlir
- Posts:
- 2,545
- Group:
- Member
- Member
- #11,890
- Joined:
- December 5, 2014
- Gender
- Male
- Country
- United States
- Favourite Anime
- FMA: Brotherhood
- What Browser do you use?
- Waterfox
- Favourite Manga
- Soul Eater
|
To disable aero, right click the desktop, click "personalize", then the Windows 7 basic theme.
Did chkdsk fix the error? If not you should be able to run it before windows starts.
|
I love building PCs. If you have any questions about it feel free to ask. I can help you with almost any kind of PC you'd want to build.
Join DBZeta
|
| |
|
Axiomatically Prodigious
|
Dec 3 2015, 02:24 AM
Post #161
|
- Posts:
- 2,433
- Group:
- Saiyan Elite
- Member
- #8,939
- Joined:
- January 29, 2013
- Gender
- Male
- Favourite Anime
- DragonBall [Z, S, GT], Cowboy Bebop, Trigun, Gangsta, Steins;Gate, Berserk, Tokyo Ghoul
- What Browser do you use?
- Google Chrome
- Favourite Manga
- DragonBall [Z, S], Legend of Zelda
|
I always have that set on classic.
I'll run the chkdsk again.
-Chkdsk reported 0 bad files. About to boot up in safe mode now.
-Safe mode did NOT display that error...... So, what is different in safe mode as opposed to a normal boot up with the classic display?
-I also did the Aero and transparency display scan from the Personalization menu... Nothing came up...
|

Super Saiyan Rose Many thanks to LNC! <3
See you Space Cowboy...
The Humanoid Typhoon
Not Justin Cook
|
| |
|
FutureProtagonist
|
Dec 3 2015, 03:37 AM
Post #162
|
Quwrof Wrlccywrlir
- Posts:
- 2,545
- Group:
- Member
- Member
- #11,890
- Joined:
- December 5, 2014
- Gender
- Male
- Country
- United States
- Favourite Anime
- FMA: Brotherhood
- What Browser do you use?
- Waterfox
- Favourite Manga
- Soul Eater
|
When exactly does the error happen?
Safe mode is a minimal boot, so only the stuff windows needs to run, and a generic display driver, which is why you probably had a low resolution in safe mode.
You may want to do this:- Quote:
-
Click the Start button and type "aero". Then click on “Find and fix problems with transparency and other visual effects”. http://www.tomshardware.com/faq/id-2066988/enable-window-transparency-aero-windows.html
You may also be able to simply disable DWM: http://www.howtogeek.com/howto/windows-vista/what-is-dwmexe-and-why-is-it-running/
|
I love building PCs. If you have any questions about it feel free to ask. I can help you with almost any kind of PC you'd want to build.
Join DBZeta
|
| |
|
Axiomatically Prodigious
|
Dec 3 2015, 03:38 AM
Post #163
|
- Posts:
- 2,433
- Group:
- Saiyan Elite
- Member
- #8,939
- Joined:
- January 29, 2013
- Gender
- Male
- Favourite Anime
- DragonBall [Z, S, GT], Cowboy Bebop, Trigun, Gangsta, Steins;Gate, Berserk, Tokyo Ghoul
- What Browser do you use?
- Google Chrome
- Favourite Manga
- DragonBall [Z, S], Legend of Zelda
|
So, then there has to be an issue with the GPU driver?
It occurs the instant that I log into my desktop when the computer is turned on.
That's what I did. No errors were retrieved. It's also in the Personalization screen at the bottom.
-Actually, it would have to be a GPU driver because the error occurs during the GPU testing of the Experience Index test. What should I do to fix this? I've tried an older firmware, which is what I'm on now. From 11/9/15.
|

Super Saiyan Rose Many thanks to LNC! <3
See you Space Cowboy...
The Humanoid Typhoon
Not Justin Cook
|
| |
|
FutureProtagonist
|
Dec 3 2015, 03:48 AM
Post #164
|
Quwrof Wrlccywrlir
- Posts:
- 2,545
- Group:
- Member
- Member
- #11,890
- Joined:
- December 5, 2014
- Gender
- Male
- Country
- United States
- Favourite Anime
- FMA: Brotherhood
- What Browser do you use?
- Waterfox
- Favourite Manga
- Soul Eater
|
As I said, you may be able to disable DWM: http://www.howtogeek.com/howto/windows-vista/what-is-dwmexe-and-why-is-it-running/
As for the drivers, you could uninstall it from device manager, then reinstall from scratch, or you could simply try another one.
It's a difficult issue. You could try getting a driver from Windows update (won't be the latest one, but it might be more compatible). It should do this if you uninstall the drivers (and check delete driver software) from the device manager.
|
I love building PCs. If you have any questions about it feel free to ask. I can help you with almost any kind of PC you'd want to build.
Join DBZeta
|
| |
|
Axiomatically Prodigious
|
Dec 3 2015, 03:51 AM
Post #165
|
- Posts:
- 2,433
- Group:
- Saiyan Elite
- Member
- #8,939
- Joined:
- January 29, 2013
- Gender
- Male
- Favourite Anime
- DragonBall [Z, S, GT], Cowboy Bebop, Trigun, Gangsta, Steins;Gate, Berserk, Tokyo Ghoul
- What Browser do you use?
- Google Chrome
- Favourite Manga
- DragonBall [Z, S], Legend of Zelda
|
Alright, so I just disabled the Windows Manager thing from starting up. I did NOT receive the error message upon restart. However, the Experience Index still fails at the "Running the Direct3D 10 Batch Assessment." I'm going to uninstall from device manager and see what happens.
|

Super Saiyan Rose Many thanks to LNC! <3
See you Space Cowboy...
The Humanoid Typhoon
Not Justin Cook
|
| |
| 1 user reading this topic (1 Guest and 0 Anonymous)
|