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: Can anyone analyize minidump files? BSOD issues

20 Jul 2015   #1

Win 7 64-bit
Can anyone analyize minidump files? BSOD issues

I started blue-screening a couple days ago rather regularly, about 5 minutes after booting up. Once the laptop restarted itself, she won't blue screen again until I shut her down and start her up again. I have not installed or updated any drivers, or done much of anything lately, so I'm not sure what has caused her to start acting up.

Analysing these files is beyond me so I figured someone here may be able to help out. Any insight is greatly appreciated. When she does blue screen, at the bottom it'll say "STOP 00000x" and a whole lot of other numbers. Unfortunately I don't remember them all. If any extra information is needed to diagnose what's going on let me know.


My System SpecsSystem Spec
21 Jul 2015   #2

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

 Clean boot
Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\KoolKat77\Downloads\WITTINATOR-PC-20_07_2015__71131_10\071915-26145-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*
Symbol search path is: SRV*c:\symbols*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`03857000 PsLoadedModuleList = 0xfffff800`03a9e730
Debug session time: Mon Jul 20 03:21:34.952 2015 (UTC + 6:00)
System Uptime: 0 days 0:09:10.435
Loading Kernel Symbols

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck A, {80, 2, 1, fffff800038d582f}

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

Followup: MachineOwner

0: 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: 0000000000000080, 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: fffff800038d582f, address which referenced memory

Debugging Details:

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003b08100
GetUlongFromAddress: unable to read from fffff80003b081c0
 0000000000000080 Nonpaged pool


fffff800`038d582f 488717          xchg    rdx,qword ptr [rdi]




PROCESS_NAME:  taskhost.exe

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

TRAP_FRAME:  fffff8800ae18fc0 -- (.trap 0xfffff8800ae18fc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8800ae191d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800038d582f rsp=fffff8800ae19150 rbp=0000000000000000
 r8=fffff8800ae191d0  r9=00000000ffffffff r10=ffffffffffffffff
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff800`038d582f 488717          xchg    rdx,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800038cae69 to fffff800038cb8c0

