Windows 7 Ultimate x64 DMP File

[DoubleGee]

Hello, everyone, My Win 7 ultimate has been working great since I have installed it, but few minutes ago, my laptop froze and I had to restart. I do not know how to open a dmp file, so here is the link for download > RapidShare: 1-CLICK Web hosting - Easy Filehosting
I would appreciate any help regarding the problem, and can any one tell me what is "the message" in the DMP file.
Thanks in advance

 

[zigzag3143]

Hello, everyone, My Win 7 ultimate has been working great since I have installed it, but few minutes ago, my laptop froze and I had to restart. I do not know how to open a dmp file, so here is the link for download > RapidShare: 1-CLICK Web hosting - Easy Filehosting
I would appreciate any help regarding the problem, and can any one tell me what is "the message" in the DMP file.
Thanks in advance

Hey DG

What version of win 7 are you running? did you download it from MS or buy it?

I am running the dmp now and getting some unusual returns

Ken J

 

[zigzag3143]

Hello, everyone, My Win 7 ultimate has been working great since I have installed it, but few minutes ago, my laptop froze and I had to restart. I do not know how to open a dmp file, so here is the link for download > RapidShare: 1-CLICK Web hosting - Easy Filehosting
I would appreciate any help regarding the problem, and can any one tell me what is "the message" in the DMP file.
Thanks in advance

Hi and welcome

the cause of this crach was probably the ataport.sys. because of the nature of the crash and the odd returns I got there was very little data in it

Bugcheck 124 is almost always hardware

I would
update all the critical drivers including bios, video, usb, etc
run system file check to verify and repair system files
to do so type cmd in search>right click and ru as admin>SFC /SCANNOW

as usual if you are overclocking stop
if you have a raid update its driver

Ken J+

