Sony Vaio BSOD

Hi

Im trying to fix a Sony Vaio PCG-71311M that randomly produces a BSOD. Its pops up and crashes so quick I don’t get a chance to see what it reports, and nothing useful in the action centre to report.

So far the hard drive has been replaced and the ram ( in various combinations) The CPU fan is clean and running but this is my next suspect as the machine itself gets hot and the fan is very quiet but I haven’t compared it to the same model. It seems to run for different lengths of time before BSOD and restarts.
Does anyone know where I can get a CPU fan for this laptop (in the UK) I think the part number is UDQFRZH14CF0. I did see a used one on ebay but I don’t know if this is such a good idea.

Also does anyone know if you can just replace the fan or do I need the whole heatsink.

Thanks in advance.

 

Are there any mini dumps in the C:\windows\minidump folder? zip them up ad atach thhem to a reply. if not turn them n.

 

2007 version of SFEP.sys will cause BSOD's on Sony's
It's an older version of the Sony Firmware Extension Parser - updated version available at the download site for your model.

Run Prime95 or Furmark in order to get the temps up quickly (and get the fan running). Links for them are here: http://www.carrona.org/hwdiag.html

 

Ok checking now - thank for the response I will let you know

 

Hi found these in the mini dump folder are these actual files as I cant seem to copy them just see them as file names.

012112-17487-01.dmp dated 21/01/12

020112-15194-01.dmp dated 01/02/12

 

They look right. You will need to attach them to a reply. you may need to zip them up first as I dont believe the forum will let you upload .dmp files

 

Here are the dmp files

 

A quick check shows that SFEP.sys (8/3/2007) is loaded in both dumps - refer back to post #3 and get that updated while I try to take a deeper look.

 

The only other 'old' driver I see loaded here is the athrx.sys, Atheros network adapter driver - http://www.atheros.cz/ holds the latest drivers for this, you will need to check via the documentation or Device Manager to find out exactly which model you have and download and install the latest.

The above is also the driver 'blamed' for both crashes, here's the basic debug output for one of them:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {94, 2, 0, fffff880044d67bd}

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+567bd )

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ac1100
 0000000000000094 

CURRENT_IRQL:  2

FAULTING_IP: 
athrx+567bd
fffff880`044d67bd 8b8094000000    mov     eax,dword ptr [rax+94h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880031fb470 -- (.trap 0xfffff880031fb470)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004e13a8c
rdx=fffffa8004e13a8c rsi=0000000000000000 rdi=0000000000000000
rip=fffff880044d67bd rsp=fffff880031fb600 rbp=0000000000000000
 r8=0000000000000000  r9=fffffa8004e13ae8 r10=fffff880045378e0
r11=00000000004bb645 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
athrx+0x567bd:
fffff880`044d67bd 8b8094000000    mov     eax,dword ptr [rax+94h] ds:00000000`00000094=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800028912a9 to fffff80002891d00

STACK_TEXT:  
fffff880`031fb328 fffff800`028912a9 : 00000000`0000000a 00000000`00000094 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031fb330 fffff800`0288ff20 : 00000000`00000000 fffffa80`0552a000 00000000`0000000b 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031fb470 fffff880`044d67bd : fffffa80`04e13a8c 00000000`08600000 00000000`00000000 00000000`00000018 : nt!KiPageFault+0x260
fffff880`031fb600 fffffa80`04e13a8c : 00000000`08600000 00000000`00000000 00000000`00000018 fffffa80`0477c56c : athrx+0x567bd
fffff880`031fb608 00000000`08600000 : 00000000`00000000 00000000`00000018 fffffa80`0477c56c 00000000`00000000 : 0xfffffa80`04e13a8c
fffff880`031fb610 00000000`00000000 : 00000000`00000018 fffffa80`0477c56c 00000000`00000000 00000000`00000000 : 0x8600000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+567bd
fffff880`044d67bd 8b8094000000    mov     eax,dword ptr [rax+94h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrx+567bd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4acea2b7

FAILURE_BUCKET_ID:  X64_0xD1_athrx+567bd

BUCKET_ID:  X64_0xD1_athrx+567bd

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

 

Thanks to all - wifi card drivers updated - had to uninstall the card to get it to load the new drivers.


been running for 3 hours now so fingers crossed.

 

Don't neglect to run a few off ... on cycles, sleep/wakes and hibernate/wakes too

Good luck!