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: Random BSODs and i don't know what to do.

08 Mar 2014   #1

Windows 7 Ultimate x64
Random BSODs and i don't know what to do.

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

My System SpecsSystem Spec
08 Mar 2014   #2

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

Hi AlexPowerUp.

Uninstall your installed latest version of the display driver.
Then clean up any possible leftover.
Then install version 13.9 WHQL only.
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                                    *
*                                                                             *

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


fffff800`038a1608 488930          mov     qword ptr [rax],rsi




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
fffff800`038a1608 488930          mov     qword ptr [rax],rsi ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800038da229 to fffff800038dac80

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


fffff880`1111aa32 ??              ???


SYMBOL_NAME:  atikmdag+bca32

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys


FAILURE_BUCKET_ID:  X64_0xA_atikmdag+bca32

BUCKET_ID:  X64_0xA_atikmdag+bca32


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
My System SpecsSystem Spec
08 Mar 2014   #3

Windows 7 Ultimate x64

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

09 Mar 2014   #4

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

Quote   Quote: Originally Posted by AlexPowerUp View Post
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.
Quote   Quote: Originally Posted by AlexPowerUp View Post
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.
My System SpecsSystem Spec
09 Mar 2014   #5

Windows 7 Ultimate x64

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
My System SpecsSystem Spec
09 Mar 2014   #6

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

No problem Alex. We are right here.
My System SpecsSystem Spec
15 Mar 2014   #7

Windows 7 Ultimate x64

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.
My System SpecsSystem Spec
15 Mar 2014   #8

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec

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

Thread Tools

Similar help and support threads
Thread Forum
Random BSODs during random tasks, numerous BCCodes.
For some reason, my last post here regarding this issue was deleted after ~2 days without warning or response from anyone, so here I am again now that I can view this section once more. For the past week or so now, my PC has been randomly BSODing at seemingly random times.. mostly when gaming....
BSOD Help and Support
Random BSODs with random intervals (have files from SF diagnostics)
Getting random BSODS from 5 times a week to 2 times a week to 0 times a week its really random and i hope the files can describe the issue.
BSOD Help and Support
BSODs, Random times, random error messages.
Hi all, first off, thanks for reading this. Basically, my current build is about 2-3 years old, the newest thing being my PSU (which I replaced after several issues with the GPU drivers constantly crashing, turns out it wasn't the power anyway...) For the past few weeks, I've been having...
BSOD Help and Support
Random BSODs Caused by Random Files with Differing Stop Codes
Since 16 Feb 2013 to today 22 Feb 2013 I've been getting Blue Screens; these appear to be completely random each time with different stop codes and (according to Blue Screen Veiw) are caused by different files. For example; Caused by ntkrnlpa.exe or atikmdag.exe, or ks,sys, or USBPORT.SYS, or...
BSOD Help and Support
Random BSODs during random tasks. Latest error: 0x1000007e
Hey folks. Acer AS4830TG-6808 Win7 Home Premium x64 Acer OEM Machine is less than a month old Added 4GB Ram stick (PNY, now total of 8GB) Have been getting random BSODs over the last week or so. I'm not sure of the reasoning, however I suspect it may be gaming related. Errors began while...
BSOD Help and Support

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 03:26.
Twitter Facebook Google+