Solved Numerous BSOD screens, have tried everything cant find problem!

[CG1644]

This is my Bios screens...nothing about voltages.

 

[CG1644]

Although I havent had any blue screens at all today after doing all the suggestions you gave me this morning. Maybe its fixed?

 

[essenbe]

Although I havent had any blue screens at all today after doing all the suggestions you gave me this morning. Maybe its fixed?

Let's just hope so. But, I'm the kind that wants to know what was wrong. But, never mind. If it is fixed, leave it alone. Let us know how it goes, and if you have any more blue screens, run the SF Diagnostics again. Did you set it to defaults in BIOS?

 

[CG1644]

I didnt touch the the BIOS settings because I am afraid to mess with anything since I have had no blue screens in over 12 hours. This is the longest I have went without a blue screen in over 2 weeks. I just wish I knew which step I took actually fixed it! And also would love to know why my voltages are showing so high even after replacing the power supply.

 

[essenbe]

That's great news. I sure hope it lasts for you. Let us know if things change.

 

[CG1644]

I sure will. Thanks so much for all your help!

 

[CG1644]

It is not fixed. Got a blue screen just now and when it restarted i got the black screen with the white cursor in the upper left corner again. Then I finally got it started again and my mouse and keyboard were unresponsive. Shut it down for 10 minutes and finally got it up and running again. I attached a new sf diagnostic file. Please help!!

 

[Arc]

It is the display driver, again.

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880257b20cb, 1, fffff880057b20b5, 2}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+19d0b5 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff880257b20cb, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff880057b20b5, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003708100
GetUlongFromAddress: unable to read from fffff800037081c0
 fffff880257b20cb Nonpaged pool

