Windows 10: BSODs whilst gaming

Hi,

I've been getting a few bluescreens and generalh CTDs whilst gaming quite a lot. So far I've replaced the motherboard (though becuase the old one was a dud), replaced the power supply (also dud) and rolled back my graphics drivers to 355.98, I also used DDU to remove the old drivers too.

Any help would be much appreciated.

Attachment 54503

:)

 

Crash whilst gaming

PC crashed whilst gaming (BSOD). Since then, I have been unable to reboot other than in safe mode. Have checked graphics drivers and all seems fine...

Checked event viewer and found the following... completely out of my depth here.

 

PC locksup & freezes whilst gaming

If the problems only started after upgrading your gpu from GTX660 to GTX960 there
may be an issue with

the new card. Just out of curiosity which Nvidia driver are you using ?

- You haven't said if you have monitored the gpu and cpu temps, or if you have tried Clean Boot.- If the problem is with only the one game reinstalling the game may help.

"Dont get me wrong tho i like win10 but im seeing a lot of people on the gaming threads with DirectX 12 GPU & Windows 10 having heaps of issues. because either the game or OS isnt compatibale in some way."

Yes, well unfortunately froums are all about problems, so you are unlikely to read posts from people who

are not having issues. I have close on 200 games from '98 to present. Disk based and download, and

they all run as well on Win10 as they did on Win7.

Not to say I didn't have to stuff around with a few of them at first eg- run the Steam 'verify integrity of game cache'

tool and re set the resolution and a few other things I don't recall atm, but there are no major issues with Win10

other than the dread DRM Blocking malware MS introduced with Win10 that prevents many disk based games from

launching. I don't have a personal problem with this as I've always used noCD fixes with my disk

based games anyway, but I reckon MS has been heartless in not providing an on/off switch for this 'feature',

and worse, not providing a proper error message so people are made to run around in circles trying to get

the 'run as admin' option to work. I have more details on this malware in my post in --this thread--.

- Back on DirectX . I already outlined how DX works above but...

It's a common misconception that Win7/8/8.1 has only DX 11, and Win10 has only DX12.

Win7/8/8.1/10 all have all of the DX - 9,10 and 11 files.

- The following is a list of the Direct X .dll's you will have when the files are up to date.

Go to the Windows / System 32 folder, (and SysWOW64 if you have 64bit).

They are in alphabetical order and will start with d3dx9 - 24 > 43 . Then d3dx10 - 33 > 43 & finally d3dx11 - 42 > 43.

There should also be - d3d9, d3d10 and d3d11 (among others).

These come before the D3Dcompilers - 33>47.

- Win10 currently has only two d3d 12 files. One in System 32, and one in SysWOW64 .

- There are more DX files, but these are most of the graphics related Direct X .dll's

However, a clean Windows install may not have all of the DX files (Win7 didn't ), so you still need to

run the DirectX Web Installer to make sure DirextX is up to date

Download DirectX End-User Runtime Web Installer from Official Microsoft Download Center

"Just like that M.Soft Rep said in their post after mine, try installing under a different compatibability mode,


well that raises red flags for me, and he/she isnt the only one i have heard that from."

This is one of the unfortunate things with these forums. The Support Engineers tend to be cut and paste

specialist who often post irrelevant suggestions. I don't fully understand their MS connections, and have no

idea what Support Engineer truly translates too (maybe phone support off line ? ) but my understanding is

they are also volunteers. While their cut and paste response is often helpful, it can wildly off mark as often as not.

- Not to say that I don't also get things wrong, or have anything approaching all the answers.

Answers to questions regarding the vagaries of the PC are rarely straight forward as we would hope.

- However, your first post has a bit too much rant and not enough useful information.

We fully understand the frustrations people experience (it never stops personally either. PC's are like that),

but to help yourself you need to provide us with good detailed information, and responses to our questions .

- You didn't mention your USB issue previously, and I'm afraid I've never had to deal with this, but have

you looked in Device Manager to see if there are any yellow exclamation marks, or other flags in

the USB section ? If so uninstall and reinstall the driver for the relevant port or device.

- Also check the keyboard and mouse section for any flags.

- Note too that if you are using a recent Logitech LGS version that it may use Apples
'Bonjour' .

This software has always been trouble. I stopped updating my LGS at version 8.55.137 because

this was the last version that did not include Bonjour (unless they have removed it from more recent

versions that I've not tried).

"So i dont know if its probably just a bad install"

- It is quite possible to have a dodgy upgrade. I had two goes. The first one had issues with the Start menu

and Task Bar as well as getting stuck in 'update' loops. I canned Win10 for two weeks and had another far

more successful upgrade on the second go.

Are you using a clone of your original Win7, or a rollback ?

If you have a clone of Win7 you can swap between it and Win10. I cloned my Win7 before the first attempt

and used it the first couple of months after doing the Win10 upgrade again, so I could swap back and fourth.

I have each OS on separate SSD's and changed the boot order in BIOS when I wanted to swap to the other OS.

- Anyway. Gotta go. It's dinner time here in Oz.

.

 

Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

Forum rules

Code: <ActivePartialProductKey>T83GX</ActivePartialProductKey> <ActiveProductKeyPid2>00331-10000-00001-AA410</ActiveProductKeyPid2> <OSVersion>10.0.10240.2.00010100.0.0.048</OSVersion> <ProductName>Windows 10 Pro</ProductName> <ProcessorArchitecture>x64</ProcessorArchitecture> <EditionId>Professional</EditionId> <BuildLab>10240.th1_st1.151104-1714</BuildLab> <TimeZone>GMT Standard Time(GMT)</TimeZone> <ActiveSkuId>2de67392-b7a7-462a-b1ca-108dd189f588</ActiveSkuId> <ActiveSkuDescription>Windows(R) Operating System, VOLUME_KMSCLIENT channel</ActiveSkuDescription> <ProductUniquenessGroups>55c92734-d682-4d71-983e-d6ec3f16059f</ProductUniquenessGroups> <ActiveProductKeyPKeyId>08e404fb-41f3-77ac-59ef-6e9f2d3f499d</ActiveProductKeyPKeyId> <ActiveProductKeyPidEx>03612-03311-000-000001-03-2057-10240.0000-3192015</ActiveProductKeyPidEx> <ActiveProductKeyChannel>Volume:GVLK</ActiveProductKeyChannel> <ActiveVolumeCustomerPid>06401-00152-026-080487-03-2057-9600.0000-1272015</ActiveVolumeCustomerPid> <OfflineInstallationId>765183589683315629916641524037813847218373957910354992534484960</OfflineInstallationId> <DomainJoined>false</DomainJoined>[/quote]