New
#11
I did a clean install of the nVidia driver and I was still having BSODs,so I updated it again to see if I get any,and still no luck.
I did a clean install of the nVidia driver and I was still having BSODs,so I updated it again to see if I get any,and still no luck.
OK, let's take a look at the card. Can you remove the side panel of your PC and check that the fan on the heatsink is clean and completely free of dust. If there is any dust in there give it a clean out with a can of compressed air and/or a soft brush. Once you're happy it's clean we'll start testing the card.
Okay,I've completely cleaned out the dust inside the PC.
Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark
NoteRun Furmark for around 30 minutes.
WarningYour GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them, if the temperature continues to rise steadily once it has reached 80°C be prepared to stop the test so as to not damage your GPU.
If you don't have any GPU temperature monitoring software let me know and I'll point one out for you.
I don't have a GPU temperature monitoring software.
Download MSI Afterburner to read your GPU temperatures, it can be minimised to the notification area so your temperature is always visible.
I ran furmark for 30 minutes and the temperature did not go above 80,here is a screenshot.
Attachment 353166
Can you run the DM Log collector again and post up the resulting .zip file so I can take a look at the most recent dump files.
Here you go,
EDIT:While I was playing Dota today it crashed twice so I tried to restart my PC,and I get a BSOD,so I ran DM log collector and while I was replying to this I get another one.
Updated log file:Attachment 353179
Last edited by soulspirit; 20 Mar 2015 at 01:56.
OK those dumps are helpful, there is a STOP 0x77 in there which is indicating a hardware error. I'm thinking at the moment that it's either the GPU or the motherboard.
I have to go out soon and won't be back around until tomorrow afternoon unfortunately but could you carry out the following in the meantime.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_STACK_INPAGE_ERROR (77) The requested page of kernel data could not be read in. Caused by bad block in paging file or disk controller error. In the case when the first arguments is 0 or 1, the stack signature in the kernel stack was not found. Again, bad hardware. An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates the data could not be read from the disk due to a bad block. Upon reboot autocheck will run and attempt to map out the bad sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging file is on a SCSI disk device, then the cabling and termination should be checked. See the knowledge base article on SCSI termination. Arguments: Arg1: 0000000000000000, (page was retrieved from page cache) Arg2: fffff88004700e00, value found in stack where signature should be Arg3: 0000000000000000, 0 Arg4: fffff88004700dc0, address of signature on kernel stack
1: Remove the power from your PC, open it up and remove the GPU. Re seat it and ensure it's fully seated, power up and test.
2: If the first option doesn't resolve the issue, move the GPU to a different PCI slot if you have one and test.
3: If neither of the options above work, if you have onboard graphics available remove the GPU and run the system using the onboard graphics to test.
I'll drop back in tomorrow to see how you get on.