[elk123]

Hello, just a few minutes ago I got a bsod for the first time on my new laptop, which I got around a month ago. I wasn't doing anything special, a program called Sibelius open, which is quite often and I was sending an email. Norton internet security was also running, just like it always does. I checked the temperature of the processor not long before it bsod and they were both around 53c like they usually are.

Since yesterday the only thing I did was install a singpleplayer demo of crysis. A couple of weeks ago I tried down volting the computer because it got quite hot sometimes but soon after I put it back to it's original voltage.

After reading a thread about bsod I saw that someone was asked to attach the files in windows/minidump so a debug could be run, so I am attaching mine as a .rar file.

Here are my specs:

Hp Pavillion dv6 artist's edition

Windows Vista Home Premium 64 bit

4 GB Ram

AMD Turion X2 ultra-dual core mobile zm-82 2.2 ghz

ATI Radeon HD 4650


I hope this is enough,

Thank you

 

[DT Roberts]

0xD1, pointing to athrx.sys:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 0, fffffa60134d6a2e}

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+cea2e )

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

0: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffffa60134d6a2e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e79080
 0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
athrx+cea2e
fffffa60`134d6a2e ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff800039207a0 -- (.trap 0xfffff800039207a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000004900800 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa60134d6a2e rsp=fffff80003920930 rbp=0000000000000000
 r8=0000000004900800  r9=fffffa8006683800 r10=fffff78000000014
r11=0000000000000192 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
athrx+0xcea2e:
fffffa60`134d6a2e ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001ca0d2e to fffff80001ca0f90

STACK_TEXT:  
fffff800`03920658 fffff800`01ca0d2e : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`03920660 fffff800`01c9fc0b : 00000000`00000000 fffffa60`13218375 fffffa80`043e1c00 fffffa80`06539dd8 : nt!KiBugCheckDispatch+0x6e
fffff800`039207a0 fffffa60`134d6a2e : fffffa80`06677030 fffffa80`06678758 fffffa80`06677001 fffffa80`06683800 : nt!KiPageFault+0x20b
fffff800`03920930 fffffa80`06677030 : fffffa80`06678758 fffffa80`06677001 fffffa80`06683800 fffff800`03920a00 : athrx+0xcea2e
fffff800`03920938 fffffa80`06678758 : fffffa80`06677001 fffffa80`06683800 fffff800`03920a00 00000000`000019f9 : 0xfffffa80`06677030
fffff800`03920940 fffffa80`06677001 : fffffa80`06683800 fffff800`03920a00 00000000`000019f9 00000000`00000000 : 0xfffffa80`06678758
fffff800`03920948 fffffa80`06683800 : fffff800`03920a00 00000000`000019f9 00000000`00000000 fffffa80`06678758 : 0xfffffa80`06677001
fffff800`03920950 fffff800`03920a00 : 00000000`000019f9 00000000`00000000 fffffa80`06678758 fffffa80`06677030 : 0xfffffa80`06683800
fffff800`03920958 00000000`000019f9 : 00000000`00000000 fffffa80`06678758 fffffa80`06677030 fffffa80`0633a990 : 0xfffff800`03920a00
fffff800`03920960 00000000`00000000 : fffffa80`06678758 fffffa80`06677030 fffffa80`0633a990 fffffa80`063271a0 : 0x19f9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+cea2e
fffffa60`134d6a2e ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrx+cea2e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  494ca6b9

FAILURE_BUCKET_ID:  X64_0xD1_athrx+cea2e

BUCKET_ID:  X64_0xD1_athrx+cea2e

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

0: kd> lmvm athrx
start             end                 module name
fffffa60`13408000 fffffa60`13553000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Sat Dec 20 03:03:05 2008 (494CA6B9)
    CheckSum:         001551C0
    ImageSize:        0014B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

athrx.sys is your Atheros network adapter driver.

Norton sometimes blocks things that it shouldn't. It appears as though Norton blocked your network card from sending the email and caused the BSOD.

First, check for updated network drivers from your manufacturer's website.

 

[elk123]

Thanks.

Does it matter that I was still typing? I hadn't actually click send yet.

 

[DT Roberts]

Well, the fact that you weren't sending means that it wasn't caused by the email program itself. Still, the updated drivers could help.