Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD BCCode 1000009f Sony VAIO

26 May 2010   #1
onkynm

Windows XP
 
 
BSOD BCCode 1000009f Sony VAIO

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



My System SpecsSystem Spec
.
26 May 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by onkynm View Post
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
My System SpecsSystem Spec
31 May 2010   #3
onkynm

Windows XP
 
 

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.
My System SpecsSystem Spec
.

02 Jun 2010   #4
usasma
Microsoft MVP

 
 

Please do as zigzag3143 has suggested.
My System SpecsSystem Spec
04 Jun 2010   #5
onkynm

Windows XP
 
 

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...
My System SpecsSystem Spec
04 Jun 2010   #6
usasma
Microsoft MVP

 
 

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 )
Quote:
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.
My System SpecsSystem Spec
04 Jun 2010   #7
usasma
Microsoft MVP

 
 

AHA!!! I just found this: (from this link: Memtest86 - Download Page )
Quote:
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!
My System SpecsSystem Spec
Reply

 BSOD BCCode 1000009f Sony VAIO




Thread Tools




Similar help and support threads
Thread Forum
Another BSOD while idle BCCode:1000009f BCP1:0000000000000004 DRIVER_P
I continue to get BSOD when my laptop is idle. I followed the steps from my Jan issues. I've attached the latest set of files. Thank you so much for your help, surf1000 Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional...
BSOD Help and Support
BSOD while idle BCCode:1000009f BCP1:0000000000000004 DRIVER_POWER_STA
I have had this problem before but now I'm getting different BCP codes - my system will blue screen when it is idle and the fan appears to be running loud/higher than it should. I have updated my bluetooth driver as recommended when it blue screened on 12/31/2012 as well as my system profile on...
BSOD Help and Support
BSOD BCCode: 1000009f
Having problems with BSOD since July 20 2012 The Laptop will reboot. I have attached the .dmp files Regards
BSOD Help and Support
BSOD problem 1000009f sony s series laptop crashed and cant shutdown
BSOD problem Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.48 Locale ID: 1033 Additional information about the problem: BCCode: 1000009f BCP1: 0000000000000004 BCP2: 0000000000000258
BSOD Help and Support
BSOD on my Sony VAIO.
The specs for my user are for my HP desktop, so here are my Sony VAIO specs: System Manufacturer/Model Number Sony VAIO VPCCW17FX (~2 years old) OS Windows 7 Home Premium OEM 64 Bit (~1 month since clean install, 1 week since repair install) CPU Intel(R) Core(TM)2 Duo CPU T6600 @ 2.20GHz...
BSOD Help and Support
**Need Help!! BSOD Sony Vaio**
How can I fix this. I have scanned the disk and did a memory test and all came back normal. I can't boot in to safe mode, it just loads the files then stops. The last file it loads is CLASSPNP.SYS, then it stops. How can I fix this!! Thanks!
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 14:12.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App