BSOD BCCode 1000009f Sony VAIO

onkynm · 26 May 2010

Hi all,

i need a hint/advice regarding this BSOD's which i get on a Sony VAIO VGN-Z51WG . All hardware tests were and are OK.
It was send once in service because of the same behavior and still has this problem : when it is powered from stand by state, randomly give this BSOD

zigzag3143 · 26 May 2010

onkynm said:

Hi all,

i need a hint/advice regarding this BSOD's which i get on a Sony VAIO VGN-Z51WG . All hardware tests were and are OK.
It was send once in service because of the same behavior and still has this problem : when it is powered from stand by state, randomly give this BSOD

These were all caused by memory corruption. To test your memory download memtestx86, burn it to cd, and run for at least 5 passes

I also noticed that your Qualcomm driver appeared in most of these so I would re-instll the newest driver

Let us know if you need help

Ken

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May  6 06:57:22.014 2010 (GMT-4)
System Uptime: 6 days 5:53:35.762
BugCheck 1000009F, {4, 258, fffffa800551b680, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for qcusbnetsny.sys
*** ERROR: Module load completed but symbols could not be loaded for qcusbnetsny.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Apr 28 04:18:07.896 2010 (GMT-4)
System Uptime: 0 days 11:23:18.644
BugCheck 1000009F, {4, 258, fffffa800551db60, fffff80003f234d0}
*** WARNING: Unable to verify timestamp for qcusbnetsny.sys
*** ERROR: Module load completed but symbols could not be loaded for qcusbnetsny.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Apr 27 11:03:33.296 2010 (GMT-4)
System Uptime: 0 days 9:50:53.903
BugCheck 1000009F, {4, 258, fffffa8005500b60, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for qcusbnetsny.sys
*** ERROR: Module load completed but symbols could not be loaded for qcusbnetsny.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 24 20:23:07.679 2010 (GMT-4)
System Uptime: 3 days 9:36:39.729
BugCheck 1000009F, {4, 258, fffffa800551c680, fffff800043294d0}
*** WARNING: Unable to verify timestamp for qcusbnetsny.sys
*** ERROR: Module load completed but symbols could not be loaded for qcusbnetsny.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 08:44:40.100 2010 (GMT-4)
System Uptime: 0 days 3:17:41.708
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 9F, {4, 258, fffffa800551a040, fffff80000b9c4d0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x9F
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May 20 11:00:05.671 2010 (GMT-4)
System Uptime: 0 days 20:22:29.932
BugCheck 1000009F, {4, 258, fffffa800550e040, fffff80000b9c4d0}
*** WARNING: Unable to verify timestamp for qcusbnetsny.sys
*** ERROR: Module load completed but symbols could not be loaded for qcusbnetsny.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 19 09:33:42.513 2010 (GMT-4)
System Uptime: 0 days 7:45:25.634
BugCheck 9F, {3, fffffa8008c55060, fffff8000431c4d8, fffffa8007b47770}
Probably caused by : WinUSB.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 18 06:01:01.484 2010 (GMT-4)
System Uptime: 4 days 9:42:01.232
BugCheck 1000009F, {4, 258, fffffa8005500b60, fffff80000ba2740}
*** WARNING: Unable to verify timestamp for qcusbnetsny.sys
*** ERROR: Module load completed but symbols could not be loaded for qcusbnetsny.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 12 02:04:27.483 2010 (GMT-4)
System Uptime: 4 days 0:43:17.231
BugCheck 1000009F, {4, 258, fffffa8005519680, fffff80003f214d0}
*** WARNING: Unable to verify timestamp for qcusbnetsny.sys
*** ERROR: Module load completed but symbols could not be loaded for qcusbnetsny.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May  7 10:28:45.817 2010 (GMT-4)
System Uptime: 0 days 9:56:53.938
BugCheck 1000009F, {4, 258, fffffa80054ff040, fffff80003f214d0}
*** WARNING: Unable to verify timestamp for qcusbnetsny.sys
*** ERROR: Module load completed but symbols could not be loaded for qcusbnetsny.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System

onkynm · 31 May 2010

Thank you for answer,

I didn't use memtest but i made all hardware internal tests, laptop has his own diagnostics test (including memory) and all have passed.

usasma · 02 Jun 2010

Please do as zigzag3143 has suggested.

onkynm · 04 Jun 2010

I run the Memtest-86 v3.5 and 3.4 . Laptop has 2 memory modules 2GB and 4GB. For the 2GB module tests were ok. The 4GB module if i test it with v3.5 at some point ( 6% ) resets the computer all the time. With version 3.4 no errors on first pass...

usasma · 04 Jun 2010

Is the memory on the QVL (Qualified Vendor List) for your laptop? If it came with the laptop, then it's not a problem.

Here's a summary of the differences between v3.4 and v3.5 (from this link: Memtest86 - Memory Diagnostic Change Log Page )

Enhancements in v3.5 (3/Jan/2009)

Limited support for execution with multiple CPUs. CPUs are selected round-robin or sequential for each test.
Support for detection of additional chipsets. (from Memtest86+ v2.11).
Additions and corrections for CPU detection including reporting of L3 cache.
Reworked information display for better readability and new information.
Abbreviated iterations for first pass.
Enhancements to memory sizing.
Misc bug fixes.

Try this free memory test to see if it successfully completes the tests: Memtest86+ - Advanced Memory Diagnostic Tool
This isn't a substitute for the other test - it's in addition to it. The reason for this is that there's something causing the system to reboot - and if it's bad RAM we'll need a test to confirm that. If it's just a "glitch", then several "clean" memory tests will support that supposition.

usasma · 04 Jun 2010

AHA!!! I just found this: (from this link: Memtest86 - Download Page )

Memtest86 3.5 Release - Less than 4GB only (3/Jan/09)

ISO's include a boot menu that allows selection of version 3.5, version 3.4 and the experimental SMP version of 3.5 that supports multiple CPUs. Version 3.5 currently has a bug that causes the test to crash when testing 4Gb or more of memory. Memtest86 is a standalone program that does not require or use any operating system for execution. The version of Windows or Linux being used is irrelavent for execution. However, you must use Windows or Linux to create a bootable CD, Floppy or USB key. The Windows and Linux packages are identical except for the installaion methods. Memtest86 supports 64 bit CPUs.
Memtest86 3.4a Release (27/Dec/2007)

Version 3.5 does not work with 4+ GB of memory. Please use the 3.4 release for testing 4GB or more of memory.

Looks like that's the problem with the 4gB stick!