EDITED: 19:49:22 KJ

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\120909-24148-01(2).dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
[B]*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64[/B]
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02a54000 PsLoadedModuleList = 0xfffff800`02c91e50
Debug session time: Wed Dec  9 18:52:56.672 2009 (GMT-5)
System Uptime: 0 days 0:00:12.294
[B]Unable to load image ntoskrnl.exe, Win32 error 0n2[/B]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.
[B]
BugCheck 124, {0, fffffa80050174f8, 0, 0}
[/B][B]
***** Kernel symbols are WRONG. Please fix symbols to do analysis.[/B]

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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: nt!_WHEA_ERROR_RECORD_HEADER                  ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : hardware

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

 

[DoubleGee]

Hello, everyone, My Win 7 ultimate has been working great since I have installed it, but few minutes ago, my laptop froze and I had to restart. I do not know how to open a dmp file, so here is the link for download > RapidShare: 1-CLICK Web hosting - Easy Filehosting
I would appreciate any help regarding the problem, and can any one tell me what is "the message" in the DMP file.
Thanks in advance

Hey DG

What version of win 7 are you running? did you download it from MS or buy it?

I am running the dmp now and getting some unusual returns

Ken J

I have downloaded it. My Win is: Windows 7 Ultimate 7600 Build. (64bit) and what do you mean by unusual returns, I will try to download the latest drivers from my manufacturer's site.
Thanks for your help.

 

[DoubleGee]

zigzag3143 thanks for your help here is a screenshot of my CMD after the SFC /SCANNOW scan was completed >

 

[DoubleGee]

Hi all, while I was playing NFS Underground 2 on my brother's laptop it BSOD.
Configuration: ASUS K51AE, Win 7 Home Premium x64 OEM, 4GB RAM.
Could anyone tell me what's the reason for the BSOD in the dmp file from 14/02/2012 as well as the one from 15/01/2012. Thanks in advance.

Error message on restart:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000538
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880054AC836
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\021412-17893-01.dmp
C:\Users\####\AppData\Local\Temp\WER-35334-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Dump file 14-02-2012 - 14-02-2012-17893-01.dmp

Dump file 15-01-2012 - 15-01-2012-23540-01.dmp

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\BSODDmpFiles\DoubleGee\14-02-2012-17893-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e51670
Debug session time: Tue Feb 14 08:53:22.519 2012 (GMT-7)
System Uptime: 0 days 6:15:52.065
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {538, 2, 0, fffff880054ac836}

Unable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+59836 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000538, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880054ac836, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebb100
 0000000000000538 

CURRENT_IRQL:  2

FAULTING_IP: 
athrx+59836
fffff880`054ac836 0fb78038050000  movzx   eax,word ptr [rax+538h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Skype.exe

TRAP_FRAME:  fffff88003921d30 -- (.trap 0xfffff88003921d30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8003887770
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880054ac836 rsp=fffff88003921ec8 rbp=0000000000000000
 r8=fffffa8008886500  r9=0000000000000000 r10=fffff880009ed000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
athrx+0x59836:
fffff880`054ac836 0fb78038050000  movzx   eax,word ptr [rax+538h] ds:5010:00000000`00000538=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c881e9 to fffff80002c88c40

STACK_TEXT:  
fffff880`03921be8 fffff800`02c881e9 : 00000000`0000000a 00000000`00000538 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03921bf0 fffff800`02c86e60 : 00000000`00000000 fffffa80`04429d20 fffff880`009ec180 00000000`000000c3 : nt!KiBugCheckDispatch+0x69
fffff880`03921d30 fffff880`054ac836 : fffff880`054af0f1 fffffa80`03887770 fffff880`054a99f3 fffffa80`0863ec33 : nt!KiPageFault+0x260
fffff880`03921ec8 fffff880`054af0f1 : fffffa80`03887770 fffff880`054a99f3 fffffa80`0863ec33 00000000`000000c3 : athrx+0x59836
fffff880`03921ed0 fffffa80`03887770 : fffff880`054a99f3 fffffa80`0863ec33 00000000`000000c3 fffffa80`046e7470 : athrx+0x5c0f1
fffff880`03921ed8 fffff880`054a99f3 : fffffa80`0863ec33 00000000`000000c3 fffffa80`046e7470 fffffa80`03887770 : 0xfffffa80`03887770
fffff880`03921ee0 fffffa80`0863ec33 : 00000000`000000c3 fffffa80`046e7470 fffffa80`03887770 fffff880`03922430 : athrx+0x569f3
fffff880`03921ee8 00000000`000000c3 : fffffa80`046e7470 fffffa80`03887770 fffff880`03922430 fffff880`05481b20 : 0xfffffa80`0863ec33
fffff880`03921ef0 fffffa80`046e7470 : fffffa80`03887770 fffff880`03922430 fffff880`05481b20 fffffa80`046e7470 : 0xc3
fffff880`03921ef8 fffffa80`03887770 : fffff880`03922430 fffff880`05481b20 fffffa80`046e7470 fffff880`00000001 : 0xfffffa80`046e7470
fffff880`03921f00 fffff880`03922430 : fffff880`05481b20 fffffa80`046e7470 fffff880`00000001 fffffa80`08886550 : 0xfffffa80`03887770
fffff880`03921f08 fffff880`05481b20 : fffffa80`046e7470 fffff880`00000001 fffffa80`08886550 fffff880`054a6501 : 0xfffff880`03922430
fffff880`03921f10 fffffa80`046e7470 : fffff880`00000001 fffffa80`08886550 fffff880`054a6501 fffffa80`08886510 : athrx+0x2eb20
fffff880`03921f18 fffff880`00000001 : fffffa80`08886550 fffff880`054a6501 fffffa80`08886510 80000000`00000000 : 0xfffffa80`046e7470
fffff880`03921f20 fffffa80`08886550 : fffff880`054a6501 fffffa80`08886510 80000000`00000000 ffff0100`c0000001 : 0xfffff880`00000001
fffff880`03921f28 fffff880`054a6501 : fffffa80`08886510 80000000`00000000 ffff0100`c0000001 fffff880`00000002 : 0xfffffa80`08886550
fffff880`03921f30 fffffa80`08886510 : 80000000`00000000 ffff0100`c0000001 fffff880`00000002 00000000`000000c3 : athrx+0x53501
fffff880`03921f38 80000000`00000000 : ffff0100`c0000001 fffff880`00000002 00000000`000000c3 fffff880`0548f587 : 0xfffffa80`08886510
fffff880`03921f40 ffff0100`c0000001 : fffff880`00000002 00000000`000000c3 fffff880`0548f587 fffffa80`046dd030 : 0x80000000`00000000
fffff880`03921f48 fffff880`00000002 : 00000000`000000c3 fffff880`0548f587 fffffa80`046dd030 00000000`00000000 : 0xffff0100`c0000001
fffff880`03921f50 00000000`000000c3 : fffff880`0548f587 fffffa80`046dd030 00000000`00000000 00000000`01580000 : 0xfffff880`00000002
fffff880`03921f58 fffff880`0548f587 : fffffa80`046dd030 00000000`00000000 00000000`01580000 fffffa80`0863eb40 : 0xc3
fffff880`03921f60 fffffa80`046dd030 : 00000000`00000000 00000000`01580000 fffffa80`0863eb40 00000000`00000000 : athrx+0x3c587
fffff880`03921f68 00000000`00000000 : 00000000`01580000 fffffa80`0863eb40 00000000`00000000 fffff880`0548faef : 0xfffffa80`046dd030


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+59836
fffff880`054ac836 0fb78038050000  movzx   eax,word ptr [rax+538h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrx+59836

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4aca1ff5

FAILURE_BUCKET_ID:  X64_0xD1_athrx+59836

BUCKET_ID:  X64_0xD1_athrx+59836

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

1: kd> lmvm athrx
start             end                 module name
fffff880`05238000 fffff880`053b5000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Mon Oct 05 10:33:57 2009 (4ACA1FF5)
    CheckSum:         0017C3B2
    ImageSize:        0017D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The wireless adapter driver needs to be updated. I would help you find the correct driver, but you did not follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html, so I cannot determine which adapter is on the system.

Atheros drivers are difficult to find. Start with ATHEROS drivers for Microsoft Windows (Atheros?????) to look for the proper adapter and driver.

If the adapter is not an Atheros adapter, you will have to find the model of the device being used and the drivers associated with that manufacturer and the support page for the particular adapter. If you need help, please follow the instructions to provide us with more information about the adapter.