New
#41
That message can actually be fixed by going into regedit and navigating to HKEY_LOCAL_MACHINE/BCD00000000/HARDWARE/DEVICEMAP/VIDEO and setting MaxObjectNumber to 0.
Random black screen and restart, bugcheck 0x0000116 in event viewer
-
-
New #42
Just because it did crash might not mean it is the driver for sure as said, this is the TDR reacting to it and recovering.
Try what other member said, but also think about some of other test maybe needed.
-
New #43
I might just do the DDU and install the latest NV drivers, I'm not 100% with regedit without messing it all up, that's what corrupted the first install lol.
-
New #44
Well, i know that very well, i just thought it would get annoying to get more messages like these so i said to edit this key.
EDIT: Yes do DDU first.
-
New #45
If backup registry or use system restore, you might be fine. A post you commented on with similar issue still has same errors like you, he found using old NVIDIA Driver seems to stop his issues. Could be something with older cards and Windows 10 issues.
Maybe there chipsets, as NVIDIA has different chipsets,Fermi,Maxwell, etc....
-
New #46
I know mine is Fermi, but it's the sweet spot for my hardware without bottlenecking, I may be able to upgrade to a 600 Kepler but finances restrict at the moment, also, not sure if it'll bottleneck.
-
New #47
Mean like GTX 660 ? Your motherboard is an older model i saw as long as PSU has sufficient power and PCI-E slot can accommodate it. Strange to me how list here does show compatibility with NVIDIA mentioned.
http://nvidia.custhelp.com/app/answe...-windows-10%3F
-
New #48
oh, my MB can accommodate, it's got 3 PCI-E slots, 2x 2.0 ports and a single 1.0 port. it's a great motherboard, just shame about the chipset. google EVGA nf78 132 CK-A1
-
-
New #49
well, it's officially solved, a fresh install again, (the last one was 32bit) and not a single crash, updated to the latest nv drivers and it's running amazingly, thanks a lot peeps.
-
Quote
Related Discussions
