From event viewer.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xffff8c81e3e50010, 0xfffff800840a1218, 0xffffffffc000009a, 0x0000000000000004). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: c92c8fdf-fc07-4c4f-bc27-34c22428a21e.
EDI: Also, when i tried connecitng the coputer monitor to the GTX 1080 it said "no input signal". I tried multiple different cords. I also tried multiple different ports. Using both the vga port (with HDMI adapter), and 2 different HDMI cables and 1 HDMI to DV-D adapter cord. All did NOT work. Then i went to sleep approximately 11pm-12am. Then iwoke up at 4am-4:30am an the computer monitor was suddenyl receiving a video signal from the graphics card I have no clue why it suddenly started working when i was asleep. Also, when NO cord is plugged into the monitor going into the GPU, the computer monitor says "check cable connection". Therefore, it can be reasoned that the cables ARE being detected, yet eithre nosignal is being sent, or the signal IS being sent, and is NOT being received.
Yet, my computer monitor suddenly froze and i saw a blue screen with words saying the computer suffered an error and was collecting information and restarting. The computer successfuly restarted and the video signal was still being sent and received, yet after logging in, the computer, AGAIN, not long after logging in, suffered the same problem. I clicked the GPU button/thing down and then pushed the GPU into the motherboard socket to attempt to reseat it. I currently do NOT have a screw driver available to unscrew the GPU from the computer case. Therefore, it is NOT currently posible to completely remove the GPU from the motherboard and fully reseat the computer.
SIDE NOTE - The same sort of error has occured before when i accidentally hit my leg into the computer. I thought this was due to the motherboard moving due to being a bit loose and hitting/coming into contact with the computer case. However, it is now more probable that the GPU was knocked out of alignment of the motherboard socket causing the error. I cannot be certain though. Any thoughts/suggestions?
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xffff8c81e3e50010, 0xfffff800840a1218, 0xffffffffc000009a, 0x0000000000000004). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: c92c8fdf-fc07-4c4f-bc27-34c22428a21e.
EDI: Also, when i tried connecitng the coputer monitor to the GTX 1080 it said "no input signal". I tried multiple different cords. I also tried multiple different ports. Using both the vga port (with HDMI adapter), and 2 different HDMI cables and 1 HDMI to DV-D adapter cord. All did NOT work. Then i went to sleep approximately 11pm-12am. Then iwoke up at 4am-4:30am an the computer monitor was suddenyl receiving a video signal from the graphics card I have no clue why it suddenly started working when i was asleep. Also, when NO cord is plugged into the monitor going into the GPU, the computer monitor says "check cable connection". Therefore, it can be reasoned that the cables ARE being detected, yet eithre nosignal is being sent, or the signal IS being sent, and is NOT being received.
Yet, my computer monitor suddenly froze and i saw a blue screen with words saying the computer suffered an error and was collecting information and restarting. The computer successfuly restarted and the video signal was still being sent and received, yet after logging in, the computer, AGAIN, not long after logging in, suffered the same problem. I clicked the GPU button/thing down and then pushed the GPU into the motherboard socket to attempt to reseat it. I currently do NOT have a screw driver available to unscrew the GPU from the computer case. Therefore, it is NOT currently posible to completely remove the GPU from the motherboard and fully reseat the computer.
SIDE NOTE - The same sort of error has occured before when i accidentally hit my leg into the computer. I thought this was due to the motherboard moving due to being a bit loose and hitting/coming into contact with the computer case. However, it is now more probable that the GPU was knocked out of alignment of the motherboard socket causing the error. I cannot be certain though. Any thoughts/suggestions?
Last edited: