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: Help with BSOD, dump analysis attached

13 Jun 2015   #1
samlfc

Greater London
 
 
Help with BSOD, dump analysis attached

Hello, can someone please help me with the following BSOd analysis:

Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.

Show DivPrimary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Homepage - OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`0401b000 PsLoadedModuleList = 0xfffff800`04262730
Debug session time: Sat Jun 13 06:07:33.647 2015 (UTC - 4:00)
System Uptime: 0 days 1:34:05.427
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+0
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1e_0

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff880038cd808 -- (.exr 0xfffff880038cd808)
ExceptionAddress: fffff880018f70d2 (storport!StorPortNotification+0x0000000000000022)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff880038cd8b0 -- (.trap 0xfffff880038cd8b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=303036783036315f rbx=0000000000000000 rcx=0000000000001003
rdx=fffffa801a4a6000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880018f70d2 rsp=fffff880038cda40 rbp=fffffa800dd69250
r8=0000000000000002 r9=0000000000000000 r10=fffffa801a4a6000
r11=fffff880038cdab0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
storport!StorPortNotification+0x22:
fffff880`018f70d2 488b18 mov rbx,qword ptr [rax] ds:30303678`3036315f=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800040872be to fffff8000408f890

STACK_TEXT:
fffff880`038cc8e8 fffff800`040872be : fffffa80`14eacbe0 00000000`00000000 fffff880`038cd060 fffff800`040bb470 : nt!KeBugCheck
fffff880`038cc8f0 fffff800`040bb13d : fffff800`042a33d4 fffff800`041da71c fffff800`0401b000 fffff880`038cd808 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`038cc920 fffff800`040b9f15 : fffff800`041e2c90 fffff880`038cc998 fffff880`038cd808 fffff800`0401b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`038cc950 fffff800`040cae81 : fffff880`038cd808 fffff880`038cd060 fffff880`00000000 fffffa80`0df42370 : nt!RtlDispatchException+0x415
fffff880`038cd030 fffff800`0408ef42 : fffff880`038cd808 00000000`00000000 fffff880`038cd8b0 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`038cd6d0 fffff800`0408d84a : 00000000`00000001 fffffa80`14ab09a0 fffffa80`141dcd60 00000000`00000030 : nt!KiExceptionDispatch+0xc2
fffff880`038cd8b0 fffff880`018f70d2 : fffffa80`0df5ba73 fffff880`012d50de 00000000`00000202 fffffa80`0df42370 : nt!KiGeneralProtectionFault+0x10a
fffff880`038cda40 fffff880`012d3aa8 : fffffa80`0dd2ecc0 fffffa80`1a4a6000 00000000`00000002 00000000`00000000 : storport!StorPortNotification+0x22
fffff880`038cdac0 fffffa80`0dd2ecc0 : fffffa80`1a4a6000 00000000`00000002 00000000`00000000 fffff880`038cdb38 : iaStorA+0x63aa8
fffff880`038cdac8 fffffa80`1a4a6000 : 00000000`00000002 00000000`00000000 fffff880`038cdb38 00000000`00000002 : 0xfffffa80`0dd2ecc0
fffff880`038cdad0 00000000`00000002 : 00000000`00000000 fffff880`038cdb38 00000000`00000002 00000000`0002283a : 0xfffffa80`1a4a6000
fffff880`038cdad8 00000000`00000000 : fffff880`038cdb38 00000000`00000002 00000000`0002283a fffff880`012dabec : 0x2


STACK_COMMAND: kb

FOLLOWUP_IP:
storport!StorPortNotification+22
fffff880`018f70d2 488b18 mov rbx,qword ptr [rax]

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: storport!StorPortNotification+22

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: storport

IMAGE_NAME: storport.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 52f04432

FAILURE_BUCKET_ID: X64_0x1e_0_storport!StorPortNotification+22

BUCKET_ID: X64_0x1e_0_storport!StorPortNotification+22

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

I had HWMointor running, was watching a program with VLC, and sound stuttered, picture froze then this BSOD. Been having issues with Device Driver Stopped Responding But Has Now Recovered ever since I upgraded my case fans and CPU water cooler. Rechecked all the cables but can't figure out why it is happening. I have a Corsair 1050W PSU and one Evga GTX 980 Sc 2.0. Bought new RAM still no joy, now this BSOD. I might have been running AISuite Monitor and HWMointor when the crash happened. Mobo P9X79-pro.


My System SpecsSystem Spec
.
13 Jun 2015   #2
SGT Oddball

 

Please follow the instructions here: Blue Screen of Death (BSOD) Posting Instructions
My System SpecsSystem Spec
13 Jun 2015   #3
samlfc

Greater London
 
 

Hello, sorry about that, please find attached the zip.file.
My System SpecsSystem Spec
.

13 Jun 2015   #4
SGT Oddball

 

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8016116890, fffff800048073d8, fffffa8018abec10}
*** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
Probably caused by : asmthub3.sys
Followup: MachineOwner
---------
Code:
*******************************************************************************
*                                                                             *
*                        
Bugcheck 
Analysis                                    
*
*                                                                             
*
*******************************************************************************

 
Use !analyze -v to get detailed debugging information.

 
BugCheck 1E, {0, 0, 0, 0}

 
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module 
load completed but symbols could not be loaded for 
iaStorA.sys
*************************************************************************
***                                                                   
***
***                                                                   
***
***    Either you specified an unqualified symbol, or your 
debugger   ***
***    doesn't have full symbol 
information.  Unqualified symbol      
***
***    resolution is turned off by default. Please either 
specify a   ***
***    fully qualified symbol 
module!symbolname, or enable resolution ***
***    of 
unqualified symbols by typing ".symopt- 100". Note that   
***
***    enabling unqualified symbol resolution with network 
symbol     ***
***    server shares in the 
symbol path may cause the debugger to     
***
***    appear to hang for long periods of time when an 
incorrect      ***
***    symbol name 
is typed or the network symbol server is down.     
***
***                                                                   
***
***    For some commands to work properly, your symbol 
path           
***
***    must point to .pdb files that have full type 
information.      
***
***                                                                   
***
***    Certain .pdb files (such as the public OS symbols) 
do not      ***
***    contain the 
required information.  Contact the group that      
***
***    provided you with these symbols if you need this 
command to    ***
***    
work.                                                          
***
***                                                                   
***
***    Type referenced: 
ExceptionRecord                               
***
***                                                                   
***
*************************************************************************
*************************************************************************
***                                                                   
***
***                                                                   
***
***    Either you specified an unqualified symbol, or your 
debugger   ***
***    doesn't have full symbol 
information.  Unqualified symbol      
***
***    resolution is turned off by default. Please either 
specify a   ***
***    fully qualified symbol 
module!symbolname, or enable resolution ***
***    of 
unqualified symbols by typing ".symopt- 100". Note that   
***
***    enabling unqualified symbol resolution with network 
symbol     ***
***    server shares in the 
symbol path may cause the debugger to     
***
***    appear to hang for long periods of time when an 
incorrect      ***
***    symbol name 
is typed or the network symbol server is down.     
***
***                                                                   
***
***    For some commands to work properly, your symbol 
path           
***
***    must point to .pdb files that have full type 
information.      
***
***                                                                   
***
***    Certain .pdb files (such as the public OS symbols) 
do not      ***
***    contain the 
required information.  Contact the group that      
***
***    provided you with these symbols if you need this 
command to    ***
***    
work.                                                          
***
***                                                                   
***
***    Type referenced: 
ContextRecord                                 
***
***                                                                   
***
*************************************************************************
*************************************************************************
***                                                                   
***
***                                                                   
***
***    Either you specified an unqualified symbol, or your 
debugger   ***
***    doesn't have full symbol 
information.  Unqualified symbol      
***
***    resolution is turned off by default. Please either 
specify a   ***
***    fully qualified symbol 
module!symbolname, or enable resolution ***
***    of 
unqualified symbols by typing ".symopt- 100". Note that   
***
***    enabling unqualified symbol resolution with network 
symbol     ***
***    server shares in the 
symbol path may cause the debugger to     
***
***    appear to hang for long periods of time when an 
incorrect      ***
***    symbol name 
is typed or the network symbol server is down.     
***
***                                                                   
***
***    For some commands to work properly, your symbol 
path           
***
***    must point to .pdb files that have full type 
information.      
***
***                                                                   
***
***    Certain .pdb files (such as the public OS symbols) 
do not      ***
***    contain the 
required information.  Contact the group that      
***
***    provided you with these symbols if you need this 
command to    ***
***    
work.                                                          
***
***                                                                   
***
***    Type referenced: 
ExceptionRecord                               
***
***                                                                   
***
*************************************************************************
*************************************************************************
***                                                                   
***
***                                                                   
***
***    Either you specified an unqualified symbol, or your 
debugger   ***
***    doesn't have full symbol 
information.  Unqualified symbol      
***
***    resolution is turned off by default. Please either 
specify a   ***
***    fully qualified symbol 
module!symbolname, or enable resolution ***
***    of 
unqualified symbols by typing ".symopt- 100". Note that   
***
***    enabling unqualified symbol resolution with network 
symbol     ***
***    server shares in the 
symbol path may cause the debugger to     
***
***    appear to hang for long periods of time when an 
incorrect      ***
***    symbol name 
is typed or the network symbol server is down.     
***
***                                                                   
***
***    For some commands to work properly, your symbol 
path           
***
***    must point to .pdb files that have full type 
information.      
***
***                                                                   
***
***    Certain .pdb files (such as the public OS symbols) 
do not      ***
***    contain the 
required information.  Contact the group that      
***
***    provided you with these symbols if you need this 
command to    ***
***    
work.                                                          
***
***                                                                   
***
***    Type referenced: 
ContextRecord                                 
***
***                                                                   
***
*************************************************************************
Probably 
caused by : iaStorA.sys ( iaStorA+63aa8 )

 
Followup: MachineOwner
---------
You have two dumps both pointing to different drivers, see bellow for details and see if you can find updates.

