Random BSODs and i don't know what to do.

[AlexPowerUp]

As you will see in the file, my PC has been throwing BSODs to my face since i bought it, and I don't know what am I supposed to do. The error messages are totally random: sometimes it's an IRQL, and the temperatures were no more than 55ºC, sometimes it's a pool_header_corrupted, etc. I don't know why does this happen, but I really need some help with it. Thanks <3

 

[Arc]

Hi AlexPowerUp.

Uninstall your installed latest version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

Then install version 13.9 WHQL only.

• Previous AMD Catalyst? Display Drivers

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

Also Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download, install and update those, and then run full system scans with both of them, one by one.

Let us know the results.
_________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff800038a1608}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+bca32 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800038a1608, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003b0c100
GetUlongFromAddress: unable to read from fffff80003b0c1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForGate+d8
fffff800`038a1608 488930          mov     qword ptr [rax],rsi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  Wow-64.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff8800dd537f0 -- (.trap 0xfffff8800dd537f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80115fb8b0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800038a1608 rsp=fffff8800dd53980 rbp=0000000000000000
 r8=0000000000000000  r9=0000000f2d2dc000 r10=0000000000000001
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForGate+0xd8:
fffff800`038a1608 488930          mov     qword ptr [rax],rsi ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800038da229 to fffff800038dac80

STACK_TEXT:  
fffff880`0dd536a8 fffff800`038da229 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0dd536b0 fffff800`038d8ea0 : 00000000`00001000 00000000`00000000 00000000`00000000 fffffa80`0ffa9b60 : nt!KiBugCheckDispatch+0x69
fffff880`0dd537f0 fffff800`038a1608 : 00000001`81ec0000 fffff880`111813ef 00000001`81ec0000 fffff880`0dd53c80 : nt!KiPageFault+0x260
fffff880`0dd53980 fffff800`038aa4f5 : fffffa80`115fb890 fffffa80`0d9cd060 00000000`00002000 00000000`00000000 : nt!KeWaitForGate+0xd8
fffff880`0dd539d0 fffff800`038f0ce8 : 00000000`00000000 00000000`000000aa 00000000`00000000 fffffa80`0d9df800 : nt!KiAcquireGuardedMutex+0x45
fffff880`0dd53a00 fffff880`1111aa32 : fffff8a0`20426010 00000001`81ec0000 00000000`00000000 fffff880`1111a3c3 : nt!KeAcquireGuardedMutex+0x38
fffff880`0dd53a30 fffff8a0`20426010 : 00000001`81ec0000 00000000`00000000 fffff880`1111a3c3 00000000`00000000 : atikmdag+0xbca32
fffff880`0dd53a38 00000001`81ec0000 : 00000000`00000000 fffff880`1111a3c3 00000000`00000000 00000000`0000001f : 0xfffff8a0`20426010
fffff880`0dd53a40 00000000`00000000 : fffff880`1111a3c3 00000000`00000000 00000000`0000001f fffff8a0`20426010 : 0x00000001`81ec0000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+bca32
fffff880`1111aa32 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  atikmdag+bca32

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52ec068c

FAILURE_BUCKET_ID:  X64_0xA_atikmdag+bca32

BUCKET_ID:  X64_0xA_atikmdag+bca32

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_atikmdag+bca32

FAILURE_ID_HASH:  {558d4df9-ebe8-2363-0bd6-15e5cbea980a}

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

5: kd> lmvm atikmdag
start             end                 module name
fffff880`1105e000 fffff880`11dff000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Sat Feb 01 01:54:44 2014 (52EC068C)
    CheckSum:         00D501B6
    ImageSize:        00DA1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

BugCheck 24, {1904fb, fffff8800ca6a328, fffff8800ca69b80, fffff880012d2d5a}

*** WARNING: Unable to verify timestamp for aswFsBlk.sys
*** ERROR: Module load completed but symbols could not be loaded for aswFsBlk.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

 

[AlexPowerUp]

I tried those drivers long ago and it kept crashing. What else can it be?

 

[Arc]

I tried those drivers long ago and it kept crashing.

Which drivers? Let us see a BSOD caused by that driver? Otherwise I cannot decide.

What else can it be?

The question should not be "what it can be" but it should be "what it is". In order to determine what it is, do complete the earlier steps and report us back.

Work on fact and not on probability.

 

[AlexPowerUp]

I installed that drivers and disabled turbocore on BIOS (i have an AMD fx8120). It seems to work, but I think it needs more testing. If it crashes another time i will post it in there. Thanks <3

 

[Arc]

No problem Alex. We are right here.

 

[AlexPowerUp]

Hi again! It crashed me again while playing Battlefield 3. About 5 minutes after getting into a game. As I can see in bluescreenviewer, the cause is ntoskrnl, so I suppose that it's probably an OS problem and I should try reinstalling everything, but i will wait your answer. Thanks, again.

 

[Arc]

ntoskrnl is the kernel on which the BSOD takes place. When the dump recording mechanism fails to detect the actual reason behind it, it wrongly blames the kernel itself.

It never fails.

So, a clean install is not a must. But it is always good. If you want to go for it, I have nothing to say against it.

Let us know about your decision. If you go for a clean install, we will not suggest any other steps right now. But if not, I would suggest you to run Driver Verifier.

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.