Solved BSOD regarding Video/Graphics Card

[Hones Tea]

Hello,

Recently, my pc is lagging so much, meaning everything is slow, clicking, opening files and all that. I thought it was my RAM or Processor, but the thing is it was my Graphics Card. Then just now I turned off PC and tried to get it back on, but sadly it won't boot up and only appearing on screen was "No Signal".

Then, I thought it could be my Graphics Card, you can see what I am using in my specs. So what I did was I removed my Graphics Card, and then put the plug into the VGA then I successfully boot up without any problems and lags. However, I cannot stay without Graphics Card, because I'm an online gamer and my game won't work without Graphics Card, it works with VGA but the game is very laggy and I cannot play anymore.

Now, I want to ask if the Graphics Card was dead or not and I have to replace or I just need to do something. I have attached the minidump file in Windows/Minidump folder. Also the SF Diagnostic.

I hope you could help me figure out my problem and what to do.

Thank you and best regards to all people here.

Edited:

I forgot to tell that after I removed my graphics card, I'm still receiving BSOD, my screen will crash then Blue screen then off.

 

[Arc]

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
If these two tests come free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
__________________________________________________________________________________
BSOD ANALYSIS:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, 828b7a46}

Probably caused by : ntkrpamp.exe ( nt!KiDeliverApc+e1 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 828b7a46, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8297084c
Unable to read MiSystemVaType memory at 8294fe20
 00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiDeliverApc+e1
828b7a46 8908            mov     dword ptr [eax],ecx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  DF5Serv.exe

TRAP_FRAME:  8f741b1c -- (.trap 0xffffffff8f741b1c)
ErrCode = 00000002
eax=00000000 ebx=82c1fb48 ecx=00000000 edx=00000000 esi=86354064 edi=86356030
eip=828b7a46 esp=8f741b90 ebp=8f741bc4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!KiDeliverApc+0xe1:
828b7a46 8908            mov     dword ptr [eax],ecx  ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828b7a46 to 82847c9b

STACK_TEXT:  
8f741b1c 828b7a46 badb0d00 00000000 82a63800 nt!KiTrap0E+0x2cf
8f741bc4 8282eb6c 00000000 00000000 00000000 nt!KiDeliverApc+0xe1
8f741bd8 828b51be 8653d150 8653d150 86356200 nt!KiCheckForKernelApcDelivery+0x24
8f741bec 82a43624 86356264 86356001 00000000 nt!AlpcpSignalAndWait+0x68
8f741c10 82a64e3f 86356001 8f741c7c 60000000 nt!AlpcpReceiveSynchronousReply+0x27
8f741ca0 82a5a2e1 8653d150 00020000 002fbc40 nt!AlpcpProcessSynchronousRequest+0x276
8f741d0c 828448ba 0000012c 00020000 002fbc40 nt!NtAlpcSendWaitReceivePort+0xd0
8f741d0c 77477094 0000012c 00020000 002fbc40 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0227f6bc 00000000 00000000 00000000 00000000 0x77477094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDeliverApc+e1
828b7a46 8908            mov     dword ptr [eax],ecx

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiDeliverApc+e1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d331

FAILURE_BUCKET_ID:  0xA_nt!KiDeliverApc+e1

BUCKET_ID:  0xA_nt!KiDeliverApc+e1

Followup: MachineOwner
---------

 

[Hones Tea]

Hello, sorry for late response. Can now close this and mark as solved. All of the conflicts was made by Deep Freeze. I uninstalled it and everything works fine.

Thank you.

 

[Arc]

Good to know that your issue is solved. For any other further issue, let us know