Driver Reference Table - asmthub3.sys
Driver Reference Table - iaStorA.sys
My System SpecsSystem Spec
Reply

 Help with BSOD, dump analysis attached




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Across Many identical systems. Need Dump analysis
Hello, We have 45 systems that are all running on identical hardware: Custom Computer MB: Intel X58 Proc: Intel i7 HT enabled Mem: 8GB DDR3 1066 Int. Sound 1 x 500GB 7200 RPM Sata 750W PS
BSOD Help and Support
BSOD crash usbport.sys suspected, please help with dump file analysis
I have an Asus G53JW notebook that has BSOD failures. Tried updating all drivers with Driver Reviver, run memtest86+ to check ram and checked disk with SeaTools for Windows but no faults so far. The notebook has no USB devices connected externally when the BSOD occurs, on most occasions the BSOD...
BSOD Help and Support
BSOD Physical Dump Analysis Help
Hello! I have a Packard Bell preinstalled laptop. It's been months that is working fine and just yesterday, the Windows can not start. Startuprepairoffline appears everytime I restart my computer. So I decided to restore my sytem to factory default using the backup disc I made. And then, an icon...
BSOD Help and Support
BSOD, Crash Dump Analysis
Hello, For some time now, I have been having a lot of BSODs. Like up to 5 times a day. Sometimes it happens after a long time idling, sometimes when I stress the CPU. It can happen when I close my session, try to close the computer or restart it. I had an overclock on everything, but for the...
BSOD Help and Support
Another BSOD Dump file analysis needed please
Hey guys I just got a BSOD and was wondering if anyone could tell me the cause thanks in advance if anyone knows a good dump analysis program could you also give me a link .
BSOD Help and Support
BSOD Dump analysis - please help
Hi, I would be very grateful if a kindly guru could look at a BSOD dump for me please. Am running Win 7 Professional 64bit on an i7 system with 4Gb DDr3 RAM. No overclocking, no RAID, no Antivirus, just Windows firewall. Mainly use system to run MS FSX. BSODs have occurred randomly over last 3...
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 05:53.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App