Solved Random BSOD's, mainly ntoskrnl.exe but also other errors.

[x BlueRobot]

I'm doing the stress test right now.

Yes I've installed all important and optional updates via windows update.

I've attached a screen shot of my device manager where it says the driver version of my graphics card. To me it seems that it is the latest version already.

It is, and follow YoYo's instructions and don't install the CCC, it does cause problems.

 

[Kreshnak]

Two and a half day without a single bsod, and then I get two in two minutes. Both ntoskrnl.exe and atikmdag.sys. Attached a new sf once again.

 

[centaur78]

Hmmm

it still looks like all the bsod (Bugcheck 24, A, and 3b) point to pool corruption from your graphic driver.

Just curious... Whats your graphic card model and make ???

 

[Kreshnak]

I have the box in front of me, it says: ASUS HD 7770 Powered by AMD Radeon HD 7770

 

[centaur78]

could you run GPUZ and post the screenshot of the Graphics and Sensor tab

 

[Kreshnak]

Done

 

[Kreshnak]

Got a few more .dmp files from my latest bsod's.

 

[YoYo155]

I've read the thread, and here is the summery of the things you've changed:

• New HDD.
• Clean install of Windows.
• New RAM.
• New PSU.
• New GPU.
• Updating drivers.
• Removed software.
• Stressed the CPU.
• Reset the BIOS to defaults.

Its beginning to look like the motherboard is at fault,
considering its the infamous nForce.


This might be a long-shot but it's worth a try.
Remove any software related with your Razer peripherals

Start Menu\Programs\Razer
Start Menu\Programs\Razer\Lycosa
Start Menu\Programs\Razer\Razer Naga

• If you have another keyboard and mouse use them.

​

As a last resort remove the ATK110 utility.

ASACPI.sys   Mon Mar 28 05:30:36 2005

 

[Kreshnak]

Ok, uninstalling the razer software now. Don't think I have any other keyboard/mouse available at the moment, can however ask around tomorrow to see if I can borrow from a friend for a few days.
Uninstalled the ATK110 utility aswell.

 

[Kreshnak]

It seems to be more frequent when i play wow for some reason, so it's my go-to way to try if something works. Started up wow and within 15 minutes i got a new bsod, immediately followed by two more.

What do I do if it is the motherboard? Is there something I can do to try to fix it, or is it just to buy a new one?

 

[x BlueRobot]

[COLOR=Red]BugCheck 19[/COLOR], {[COLOR=Blue]21[/COLOR], [COLOR=SeaGreen]fffffa800a615000[/COLOR], 1050, 50}

GetPointerFromAddress: unable to read from fffff80002eb1100
GetUlongFromAddress: unable to read from fffff80002eb11c0
GetUlongFromAddress: unable to read from fffff80002e1fa38
Probably caused by : [COLOR=Red]memory_corruption[/COLOR] ( nt!MmWaitForCacheManagerPrefetch+30 )

It seems that a driver has over run the data following the pool block being freed.

2: kd> [COLOR=SeaGreen]!pool fffffa800a615000[/COLOR]
Pool page fffffa800a615000 region is Nonpaged pool
GetUlongFromAddress: unable to read from fffff80002e1fa38
fffffa800a615000 is not a valid small pool allocation, checking large pool...
unable to get pool big page table - either wrong symbols or pool tagging is disabled
fffffa800a615000 is freed (or corrupt) pool
Bad allocation size @fffffa800a615000, zero is invalid

***
*** An error (or corruption) in the pool was detected;
*** Attempting to diagnose the problem.
***
*** Use !poolval fffffa800a615000 for more details.


Pool page [ fffffa800a615000 ] is __inVALID.

Analyzing linked list...
[ fffffa800a615000 --> fffffa800a615490 (size = 0x490 bytes)]: Corrupt region


Scanning for single bit errors...

None found

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Enable the Special Pool option too.

It could be the nVidia chipset drivers, which are well known to cause problems.

A Stop 0xA points to the graphics card driver:

3: kd>[COLOR=SeaGreen] lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`056db000 fffff880`061f1000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR=Red]Wed Dec 19 20:38:55 2012[/COLOR] (50D225DF)
    CheckSum:         00AC6529
    ImageSize:        00B16000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Kreshnak]

Ok, I've enabled driver verifier now. Was a bit skeptic because the other times I've been asked to use driver verifier, I've had to make a system restore because I couldn't even get into safe mode. But now it seems it's working just as fine as without the verifier enabled. Will post the results after at least 24 hours of verifier enabled.

 

[essenbe]

Also, Please keep a watch on your graphics card temps. Tell us how they are while doing different things, especially gaming. One thing I did notice on your GPUz attacchments was the default fan speed of 10%. That's pretty low. Even idling on the desktop, mine is always a minimum of 40%. Almost every card I have owned, that was the minimum fan speed -40%. You can customize your fan profile, if you like. I'm sure Asus has an 'overclocking' program thaat will do it or you can use MSI Afterburner.

If you have a utility that will do it, I would watch my CPU, GPU and motherboard temps very closely. Many motherboards have utilities to watch motherboard temps, if not just monitor your CPU and FPU temps Afterburner for GPU and I use Core Temp for CPU.

 

[Kreshnak]

Approximately half-way into my 24 hours test I've got some things to report. The temps seem stable. The graphics card peaked at 53°C while playing wow. About 30-33 while idle and around 48-49 while gaming. I attached some screens of the temps. I also attached a few pics I took with my phone. It's what happens when it crashes. It doesn't go to a bsod very often at all, it's usually that screen that show. Just a blur of whatever color the last program i ran was. The few bsod's I've gotten hasen't created any .dmp files for some reason. However i wrote the cause down: one was because of Acpi.sys. Another did just show a stop-message: 0x01A (Memory Management)

EDIT: Can't for some reason upload my zip with the screens. Just get this error:
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.

 

[x BlueRobot]

Have you tried again today? It may be something to do at this end.

 

[Kreshnak]

Yup, I've tried a few times. Both to put them in a zip, and individually as .jpg. Still the same error.

 

[x BlueRobot]

Is your Internet working fine in general? I would suggest reporting the problem to one of the Admins - Windows 7 Help Forums - View Profile: Brink or Windows 7 Help Forums - View Profile: z3r010

 

[Kreshnak]

Because I'm stupid and can't read the size limitations on .zip and .jpg for upload to the forum.. I tried to upload a file of 8.4mb when the maximum is 8mb. Anyways, it works now.

 

[Kreshnak]

Anyways, the driver verifier has been enabled for more than 24 hours now. I've got nothing more to report than what I've already told you.

 

[Kreshnak]

New sf again.