Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Crap ton of BSOD - (Too many to list)

12 May 2014   #31
BanjoDrummer

Windows 7 professional x64
 
 

Quote   Quote: Originally Posted by derekimo View Post
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.

Quote:
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.


My System SpecsSystem Spec
.
12 May 2014   #32
mohavepc

Windows 7 Professional x64
 
 

Quote:
=BanjoDrummer;2774084How can I tell how many continuous amps it has?
Research is how I found it. after contacting an engineer at Corsair and asking him what your PSU's continuous rating was he told me and then told me that basically the higher the wattage the higher the continuous amperage within reason on a well built PSU. each manufacturer can and do tweek their labels to make the units sound better than they will actually perform.
My System SpecsSystem Spec
12 May 2014   #33
derekimo

Microsoft Community Contributor Award Recipient

Win 10 Pro x64
 
 

Quote   Quote: Originally Posted by BanjoDrummer
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...

Quote:
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.
My System SpecsSystem Spec
.

12 May 2014   #34
BanjoDrummer

Windows 7 professional x64
 
 

Quote   Quote: Originally Posted by derekimo View Post
Quote   Quote: Originally Posted by BanjoDrummer
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...

Quote:
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?
My System SpecsSystem Spec
12 May 2014   #35
derekimo

Microsoft Community Contributor Award Recipient

Win 10 Pro x64
 
 

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.
My System SpecsSystem Spec
12 May 2014   #36
mohavepc

Windows 7 Professional x64
 
 

Quote   Quote: Originally Posted by derekimo View Post
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.
And a lot more difficult to diagnose and repair in this environment. Having the machine physically in front of one of use we have tests we can do to speed up the process. 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.
My System SpecsSystem Spec
12 May 2014   #37
derekimo

Microsoft Community Contributor Award Recipient

Win 10 Pro x64
 
 

Quote   Quote: Originally Posted by mahovepc
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.
My System SpecsSystem Spec
20 May 2014   #38
BanjoDrummer

Windows 7 professional x64
 
 

Quote   Quote: Originally Posted by mohavepc View Post

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
My System SpecsSystem Spec
20 May 2014   #39
mohavepc

Windows 7 Professional x64
 
 

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.
My System SpecsSystem Spec
30 May 2014   #40
BanjoDrummer

Windows 7 professional x64
 
 

Quote   Quote: Originally Posted by mohavepc View Post
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?
My System SpecsSystem Spec
Reply

 Crap ton of BSOD - (Too many to list)




Thread Tools




Similar help and support threads
Thread Forum
Spent to much money for this BSOD crap ntoskrnl.exe+75bc0
I had a computer but thought it was time for a new one, got a new cpu video card motherboard power supply ram, all of it. When I switched my hard drive to new computer i was getting BSOD so i reset the hard drive and installed windows 7 Kept getting it so i bought a new hard drive and put...
BSOD Help and Support
oh crap! thats not cheap
ok for something on par wait the 5870.... (more or less ya know.....) this is waaaaayyyyy high on the price :zip: SabrePC.com - Nvidia Geforce GTX 480 GDDR5 1.5GB PCI-Express 2.0
Graphic Cards
what's up with the permissions crap?
i had to map a network drive because when i tried to download win7.iso, and save it to any directory on that drive. in fact, to any directory on both partitions on that drive. i had to save to a network drive in order for this thing to go through. s win now i'm one who is lucky enough to have...
General Discussion


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 02:35.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App