fffff880`0ae18e78 fffff800`038cae69 : 00000000`0000000a 00000000`00000080 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0ae18e80 fffff800`038c9ae0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0ae18fc0 fffff800`038d582f : 00000000`00000000 fffff6fb`7da00000 fffffa80`0a14eb10 fffff680`000af000 : nt!KiPageFault+0x260
fffff880`0ae19150 fffff800`0398b08e : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`06aa4000 : nt!KeAcquireInStackQueuedSpinLock+0x5f
fffff880`0ae191a0 fffff800`0394949d : 00000030`0000006e fffff680`000af000 fffff680`000af000 000fffff`00000005 : nt!MiReleaseConfirmedPageFileSpace+0x5e
fffff880`0ae19220 fffff800`038b8b12 : 00000000`00000000 fffff800`0000f43a fffffa80`0a14eb10 fffffa80`0a14eea8 : nt! ?? ::FNODOBFM::`string'+0x45c56
fffff880`0ae19ab0 fffff880`0417d0a8 : ffffffff`ffffffff 00000000`0349f6f8 00000000`0349f6f0 00000980`00004000 : nt!NtFreeVirtualMemory+0x382
fffff880`0ae19bb0 ffffffff`ffffffff : 00000000`0349f6f8 00000000`0349f6f0 00000980`00004000 0000007f`fffffff8 : aswSP+0x130a8
fffff880`0ae19bb8 00000000`0349f6f8 : 00000000`0349f6f0 00000980`00004000 0000007f`fffffff8 00000000`00000004 : 0xffffffff`ffffffff
fffff880`0ae19bc0 00000000`0349f6f0 : 00000980`00004000 0000007f`fffffff8 00000000`00000004 00000000`0349f990 : 0x349f6f8
fffff880`0ae19bc8 00000980`00004000 : 0000007f`fffffff8 00000000`00000004 00000000`0349f990 00000002`00000002 : 0x349f6f0
fffff880`0ae19bd0 0000007f`fffffff8 : 00000000`00000004 00000000`0349f990 00000002`00000002 ffffffff`ffffffff : 0x00000980`00004000
fffff880`0ae19bd8 00000000`00000004 : 00000000`0349f990 00000002`00000002 ffffffff`ffffffff 00000000`0349f6f8 : 0x0000007f`fffffff8
fffff880`0ae19be0 00000000`0349f990 : 00000002`00000002 ffffffff`ffffffff 00000000`0349f6f8 00000000`0349f6f0 : 0x4
fffff880`0ae19be8 00000002`00000002 : ffffffff`ffffffff 00000000`0349f6f8 00000000`0349f6f0 00000000`00004000 : 0x349f990
fffff880`0ae19bf0 ffffffff`ffffffff : 00000000`0349f6f8 00000000`0349f6f0 00000000`00004000 fffffa80`0b4f8b50 : 0x00000002`00000002
fffff880`0ae19bf8 00000000`0349f6f8 : 00000000`0349f6f0 00000000`00004000 fffffa80`0b4f8b50 fffff800`038cab53 : 0xffffffff`ffffffff
fffff880`0ae19c00 00000000`0349f6f0 : 00000000`00004000 fffffa80`0b4f8b50 fffff800`038cab53 00000000`00000000 : 0x349f6f8
fffff880`0ae19c08 00000000`00004000 : fffffa80`0b4f8b50 fffff800`038cab53 00000000`00000000 00000000`2699dc6e : 0x349f6f0
fffff880`0ae19c10 fffffa80`0b4f8b50 : fffff800`038cab53 00000000`00000000 00000000`2699dc6e fffff880`0ae19c01 : 0x4000
fffff880`0ae19c18 fffff800`038cab53 : 00000000`00000000 00000000`2699dc6e fffff880`0ae19c01 00000000`000000fe : 0xfffffa80`0b4f8b50
fffff880`0ae19c20 00000000`7722dd9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0349f6b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7722dd9a


fffff880`0417d0a8 ??              ???


SYMBOL_NAME:  aswSP+130a8

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  aswSP.sys


FAILURE_BUCKET_ID:  X64_0xA_aswSP+130a8

BUCKET_ID:  X64_0xA_aswSP+130a8


FAILURE_ID_HASH_STRING:  km:x64_0xa_aswsp+130a8

FAILURE_ID_HASH:  {f69b88c7-7fe1-dc1f-db01-ace0ed447c67}

Followup: MachineOwner
Remove Avast!

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

Good and Free system security combination.

warning   Warning
Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Memtest should be done overnight.
My System SpecsSystem Spec

 Can anyone analyize minidump files? BSOD issues

Thread Tools

Similar help and support threads
Thread Forum
BSOD with minidump files.
This laptop has very random BSOD occurrences. I attempted to download the diagnostic tools but was unsuccessful. I wish I could add more detail other than the two more recent minidumps, but that is the best I have for now. Thank you so much.
BSOD Help and Support
BSOD with no minidump files!
OK guys, I've tried to do my research on this and I've done a LOT of troubleshooting so far. For the past 6 months, I have been getting BSOD about 3 times a week at complete random times. It mostly occurs overnight when I'm asleep. I have tried deactivating all hibernate and sleep...
BSOD Help and Support
Bsod Minidump files
Installed new 4890 and I've had bSOD's ever since. I was hoping someone could help.
BSOD Help and Support
BSOD - Need Help with minidump files
I have been having system crashes intermittantly and need some help undestanding my minidump files... Here's what I am seeing: Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File Mini Kernel Dump File:...
BSOD Help and Support
Win 7 BSOD Help w/minidump files
Here are the two latest minidump files Thanks Matt
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 20:43.
Twitter Facebook Google+