FAULTING_IP: 
atikmdag+19d0b5
fffff880`057b20b5 66413100        xor     word ptr [r8],ax

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800217ca90 -- (.trap 0xfffff8800217ca90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000f13c rbx=0000000000000000 rcx=0000000000000018
rdx=fffff8800217cc78 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880057b20b5 rsp=fffff8800217cc28 rbp=fffff8800217cd30
 r8=fffff880257b20cb  r9=fffff8800217cc78 r10=0217cc7800000000
r11=0000000000000018 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
atikmdag+0x19d0b5:
fffff880`057b20b5 66413100        xor     word ptr [r8],ax ds:fffff880`257b20cb=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000354c6a4 to fffff800034cfc40

STACK_TEXT:  
fffff880`0217c928 fffff800`0354c6a4 : 00000000`00000050 fffff880`257b20cb 00000000`00000001 fffff880`0217ca90 : nt!KeBugCheckEx
fffff880`0217c930 fffff800`034cdd6e : 00000000`00000001 fffff880`257b20cb cb962147`885c8400 00000000`00000018 : nt! ?? ::FNODOBFM::`string'+0x43836
fffff880`0217ca90 fffff880`057b20b5 : fffff880`0578e7ab 00000000`00000004 00000000`00000000 00000000`0000de00 : nt!KiPageFault+0x16e
fffff880`0217cc28 fffff880`0578e7ab : 00000000`00000004 00000000`00000000 00000000`0000de00 fffff880`05a32000 : atikmdag+0x19d0b5
fffff880`0217cc30 00000000`00000004 : 00000000`00000000 00000000`0000de00 fffff880`05a32000 fffff880`0308f180 : atikmdag+0x1797ab
fffff880`0217cc38 00000000`00000000 : 00000000`0000de00 fffff880`05a32000 fffff880`0308f180 00000000`0005ae79 : 0x4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+19d0b5
fffff880`057b20b5 66413100        xor     word ptr [r8],ax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+19d0b5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50d225df

FAILURE_BUCKET_ID:  X64_0x50_atikmdag+19d0b5

BUCKET_ID:  X64_0x50_atikmdag+19d0b5

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

5: kd> lmvm atikmdag
start             end                 module name
fffff880`05615000 fffff880`0612b000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Thu Dec 20 02:08:55 2012 (50D225DF)
    CheckSum:         00AC6529
    ImageSize:        00B16000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Is the computer supplying adequate power? Check it.
eXtreme Power Supply Calculator

Set the BIOS to the default settings.
How To Clear CMOS (Reset BIOS)

If possible, Dismantle the computer, clean the inside, specially the fan grills and air vents.

2010 BIOS
​

 

[CG1644]

The Speccy seems to always show the same stats no matter how long my computer is running. The weird thing is that the blue screens happen mostly in the morning when first turning on my machine no after many hours of use. I dont understand how to do the power supply calculator......can you guide me? I will reset my BIOS but to be honest I am afraid of doing the stress test, i read that it can actually start a fire or blow up your machine, that kind of scares me!

 

[CG1644]

I think I figured out the power supply calculator, its telling me I should have a minimum of 320 watts and a recommended 370 watts.

 

[Arc]

You should try to reset the BIOS.
How To Clear CMOS (Reset BIOS)

Also try a driver rollback, to one version that worked good lately.
Device Manager - Roll Back Driver

And, use the onboard graphics to see if it is occurring the same there or not.

We need to eliminate the probable chances of a stop 0x50 display driver BSOD, so these are needed.

 

[CG1644]

which driver am i looking to rollback? How do I use the onboard graphics card? Its really crazy because I dont get the blue screens often anymore, i get them in the morning but then the computer seems stable for the rest of the day. I wont know if anything worked until I get another blue screen or not get one.... so do I just us the onboard graphics for the next day or so?

 

[Arc]

Rollback the driver that is failing .... obviously the display driver.
If it is crashing again, unplug the VGA/DVI/HDMI port from the GPU's end and plug it to the motherboard's end.

Bet before everything, reset the BIOS. Just remove the COMS battery and place it again.

 

[essenbe]

Click the start button, type device manager in the search box, click on device manager and click the arrow next to display adapters. it will look like this except for the card will be your card.
View attachment 263428

Right click on the card and select properties, go to the driver tab:
View attachment 263429

Click on the roll back driver button

Also, your computer will not burn up , just watch the temps. You can stop the test if temps get too high. Download and install MSI Afterburner, and go to the monitoring section, check the GPU temp and at the bottom select show in task bar. You will see the temps of your graphics card. Also download and install Core Temp. It will show the temp of your CPU cores. Monitor them during tests. You can always stop any stress test. I run them all the time on my computer. When you reset CMOS, remember the sata controller settings you have now. Go into bios after replacing the battery and set defaults (F5) afyer setting the defaults, set your sata controller back to what it is right now or your computer won't boot. Save and exit.

 

[CG1644]

Ok thanks I will try all that in a few. I was reading around and decided to run a driver verifier test. As soon as I restarted my computer screen turned a million colors and froze, i got nervous and shut it off because the blue screen didnt come. Should I do it again and leave it be until it blue screens? It just sits there with a bunch of weird colors covering the entire screen. Maybe this can help me determine the exact drivers causing these blue screens?

 

[Arc]

Driver Verifier is only needed when we dont have the proper concept as to what driver is failing ..... but here we know it with certainty that it is the display driver. What more information we may expect from DV?

We now need to discriminate it between hardware and software issue. We are trying in this direction.

Rather you should have followed the instructions given.

 

[CG1644]

Oh ok i thought since I kept getting different blue screens maybe it was more than 1 driver. I will do what you suggested now. can you tell me what temps my cpu and gpu should never exceed when running the stress test?

 

[Arc]

During the GPU stress test, if you see that the heat is crossing 80s ... and tending to 90's, stop it. But in most of the cases they stay within 70's.

Observe for any artifacts or display crashes during the furmark or OCCT test.

 

[CG1644]

OK will the test stop when its completed or do I need to manually stop it at a certain point? Sorry for so many questions, i have never done a stress test before.

 

[Arc]

Usually the test stops after the designed time, but it may crash in between. But if dont crash and continue to that heat mentioned earlier, stop it manually.