Crap ton of BSOD - (Too many to list)

derekimo said:

I'm not sure why you are having problems, too many variables. Which is also the reason why display drivers work for some and don't work for others, too many variables.

Is it the driver causing the issue or is it my computer not working well with the driver?

That is what we are trying to figure out.

Could you take a look at the first one? (4/19/14). This one occurred on the day I installed windows and I am curious to know what caused the bsod.

BanjoDrummer said:

Could you take a look at the first one? (4/19/14). This one occurred on the day I installed windows and I am curious to know what caused the bsod.

Sure, here's what the dump is pointing to,

Code:

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x1141df

Your video driver, the 13.12 version,

Code:

2: kd> lmvm atikmdag
start             end                 module name
fffff880`1103f000 fffff880`11d2f000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Dec 06 13:19:43 2013 (52A23F6F)
    CheckSum:         00CA856E
    ImageSize:        00CF0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If you look at the BugCheck,

Code:

BugCheck 1000007E, {ffffffffc0000005

Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (Windows Debuggers)

Code:

0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.

Some obvious things to try...

Resolution

If you are not equipped to debug this problem, you should use some basic troubleshooting techniques.
Make sure you have enough disk space.
If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
Try changing video adapters.
Check with your hardware vendor for any BIOS updates.
Disable BIOS memory options such as caching or shadowing.

A little more info,

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff880045b3b34, fffff880027f0788, fffff880027effe0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_APERTURE_SEGMENT::EvictResource+26c )

Followup: MachineOwner

That probably caused by is a windows driver which we know is false,

Driver Reference Table - dxgmms1.sys

That is about as much info as I'm capable of giving.

derekimo said:

BanjoDrummer said:

Could you take a look at the first one? (4/19/14). This one occurred on the day I installed windows and I am curious to know what caused the bsod.

Sure, here's what the dump is pointing to,

Code:

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x1141df

Your video driver, the 13.12 version,

Code:

2: kd> lmvm atikmdag
start             end                 module name
fffff880`1103f000 fffff880`11d2f000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Dec 06 13:19:43 2013 (52A23F6F)
    CheckSum:         00CA856E
    ImageSize:        00CF0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If you look at the BugCheck,

Code:

BugCheck 1000007E, {ffffffffc0000005

Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (Windows Debuggers)

Code:

0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.

Some obvious things to try...

Resolution

If you are not equipped to debug this problem, you should use some basic troubleshooting techniques.
Make sure you have enough disk space.
If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
Try changing video adapters.
Check with your hardware vendor for any BIOS updates.
Disable BIOS memory options such as caching or shadowing.

A little more info,

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff880045b3b34, fffff880027f0788, fffff880027effe0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_APERTURE_SEGMENT::EvictResource+26c )

Followup: MachineOwner

That probably caused by is a windows driver which we know is false,

Driver Reference Table - dxgmms1.sys

That is about as much info as I'm capable of giving.

Thanks a lot for the help! So, the 13.12 driver caused this bsod? Could it be my RAM because a memory access violation occurred?
AND how did I get the false driver dxgmms1.sys?

I was afraid I might of put too much out there, basically the probably caused by is the first guess from the debugger, since it was a Microsoft driver we have to go deeper because they are never the actual cause.

Digging deeper we found the display driver was the actual driver.

Looking at the timestamp for that driver gave me it's release date, so I could see it was the 13.12 driver that caused the crash on the 4-19-2014.

Could it be your RAM? According to this,

BSOD Index

That could be one of the reasons.

So you can see why this stuff takes a lot of testing, and trial and error and isn't always an obvious fix.

mahovepc said:

like I mentioned before a Linux cd or a trash hard drive would give us the opportunity to see what hardware is actually having issues.

That is a good idea.

mohavepc said:

like I mentioned before a Linux cd or a trash hard drive would give us the opportunity to see what hardware is actually having issues.

I have to agree that yes it could be ram as even ram that passes the test could have a bad chip or perhaps incompatible with another piece of hardware.

I just had 2 other bsod. How would I go about using a linux cd? I have never done that before

mohavepc said:

Ok first download a Linux Iso.

Stress Linux is good for testing hardware but requires a torrent utility to download.

You can also just get Linux Mint to do a general test of the system.

You can then create either a bootable flash drive or bootable DVD / CD.
For a bootable Flash I recommend Universal USB Installer
For DVD / CD I recommend Image Burn
Both of which are freeware.

Next step is to boot from USB or DVD / CD.

Best option is to enter the Bios using either f2, Del, Esc key and change boot order. You can also try pressing f12 at the splash screen and choose boot device but if you miss you will have to try again.

If your using Stress Linux follow the prompts to test your system.

If your using Mint Linux there are a few minor Linux tests built in but I would essentially use the system, open firefox go to youtube ect. to see how it performs.

Will mint linux help to tell if it is a driver issue or a hardware issue? I think you said that if it runs fine in mint linux for a couple of hours, then it is probably a driver issue. How will I be able to tell which driver is causing the issue?