Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD on new Sony Vaio VGN-FW455J


  • Please log in to reply
1 reply to this topic

#1 Jason1235

Jason1235

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:55 AM

Posted 01 September 2009 - 06:17 PM

I frequently get BSOD on a new Sony Vaio VGN-FW455J (Windows Vista, 4GB RAM, uninstalled the Norton it came with and added Microsoft One Care. Did all the available window updates and latest Sony drivers. Still get BSOD frequently. Seems kind of random. Sometimes happens when I turn the wireless on/off. Sometimes just seemingly random... Passed Windows memory tests. Boots fine. Lots of wireless connectivity errors (Sometimes) compared to the other computers in the house... flipping it on & off corrects. Any ideas how I should proceed from here to stop the BSOD?

BSOD on new Sony VGN-FW455J:

Some Event View errors:

Source: WMI
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Souce: VzCdbSvc
Failed to load the plug-in module. (GUID = {56F9312C-C989-4E04-8C23-299DEE3A36F5})(Error code = 0x80042019)




The following boot-start or system-start driver(s) failed to load:
DMICall
SRTSP
SRTSPX



\SystemRoot\SysWow64\DRIVERS\DMICall.sys
000000000200300000000000240400C0000000006B0300C000000000000000000000000000000000
\SystemRoot\SysWow64\DRIVERS\DMICall.sys has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.







BSOD Dump logs:





Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report0fe3050e\Mini090109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.22477.amd64fre.vistasp1_ldr.090722-0700
Machine Name:
Kernel base = 0xfffff800`02210000 PsLoadedModuleList = 0xfffff800`023d2db0
Debug session time: Tue Sep 1 09:41:38.446 2009 (GMT-5)
System Uptime: 1 days 12:48:01.260
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800025d6b8c, fffffa60019f5798, fffffa60019f5170}

Probably caused by : ntkrnlmp.exe ( nt!IopFreeRelationList+2c )

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









Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report0fe3050e\Mini090109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.22477.amd64fre.vistasp1_ldr.090722-0700
Machine Name:
Kernel base = 0xfffff800`02210000 PsLoadedModuleList = 0xfffff800`023d2db0
Debug session time: Tue Sep 1 09:41:38.446 2009 (GMT-5)
System Uptime: 1 days 12:48:01.260
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800025d6b8c, fffffa60019f5798, fffffa60019f5170}

Probably caused by : ntkrnlmp.exe ( nt!IopFreeRelationList+2c )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800025d6b8c, The address that the exception occurred at
Arg3: fffffa60019f5798, Exception Record Address
Arg4: fffffa60019f5170, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!IopFreeRelationList+2c
fffff800`025d6b8c 44392f cmp dword ptr [rdi],r13d

EXCEPTION_RECORD: fffffa60019f5798 -- (.exr 0xfffffa60019f5798)
ExceptionAddress: fffff800025d6b8c (nt!IopFreeRelationList+0x000000000000002c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffffa60019f5170 -- (.cxr 0xfffffa60019f5170)
rax=fffffa8003cb1b01 rbx=fffff88000a4f698 rcx=fffff88000a4f698
rdx=fffffa8003cb1b01 rsi=fffff88000a4f6a8 rdi=0075007400720069
rip=fffff800025d6b8c rsp=fffffa60019f59d0 rbp=0000000000000000
r8=fffffa80085e11d0 r9=5000c6b64a000000 r10=0000000000000000
r11=00000000000007ff r12=fffff80002408b20 r13=0000000000000000
r14=0000000000000000 r15=0000000000000008
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!IopFreeRelationList+0x2c:
fffff800`025d6b8c 44392f cmp dword ptr [rdi],r13d ds:002b:00750074`00720069=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002435080
ffffffffffffffff

FOLLOWUP_IP:
nt!IopFreeRelationList+2c
fffff800`025d6b8c 44392f cmp dword ptr [rdi],r13d

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff80002640417 to fffff800025d6b8c

STACK_TEXT:
fffffa60`019f59d0 fffff800`02640417 : fffffa80`085e11d0 00000000`00000001 fffffa80`0844d060 fffff800`0247438c : nt!IopFreeRelationList+0x2c
fffffa60`019f5a10 fffff800`02640555 : fffffa80`085e11d0 fffffa80`0620e9c8 fffffa80`0620e990 00000000`00000007 : nt!PnpDelayedRemoveWorker+0x97
fffffa60`019f5a60 fffff800`0233bc69 : 00000000`00000007 00000000`00000001 00000000`00000000 fffffa80`07efc010 : nt!PnpChainDereferenceComplete+0x115
fffffa60`019f5aa0 fffff800`02644d79 : 00000000`00000000 fffffa80`0844d000 fffffa80`087ec930 00000000`00000001 : nt!PnpIsChainDereferenced+0xc9
fffffa60`019f5b20 fffff800`02644ffc : fffffa60`019f5cf8 fffffa80`05d59400 fffffa80`03cb1b00 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xf99
fffffa60`019f5c70 fffff800`025456c7 : 00000000`00000001 fffffa80`05d59490 fffff880`09c3c250 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffffa60`019f5ca0 fffff800`02269e4a : fffff800`02471494 fffff880`0a1d1010 fffff800`0239f8f8 fffffa80`03cb1bb0 : nt! ?? ::NNGAKEGL::`string'+0x4a314
fffffa60`019f5cf0 fffff800`02481573 : fffffa80`05d59490 00000000`10000000 fffffa80`03cb1bb0 00000000`00000080 : nt!ExpWorkerThread+0x11a
fffffa60`019f5d50 fffff800`02298ff6 : fffffa60`005ec180 fffffa80`03cb1bb0 fffffa60`005f5d40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`019f5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!IopFreeRelationList+2c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a67e1a0

STACK_COMMAND: .cxr 0xfffffa60019f5170 ; kb

FAILURE_BUCKET_ID: X64_0x7E_nt!IopFreeRelationList+2c

BUCKET_ID: X64_0x7E_nt!IopFreeRelationList+2c

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

BC AdBot (Login to Remove)

 


#2 Jason1235

Jason1235
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:55 AM

Posted 02 September 2009 - 06:02 AM

Microsoft came back with a recommendation about uninstalling Windows update KB973879. Haven't crashed since then (fingers crossed). So now I just have the smaller issue of the wireless constantly disconnecting, unlike every other computer and device in the house. Maybe it's a linksys compatibility thing?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users