BSOD at Random Times - Windows 7 x64

U

UHCoog09

Member
Joined
Dec 28, 2014
Posts
12
Hi,

My PC has been crashing at random moments, multiple times a day. There does not seem to be a pattern or program that triggers this.

OS - Windows 8.1, 8, 7, Vista ? Windows 7
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? No
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Full Retail Version
· Age of system (hardware) 2 years
· Age of OS installation - have you re-installed the OS? 1 and 1/2 years ago

· CPU AMD Athlon II X3 435 - 2.9 GHZ
· Video Card ATI Radeon 4800 HD Series
· MotherBoard - (if NOT a laptop) Unknown - will pull documentation or open PC to determine
· Power Supply - brand & wattage (if laptop, skip this on? Not sure

· System Manufacturer Custom Built
· Exact model number (if laptop, check label on bottom)

· Laptop or Desktop? ​Desktop
 

Attachments

I setup driver verifier per the instructions; however, I had to disable due to my PC freezing once I logged into Windows. It was not a BSOD, just that the completely almost immediately froze after logging into to my Windows account.
 
Code: 
[COLOR=#ff0000]BugCheck D1[/COLOR], {203, 2, 1, [COLOR=#008000]fffff88004962558[/COLOR]}

Probably caused by : [COLOR=#ff0000]atikmdag.sys[/COLOR] ( atikmdag+143558 )

A driver has referenced an invalid memory address, and then attempted to perform a write operation on that address.

Code: 
2: kd> [COLOR=#008000].trap 0xfffff88002f8c820[/COLOR]
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000088f8ff8 rbx=0000000000000000 rcx=fffffa80081fb050
rdx=fffffa80081fba18 rsi=[COLOR=#0000cd]0000000000000000[/COLOR] rdi=0000000000000000
rip=[COLOR=#ff0000]fffff88004962558[/COLOR] rsp=fffff88002f8c9b8 rbp=fffffa80081fba18
 r8=fffffa80074035a0  r9=0000000000000013 r10=0000000000000fff
r11=0000000000000031 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
atikmdag+0x143558:
fffff880`04962558 488986f0010000  mov     qword ptr [rsi+1F0h],rax ds:00000000`000001f0=????????????????

The rsi register is a NULL pointer.

Code: 
2: kd> [COLOR=#008000]r.[/COLOR]
Last set context:
rsi=00000000`00000000  rax=00000000`088f8ff8

I would suggest looking for an driver update for your AMD graphics card:

Code: 
2: kd>[COLOR=#008000] lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`0481f000 fffff880`053d2000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR=#ff0000]Tue Apr 30 03:07:09 2013[/COLOR] (517F274D)
    CheckSum:         00B6397D
    ImageSize:        00BB3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Motherboard Information:

Code: 
2: kd> [COLOR=#008000]!sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.5, DMIVersion 0, Size=1420]
BiosMajorRelease = 8
BiosMinorRelease = 14
BiosVendor = American Megatrends Inc.
BiosVersion = P1.20
BiosReleaseDate = [COLOR=#ff0000]08/31/2009[/COLOR]
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
SystemFamily = To Be Filled By O.E.M.
SystemVersion = To Be Filled By O.E.M.
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = [COLOR=#ff0000]ASRock[/COLOR]
BaseBoardProduct = [COLOR=#ff0000]M3A770DE[/COLOR]
BaseBoardVersion =
 
The AMD Control Center and device manager drivers match what AMD has listed as the latest driver version on their website (Legacy)

Display Driver ver. 8.97.100.11
AMD Control Center.PNG
 
Oh, a 4xxx series. Yeah, not a surprise there.

Roll back to a previous or beta if available.
 
Rolled back the driver this morning (could not find a beta driver) and left the pc on during the day. Came home to the following BSOD: IMAG0802.jpg
 
Do you have integrated video, or a secondary video card to try? If so, uninstall drivers and give it a try.
 
Does the system crash at all without any AMD drivers installed, as in does it run okay on basic Windows drivers?
 
The driver in the bugcheck is a Windows driver, and you can follow Patrick's suggestion by booting into Safe Mode.
 
Ran the system in safe mode a couple of hours ago and it experienced an error and restarted. Please let me know if you need me to re-run any data collection files to analyze.
 
What kind of error, a bug check? If you crashed in safe mode this is a hardware problem. Yes, please re-run the collection app.
 
When I checked the computer it had actually restarted, which I assume some type of error had occurred due to it restarting. When I logged into Windows it did indicate 'windows has experienced an error'. The exact type of error I'm unaware of. Attached are the results from the collection app. Thanks.
 
One of two things are a possibility. Either your RAM is bad or your video card is bad.

Run Memtest for no less than 8 passes:


Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works (you don't need to read, it's only for those interested in the specifics):

Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.

The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead and ensure that all adjacent cells have at least been written with all possible one and zero combinations.

The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.

Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting
 
Ran MemTest on each stick individually. Three tested with 0 errors and one tested with errors. It appears one of the ram sticks is faulty. I will try the pair of ddr that is working and see if any BSOD occur. I also had my timings set to auto but have a updated per g.skill specs to 8-8-8-21.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top