Win 8.1 BSOD MEMORY_MANAGEMENT (0x1a_3453) - Potential iastor.sys (Intel ICH9R) issue
After upgrading to Windows 8, then 8.1 from Windows 7 I have been experiencing frequent BSOD halts that appear to be related to the storage driver. Version 12.8 of the intel driver and utility has been used up until now. I have tried an older version (10.8)
of the driver and utility as that was reported to work will with Win 8. I have also (and currently) upgraded to the latest driver 12.9.0.1001 which was released only a few months ago. The issue appears to occur when the system is under high load for
extended periods (e.g. video rendering or extended game play). My guess is that as it's a memory management issue related to when the swap file is being extensively used.
I have a large number of mini-dumps available all with the same error id, and same sub-type. I have scanned the pc to confirm no infections, rootkits or other malware appear to be contributing to this issue. Suggestions or a fix would be greatly appreciated!
Here is some data from the latest full dump:
0: kd> .symfix
0: kd> .reload
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
0: kd> !analyze -vv
* Bugcheck Analysis
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003453, The subtype of the bugcheck.
Arg2: ffffe00001bae2c0
Arg3: 0000000000125529
Arg4: 0000000000000004
Debugging Details:
BUILD_VERSION_STRING: 9600.16452.amd64fre.winblue_gdr.131030-1505
SYSTEM_MANUFACTURER: System manufacturer
SYSTEM_PRODUCT_NAME: System manufacturer
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1403
BASEBOARD_MANUFACTURER: ASUSTeK Computer INC.
OVERLAPPED_UNLOADED_MODULE: Address regions for 'dump_iaStorA'
and 'dump_iaStorA.sys (unloaded)' overlap
BUGCHECK_STR: 0x1a_3453
CPU_MICROCODE: 6,f,b,0 (F,M,S,R) SIG: C1'00000000 (cache) C1'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: SILENTBOB
ANALYSIS_SESSION_TIME: 01-04-2014 00:07:43.0544
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff8021b1ff0a5 to fffff8021b1cdca0
STACK_TEXT:
ffffd000`21a4a8b8 fffff802`1b1ff0a5 : 00000000`0000001a 00000000`00003453 ffffe000`01bae2c0 00000000`00125529 : nt!KeBugCheckEx
ffffd000`21a4a8c0 fffff802`1b472fed : ffffffff`ffffffff ffffe000`06eae0b0 ffffe000`04e98a60 ffffe000`01bae5a8 : nt! ?? ::FNODOBFM::`string'+0x20f05
ffffd000`21a4a960 fffff802`1b472ae9 : ffffe000`01bae2c0 ffffe000`04e98a60 ffffe000`01bae5a8 00000000`00000001 : nt!MmDeleteProcessAddressSpace+0x35
ffffd000`21a4a9a0 fffff802`1b4aebf8 : 00000000`00000000 00000000`00000000 ffffe000`01bae2c0 ffffe000`000c32f0 : nt!PspProcessDelete+0x199
ffffd000`21a4aa40 fffff802`1b0bb60f : 00000000`00000000 ffffd000`21a4ab69 ffffe000`01bae2c0 ffffe000`07eee000 : nt!ObpRemoveObjectRoutine+0x64
ffffd000`21a4aaa0 fffff802`1b10a3d2 : ffffe000`07eee000 ffffe000`07eeede8 ffffe000`07eeeff8 ffffe000`07eee048 : nt!ObfDereferenceObject+0x8f
ffffd000`21a4aae0 fffff802`1b4769b5 : 00000000`00000000 00000000`00000000 ffffd000`21a4ab69 ffffe000`07eeede8 : nt!MmFreeAccessPfnBuffer+0x22
ffffd000`21a4ab10 fffff802`1b6805ce : 00000000`00000001 fffff802`1b31f928 00000000`00000000 ffffe000`00000000 : nt!PfpFlushBuffers+0x24d
ffffd000`21a4abd0 fffff802`1b10d2e4 : 00000000`00000000 ffffe000`04e98740 ffffe000`04e98740 ffffe000`000ee900 : nt!PfTLoggingWorker+0x156
ffffd000`21a4ad40 fffff802`1b1d42c6 : ffffd000`201d5180 ffffe000`04e98740 ffffd000`201e11c0 ffffc000`04accdd0 : nt!PspSystemThreadStartup+0x58
ffffd000`21a4ada0 00000000`00000000 : ffffd000`21a4b000 ffffd000`21a45000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+20f05
fffff802`1b1ff0a5 cc int 3
FAULT_INSTR_CODE: 85c6ffcc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+20f05
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 52718d9c
BUCKET_ID_FUNC_OFFSET: 20f05
FAILURE_BUCKET_ID: 0x1a_3453_VRF_nt!_??_::FNODOBFM::_string_
BUCKET_ID: 0x1a_3453_VRF_nt!_??_::FNODOBFM::_string_
ANALYSIS_SESSION_ELAPSED_TIME: fdb
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1a_3453_vrf_nt!_??_::fnodobfm::_string_
FAILURE_ID_HASH: {218cdcfe-f420-cf6d-10b1-e3e8392a9d9e}
Followup: MachineOwner
0: kd> kb
RetAddr : Args to Child
: Call Site
fffff802`1b1ff0a5 : 00000000`0000001a 00000000`00003453 ffffe000`01bae2c0 00000000`00125529 : nt!KeBugCheckEx
fffff802`1b472fed : ffffffff`ffffffff ffffe000`06eae0b0 ffffe000`04e98a60 ffffe000`01bae5a8 : nt! ?? ::FNODOBFM::`string'+0x20f05
fffff802`1b472ae9 : ffffe000`01bae2c0 ffffe000`04e98a60 ffffe000`01bae5a8 00000000`00000001 : nt!MmDeleteProcessAddressSpace+0x35
fffff802`1b4aebf8 : 00000000`00000000 00000000`00000000 ffffe000`01bae2c0 ffffe000`000c32f0 : nt!PspProcessDelete+0x199
fffff802`1b0bb60f : 00000000`00000000 ffffd000`21a4ab69 ffffe000`01bae2c0 ffffe000`07eee000 : nt!ObpRemoveObjectRoutine+0x64
fffff802`1b10a3d2 : ffffe000`07eee000 ffffe000`07eeede8 ffffe000`07eeeff8 ffffe000`07eee048 : nt!ObfDereferenceObject+0x8f
fffff802`1b4769b5 : 00000000`00000000 00000000`00000000 ffffd000`21a4ab69 ffffe000`07eeede8 : nt!MmFreeAccessPfnBuffer+0x22
fffff802`1b6805ce : 00000000`00000001 fffff802`1b31f928 00000000`00000000 ffffe000`00000000 : nt!PfpFlushBuffers+0x24d
fffff802`1b10d2e4 : 00000000`00000000 ffffe000`04e98740 ffffe000`04e98740 ffffe000`000ee900 : nt!PfTLoggingWorker+0x156
fffff802`1b1d42c6 : ffffd000`201d5180 ffffe000`04e98740 ffffd000`201e11c0 ffffc000`04accdd0 : nt!PspSystemThreadStartup+0x58
00000000`00000000 : ffffd000`21a4b000 ffffd000`21a45000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
0: kd> dv
Unable to enumerate locals, HRESULT 0x80004005
Private symbols (symbols.pri) are required for locals.
Type ".hh dbgerr005" for details.
You may have read this thread?
http://answers.microsoft.com/en-us/windows/forum/windows_8-system/bsod-power-driver-state-failure-iastorasys/4643832c-e2b6-49ca-b646-6ff135bc30f9?msgId=e7295c77-5107-4bb2-843b-3326b3786ee8
Have you run the Memtest86 tool for testing memories?
http://www.memtest.org/
Similar Messages
-
Iastors.sys 0xc000035a boot errors.
I am running OSD to upgrade xp to win7 from the xp OS. At another site the image deployed correctly. USMT runs then it reboots to winpe, formats the drive, installs windows ect......
Now im at another site and running the same TS but when the systems reboot to winpe I get the BSOD with iastors.sys 0xc000035a.
I went to Dells site and grabbed the WinPE 5.0 drivers and installed into my boot image. No change though same error. This is on a Dell 990. Same system type we were able to deploy to at the other site sucsessfully.
tconnersHi,
The error is caused by the driver iastors.sys .
If this driver is not required, you could remove the driver. Or have a test with another boot image.
(Please confirm all the drivers in the boot image are right and they should correspond with the architecture of your WINPE.)
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
I recently had rearranged our imaging by creating selection profiles for each computer model and then creating a task sequence for each model so that it looks for a model and only injects the drivers for that model. Everything had been working great
and then we got a new batch of Dell Latitude E6440's in. I checked over the machine and just wanted to make sure nothing changed so i grabbed a couple drivers off of it and uploaded them into mdt under that model. I went to update the deployment
share and started to get a whole host of Error: 2, no driver packages were found on the specified path. Verify the driver .INF file are in the specific location and try the command again. It points to the dism log and exit code is =2 then it says DISM
/Add-Driver failed, rc = 2 and lists all the drivers that had failed. It was a whole bunch for both the x86 and x64. Although i didnt add all these drivers. I only messed with the wifi and nic driver and it was only two files. I ran
through imaging and there were no issues it rebooted windows is about to start and it goes to the black screen with the iaStorA.sys message. I checked everything, i looked over all the chipset drivers i knew i imported and those were still there. I
downloaded the WINPE stuff from dell and found the driver and made sure to import everything in that folder and it skipped it as it said it was still there. I wanted to make sure it wasnt the whole mdt server so i imaged a different computer model all
together and that worked. So i deleted every driver out for this model made sure to delete it if it was in other places. I am now in the process of only including very specific drivers ie just the nic and display and audio and see if it will get
passed first bootup. But what would make it go from working every time for about 3 weeks now to all of a sudden not injecting drivers through updating the deployment share and causing a problem for just this image. I am including the dism log and
it is lengthy. The drivers are all sitting all sorted out in their respected folders on the desktop of the share. This has never been an issue before. here is the log
=== Making sure the deployment share has the latest x86 tools ===
=== Processing LiteTouchPE (x86) boot image ===
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.
WIM file mounted.
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
Image Version: 6.3.9600.16384
There was a problem opening the INF file. D:\Windows7\Out-of-box Drivers\hdc\iaAHCI_8.9.8.1005_157DE4AE7437DC1A46C7E0E4B3294E513CB47D80\iaAHCI.inf Error: 0x80070002.
Error: 2
No driver packages were found on the specified path.
Verify that the driver .INF files are in the specified location and try the command again.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = 2
DISM /Add-Driver failed, rc = 2.
Injected driver Intel hdc iaAHCI.inf 8.9.8.1005 (2)
Injected driver Intel hdc ibexahci.inf 7.0.0.1013 (14)
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
Image Version: 6.3.9600.16384
There was a problem opening the INF file. D:\Windows7\Out-of-box Drivers\hdc\ibexahci_7.0.0.1013_CDE6EABDFCC22A23476F9CB4EA115D63FF4A6DBE\ibexahci.inf Error: 0x80070002.
Error: 2
No driver packages were found on the specified path.
Verify that the driver .INF files are in the specified location and try the command again.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = 2
DISM /Add-Driver failed, rc = 2.
Injected driver Intel hdc ibexahci.inf 7.0.0.1013 (15)
Injected driver Intel hdc ibexid2.inf 9.1.1.1013 (6)
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
There were about 2,000 plus more lines of the same stuff.
For future purposes where should the driver be when import them into mdt and do i need to then keep them? I am still learning all this stuff after taking over the roll in October of 2014. Any help would be greatly appreciated.Hi KheenanHalvorson,
According to the log ,it seems that there is something missing in the driver package .
According to your description ,I assumed that you have configured the whole process correctly.
To deploy the drivers in this way the driver package should include two files an INF and SYS file .We may need to replace the driver package with another one including the INF file .
Here is a link for reference:
How to manage Out-of-Box Drivers with the use of Model Specific Driver Groups in Microsoft Deployment Toolkit 2012 Update 1
http://blogs.technet.com/b/askcore/archive/2013/05/09/how-to-manage-out-of-box-drivers-with-the-use-of-model-specific-driver-groups-in-microsoft-deployment-toolkit-2012-update-1.aspx
"One thing to note about Driver injections is that the driver must have an INF and SYS file in order for us to install the driver this way. If a driver installs via an EXE and there is no way to extract that driver to reveal the actual INF
and SYS file, then you would be forced to add that driver EXE package as an application and install it as an application. "
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
I'm getting an invalad signature when trying to update Itunes on win 7. Win 7 is up to date. How do I fix issue? Thanks
Try clearing your browser's cache and redownloading the iTunes setup file.
For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down page in case one of them applies.
Your library should be unaffected by these steps but there is backup and recovery advice elsewhere in the user tip.
tt2 -
IAstoreA.sys bluescreen / where to get drivers? [GT70 0nd]
Hey guys,
i just wanted to mount an .iso with WINcdemu and got an bluescreen right after the mounting (IAstoreA.sys) so i've read around and figured it out it has something to do with "RAID"?!
So i wanted to take a look on the MSI site but.. for my laptop the site isnt there anymore :O
Where to get the drivers for the RAID now?
System:
Win7 x64
MSI GT70 0ndQuote from: 4g63pilot on 17-February-14, 04:23:17
Thanks Zipper. Its odd that they don't have that when you look at the US site. The other odd thing is the driver version they have for download is the same that came loaded 311 from almost a year ago. On the NVidia site they have version 334 I think. Shouldn't they have a newer version on the MSI site ? Thanks for any help.
Most manufacturer's will, from time to time, post updated drivers. But it tends to be rare. Because that also means quite a bit on their end, such as testing, verification, etc...for every laptop model, and every new driver.
In the end, it's too costly and time consuming for them to release a new, authorized, official driver everytime one gets updated.
Use the ones from NVidia's site, they should work just fine.
As far as IAstoreA.sys, that driver is actually related to Intel's chipset/RAID driver and has nothing to do with the video card.
I would consider checking Intel's website for a new chipset/RAID driver for your notebook. -
MSI P55 GD65 - BSOD - MEMORY_MANAGEMENT
I'm facing a weird issue with my pc:
If I turn on the PC, the system starts up fine, but within 30 secs up to 5 minutes I get a BSOD (usually MEMORY_MANAGEMENT).
If I then restart the system it will run fine..
CPU intensive gaming, memory checks, benchmarks, standby and wakeup, all runs fine... after a first BSOD.
I've tried all kinds of memory settings, but nothing seems to help. Also hard to test if it runs fine after a crash.
It's almost like the system needs to warm-up a bit and then it will run fine
The BSOD message indicates a memory issue, but then I would expect random BSOD, not only right after cold start.
Any suggestions?
MSI P55 GD65 - latest 1.9 bios
i875k
Windows 7 64bit
Geil DDR3-1600 2x2GB Black Dragon GB34GB1600C8DC
This Geil ram is not in the MSI memory list but Geil shows the MSI P55 GD65 in their compatibility list for this memory:
"All motherboards listed on the GeIL Qualified Motherboard List – GQML have been tested with the specified GeIL memory kits for compatibility, stability and
performance by GeILs’ FAE to ensure best quality."
http://www.geil.com.tw/uploads/download_files/c8c397a9533d1896e708e3c106a99cb3.pdfStatus update:
I've reset the bios to safe defaults.
Started up memtest86+ and screen turned red rather then blue, so lots of mem-errors.
Restarted and then memtest ran fine for more then 10 hours.
Passed 20 times all tests no errors with both Dimms inserted.
Then I tested cold start with 1 dimm only:
- with 1 DIMM in slot 3 only system cold-starts fine and memtest runs fine with no errors.
- with 1 DIMM in slot 1 only system cold-starts fine and memtest starts up but then doesn't even start a test. So it seems to be hanging already.
Swapping both dimms showed the same result.
Preliminary conclusion now is a faulty slot 1
Does it indeed sound like a slot 1 issue?
MB is the worst part to RMA, so hopefully I can find a solution.... slot 1 seems not to be completely broken after all.
PS: increasing to 1.6V I had already tried before without success. -
Hello
I was starting up a game of League of Legends on my custom PC (AMD based) when I received the BSOD, error system service exception. So it turned off, like the error message says. The computer restarts, I can hear everything start running again... but nothing
happens on the screen. The monitor doesn't recognize any input. No sound, nothing on screen. Verified everything (hdmi, power, usb, etc) still plugged in. looked inside the case, everything looks how I left it. After restarting again, I noticed a few things:
1. Only the case is staying on (leds and fans).
2. The CPU fan turns on for about 2 seconds, then stops.
3. The cd drive still opens and closes.
I'm completely lost, this is quite stressful. Only a few weeks old, and it's my first build :( also, never had any issues whatsoever for the first 2 weeks.
Any help is welcome, thanks!Hi,
According to your description, I doubt your Graphic Card was the reason of this BSOD, If your computer couldn't be start any more, please contact the manufacture of your computer to check hardware problem.
Roger Lu
TechNet Community Support -
Lenovo G550 core 2 duo+win 7 frequent bsod
Hi,
I recently bought a lenovo g550 laptop with a core 2 duo configuration with pre installed win 7 home premium. It has been over month since I purchased and have been having a frequent problem of blue screen of death with an error as follows..
Problem signature:
Problem Event Name: BlueScreen
Additional information about the problem:
BCCode: 19
BCP1: 00000003
BCP2: 82F7DB40
BCP3: 87C8899C
BCP4: 82F7DB40
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
I would be glad if anyone could help me regarding this. The customer care has been useless.probably it supports.
you can check it under directx ( press window + r, type "dxdiag" and enter ) -
BSOD may occurs when hibernating by Intel WiFi driver on Windows 7 x64
I use Thikpad X201s (5129CTO). BSOD has occured today.
The content of the event log is shown in the following.
- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 2
Level 1
Task 63
Opcode 0
Keywords 0x8000000000000002
- EventData
BugcheckCode 159
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa80024b2a20
BugcheckParameter3 0xfffff80004dde518
BugcheckParameter4 0xfffffa80095f8990
SleepInProgress true
PowerButtonTimestamp 0
The content of memory dump is shown in the following.
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03652000 PsLoadedModuleList = 0xfffff800`0388fe50
Debug session time: Sat Jul 17 19:29:21.218 2010 (GMT+9)
System Uptime: 0 days 8:01:36.810
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80024b2a20, fffff80004dde518, fffffa80095f8990}
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys
Followup: MachineOwner
0: kd> !analyze -v
* Bugcheck Analysis *
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80024b2a20, Physical Device Object of the stack
Arg3: fffff80004dde518, Functional Device Object of the stack
Arg4: fffffa80095f8990, The blocked IRP
Debugging Details:
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa80095f8990
DEVICE_OBJECT: fffffa8004a92050
DRIVER_OBJECT: fffffa8004a91060
IMAGE_NAME: NETw5s64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ba1b871
MODULE_NAME: NETw5s64
FAULTING_MODULE: fffff88006293000 NETw5s64
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800037311b3 to fffff800036c2600
STACK_TEXT:
fffff800`04dde4c8 fffff800`037311b3 : 00000000`0000009f 00000000`00000003 fffffa80`024b2a20 fffff800`04dde518 : nt!KeBugCheckEx
fffff800`04dde4d0 fffff800`036ce6a6 : fffff800`04dde600 fffff800`04dde600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`04dde570 fffff800`036cda26 : fffffa80`018b3168 fffffa80`018b3168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`04dde5e0 fffff800`036ce57e : 00000043`47d76c0b fffff800`04ddec58 00000000`001c43bb fffff800`038409e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04ddec30 fffff800`036cdd97 : 0000000d`fb5d6bc7 0000000d`001c43bb 0000000d`fb5d6bc3 00000000`000000bb : nt!KiTimerExpiration+0x1be
fffff800`04ddecd0 fffff800`036cadfa : fffff800`0383ce80 fffff800`0384ac40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04dded80 00000000`00000000 : fffff800`04ddf000 fffff800`04dd9000 fffff800`04dded40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_NETw5s64.sys
BUCKET_ID: X64_0x9F_IMAGE_NETw5s64.sys
Followup: MachineOwner
Probably, it seems to causing by Intel Wireless WiFi Link Adapter 's driver 'NETw5s64.sys'. The version of 'NETw5s64.sys' is 13.2.0.30. The michine installed Intel Centrino Advanced-N + WiMAX 6250. All hardware are functional.
I hibernate the machine manually, then same problem not occured.
Does a similar problem occur?
Where should I feed back?Similar thread, also with Event-ID 41, though file of concern seems to be pci.sys:
http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/X201-Random-Shutdown-Screen-goes-off/td-p/2471...
How exactly did it occur? Did your x201 automatically go into hibernation after the defined time?
Because at my place this BSOD occurs suddenly, last time it happened about 1 minute after i was using the notebook. Trying to find analogies there ...
Win 7 32Bit though.
I disabled Multi-Core in BIOS so i don't have regular lags.
I always keep energy saving settings to "Maximum Performance" so i don't have regular contrast issues.
I deinstalled ThinkAdvantage Access Connections so i don't have random WLAN Adapter "power offs". -
Windows Server 2008 R2 SP1 - BSOD Stop Error 0x00000050 RDPWD.SYS
Hi all,
I have been struggling with a BSOD for the past 5 weeks and have scoured the web trying in vain to find someone else with the same issue.
Environment:
8 x 2008 R2 SP1 Windows Servers (8Gb RAM, 25Gb HDD) with Remote Desktop Services Roles installed, running as part of an RDS Farm. All Servers are VM Guests (hardware version 7) running on VMware vSphere v4.1.0-260247 Hosts (Dell
PowerEdge R710 - 128Gb RAM). Our vSphere 'farm' has 5 Hosts that connect to our EMC SAN via iSCSI with multipath routes.
Each RDS Server is load balanced via a Connection Broker, and each server has the same set of software / vm hardware installed. In a nutshell, each has Symantec Endpoint Protection v11.0.5002.333, Symantec Altiris v7.0, Microsoft Office 2007 as well as
other various software essential to these servers.
Symptoms:
Randomly throughout the day, one (or more) of the RDS Servers will crash with a BSOD more often than not with "caused by driver ntoskrnl.exe" sometimes with "cng.sys" and once with "ksecpkg.sys". So far in the 5 weeks I have had 90 crashes. Yesterday
all 8 of the RDS Servers crashed at some point throughout the day.
On a typical BSOD, it says:
The problem seems to be caused by the following file: ntoskrnl.exe
PAGE_FAULT_IN_NONPAGED_AREA
Technical Information:
*** STOP: 0x00000050 (0xfffffa800c153284, 0x0000000000000001, 0xfffff880053dc0c9, 0x0000000000000000)
*** ntoskrnl.exe - Address 0xfffff8000169ac40 base at 0xfffff8000161e000 DateStamp 0x4e02aaa3
Using BlueScreenView it says "caused by address: ntoskrnl.exe+7cc40" nearly every time.
I have analysed as best I could using Microsoft WinDbg, and this is the output of a typical mini-dump file:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [\\hqrds01\c$\Windows\Minidump\030112-19359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Program Files\Debugging Tools for Windows (x64)\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: Server, suite: TerminalServer
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01609000 PsLoadedModuleList = 0xfffff800`0184e670
Debug session time: Thu Mar 1 09:14:00.921 2012 (UTC + 0:00)
System Uptime: 0 days 21:31:41.950
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa800be83284, 1, fffff8800576f0c9, 0}
Could not read faulting driver name
Probably caused by : RDPWD.SYS ( RDPWD!memcpy+1d9 )
Followup: MachineOwner
1: kd> !analyze -v
* Bugcheck Analysis
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa800be83284, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800576f0c9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800018b8100
fffffa800be83284
FAULTING_IP:
RDPWD!memcpy+1d9
fffff880`0576f0c9 668901 mov word ptr [rcx],ax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800bf70a80 -- (.trap 0xfffff8800bf70a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000023d rbx=0000000000000000 rcx=fffffa800be83284
rdx=ffffffffffe7e63b rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800576f0c9 rsp=fffff8800bf70c18 rbp=0000000000000001
r8=000000000000001c r9=fffff8a0033401e8 r10=fffff8a0033401e8
r11=fffffa800be83268 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
RDPWD!memcpy+0x1d9:
fffff880`0576f0c9 668901 mov word ptr [rcx],ax ds:0c40:fffffa80`0be83284=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800016319fc to fffff80001685c40
STACK_TEXT:
fffff880`0bf70918 fffff800`016319fc : 00000000`00000050 fffffa80`0be83284 00000000`00000001 fffff880`0bf70a80 : nt!KeBugCheckEx
fffff880`0bf70920 fffff800`01683d6e : 00000000`00000001 fffffa80`0be83284 00000000`00000000 fffff8a0`0be85820 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`0bf70a80 fffff880`0576f0c9 : fffff880`057547cf 00000000`00000000 00000000`00000022 00000000`00000002 : nt!KiPageFault+0x16e
fffff880`0bf70c18 fffff880`057547cf : 00000000`00000000 00000000`00000022 00000000`00000002 fffff880`0576c99d : RDPWD!memcpy+0x1d9
fffff880`0bf70c20 fffff880`0576c9fc : fffff8a0`0f938010 00000000`00000022 00000000`00000019 00000000`00000002 : RDPWD!SM_MCSSendDataCallback+0x303
fffff880`0bf70c60 fffff880`0576b354 : fffff880`0bf70da0 fffff8a0`033401e8 00000000`00000000 fffff880`0576abfd : RDPWD!HandleAllSendDataPDUs+0x188
fffff880`0bf70d10 fffff880`0576af64 : 00000000`00000031 fffffa80`0bd01895 00000006`0000001f fffff880`05739079 : RDPWD!RecognizeMCSFrame+0x28
fffff880`0bf70d50 fffff880`029ba1f8 : fffff8a0`03345000 fffffa80`0bae6e80 fffffa80`0a5c0e60 fffff880`05737e00 : RDPWD!MCSIcaRawInputWorker+0x3d4
fffff880`0bf70df0 fffff880`057378d0 : 00000000`00000000 fffff880`0bf70f10 fffff880`0bf70f08 00000000`00000000 : termdd!IcaRawInput+0x50
fffff880`0bf70e20 fffff880`05736d85 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tssecsrv!CRawInputDM::PassDataToServer+0x2c
fffff880`0bf70e50 fffff880`057367c2 : fffffa80`088e8a28 fffffa80`00000000 00000000`00000031 fffff800`00000000 : tssecsrv!CFilter::FilterIncomingData+0xc9
fffff880`0bf70ef0 fffff880`029ba1f8 : fffff880`009b8180 00000000`00000001 00000000`00000000 00000000`00000000 : tssecsrv!ScrRawInput+0x82
fffff880`0bf70f60 fffff880`0572c4c5 : fffffa80`088e8a10 fffffa80`0bd01658 00000000`00000000 fffffa80`088e8a10 : termdd!IcaRawInput+0x50
fffff880`0bf70f90 fffff880`029baf3e : fffffa80`0bd01620 fffffa80`0c100420 fffffa80`0bd4b450 fffffa80`0973b9b0 : tdtcp!TdInputThread+0x465
fffff880`0bf71810 fffff880`029b9ae3 : fffffa80`09d902b0 fffffa80`0973b9b0 fffffa80`093d8520 fffffa80`0bd4b450 : termdd!IcaDriverThread+0x5a
fffff880`0bf71840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : termdd!IcaDeviceControlStack+0x827
STACK_COMMAND: kb
FOLLOWUP_IP:
RDPWD!memcpy+1d9
fffff880`0576f0c9 668901 mov word ptr [rcx],ax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: RDPWD!memcpy+1d9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RDPWD
IMAGE_NAME: RDPWD.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7ab45
FAILURE_BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
Followup: MachineOwner
The RDS servers are set to reboot automatically, and after a period of 5 minutes or so, the users can reconnect and log back in. On a typical day each server will have around 10 people RDP'd in to them.
The Users connecting to the RDS Servers included XP laptops/desktops and IGEL UD-120-LX Thin Terminals. The XPs have SP3 installed and are fully patched via Symantec Altiris.
Things I have tried:
- Analyse the dump-files (as per above).
- I have tracked each user logging on to the RDS Farm (via batch scripts) and tried to determine if this is caused by the same individual(s) but it appears random.
- Check to see if the crashing Virtual Machine is running on a specific host, but it has happened on all Hosts.
- Check to see if there was anything specific that happened on the day that the crashes started. There were about 5 new poeple introduced to the RDS Farm at that time, but there were using (a) client machines that had been used previously elsewhere with
no issues, (b) software that had been used previously, (c) in a remote location that had previous users using RDS, (d) have not been logged on to a RDS Server when it has crashed.
- Updated Windows Server 2008 R2 SP1 to the latest patches (as of Feb 2012).
- Turned on Verifier (using recommended settings), and then analysed dump-files with the same reference to rdpwd.sys.
- Fixed the Memory Resource Reservation in vSphere to the full 8Gb for all these RDS Servers (so that the memory is not shared at all).
- Ran MEMTEST on a VM Guest with the full 8Gb RAM, on a couple of the ESX Hosts.
- Changed the VMTools Video Driver to the SVGA II driver from the Standard VGA Driver.
- Ran a full AV Scan (using SEP).
- Isolated the Printer Drivers using the Printer Management MMC.
- Ran sfc /scannow of all RDS Servers and rebooted.
The mini-dump file mentioned above is here:https://skydrive.live.com/redir.aspx?cid=48f471f287af2349&resid=48F471F287AF2349!105&parid=48F471F287AF2349!103
I hope someone can help, as what hair I have left (from pulling it out) is turning grey!
Andy* Bugcheck Analysis
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa800c153284, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff880053dc0c9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800018cd100
fffffa800c153284
FAULTING_IP:
RDPWD!memcpy+1d9
fffff880`053dc0c9 668901 mov word ptr [rcx],ax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800aa48a80 -- (.trap 0xfffff8800aa48a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000001ff rbx=0000000000000000 rcx=fffffa800c153284
rdx=ffffffffffee6b8b rsi=0000000000000000 rdi=0000000000000000
rip=fffff880053dc0c9 rsp=fffff8800aa48c18 rbp=0000000000000001
r8=000000000000001c r9=fffff8a0123923a8 r10=fffff8a0123923a8
r11=fffffa800c153268 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
RDPWD!memcpy+0x1d9:
fffff880`053dc0c9 668901 mov word ptr [rcx],ax ds:8c40:fffffa80`0c153284=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800016469fc to fffff8000169ac40
STACK_TEXT:
fffff880`0aa48918 fffff800`016469fc : 00000000`00000050 fffffa80`0c153284 00000000`00000001 fffff880`0aa48a80 : nt!KeBugCheckEx
fffff880`0aa48920 fffff800`01698d6e : 00000000`00000001 fffffa80`0c153284 00000000`00000000 fffff8a0`10919830 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`0aa48a80 fffff880`053dc0c9 : fffff880`053c17cf 00000000`00000000 00000000`00000022 00000000`00000002 : nt!KiPageFault+0x16e
fffff880`0aa48c18 fffff880`053c17cf : 00000000`00000000 00000000`00000022 00000000`00000002 fffff880`053d999d : RDPWD!memcpy+0x1d9
fffff880`0aa48c20 fffff880`053d99fc : fffff8a0`10cf30d0 00000000`00000022 00000000`00000019 00000000`00000002 : RDPWD!SM_MCSSendDataCallback+0x303
fffff880`0aa48c60 fffff880`053d8354 : fffff880`0aa48da0 fffff8a0`123923a8 00000000`00000000 fffff880`053d7bfd : RDPWD!HandleAllSendDataPDUs+0x188
fffff880`0aa48d10 fffff880`053d7f64 : 00000000`00000031 fffffa80`0c039de5 00000006`0000001f fffff880`053a6079 : RDPWD!RecognizeMCSFrame+0x28
fffff880`0aa48d50 fffff880`012c01f8 : fffff8a0`12393000 fffffa80`0bb7aa60 fffffa80`0b81e9c0 fffff880`053a4e00 : RDPWD!MCSIcaRawInputWorker+0x3d4
fffff880`0aa48df0 fffff880`053a48d0 : 00000000`00000000 fffff880`0aa48f10 fffff880`0aa48f08 fffffa80`0c039ba8 : termdd!IcaRawInput+0x50
fffff880`0aa48e20 fffff880`053a3d85 : fffff880`01716890 fffffa80`0c0327e8 00000000`00000000 00000000`00000000 : tssecsrv!CRawInputDM::PassDataToServer+0x2c
fffff880`0aa48e50 fffff880`053a37c2 : fffffa80`0c16e598 fffffa80`00000000 00000000`00000031 fffff800`00000000 : tssecsrv!CFilter::FilterIncomingData+0xc9
fffff880`0aa48ef0 fffff880`012c01f8 : fffff880`009b8180 00000000`00000001 00000000`00000000 00000000`00000000 : tssecsrv!ScrRawInput+0x82
fffff880`0aa48f60 fffff880`052994c5 : fffffa80`0c16e580 fffffa80`0c039ba8 00000000`00000000 fffffa80`0c16e580 : termdd!IcaRawInput+0x50
fffff880`0aa48f90 fffff880`012c0f3e : fffffa80`0c039b70 fffffa80`0acccf20 fffffa80`0a95c450 fffffa80`0abf9620 : tdtcp!TdInputThread+0x465
fffff880`0aa49810 fffff880`012bfae3 : fffffa80`0c0a6560 fffffa80`0abf9620 fffffa80`087eee80 fffffa80`0a95c450 : termdd!IcaDriverThread+0x5a
fffff880`0aa49840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : termdd!IcaDeviceControlStack+0x827
STACK_COMMAND: kb
FOLLOWUP_IP:
RDPWD!memcpy+1d9
fffff880`053dc0c9 668901 mov word ptr [rcx],ax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: RDPWD!memcpy+1d9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RDPWD
IMAGE_NAME: RDPWD.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7ab45
FAILURE_BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
Followup: MachineOwner
Bug Check Code 0x50:http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023%28v=vs.85%29.aspx
Please start by that:
Update all possible drivers
Uninstall all unused programs
Disable all security softwares you have
Run chkdsk /r /f and sfc /scannow
Run memtest86+ to check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support
If this does not help then upload MEMORY.DMP file (You can zip it and divide it using 7-ZIP) using Microsoft Skydrive and post a link here.
You can also contact Microsoft CSS for assistance.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft
Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer -
Tips for blue screen (BSOD) errors with Windows Vista and Intel Turbo Memory on T61/T61p
Important note: The symptoms and solutions described below address only a small subset of the possible causes for blue screen errors, aka BSOD. This information can help address blue screen errors specifically related to Turbo Memory, but may not solve errors related to other issues. Please read through the instructions completely, make sure they apply to your system, and after attempting the solutions please post back with your feedback for the community.
Some users may experience random blue screen errors with ThinkPad
systems running Windows Vista with Intel Turbo Memory hardware. These
blue screens may occur during normal usage on the system or they may
occur when booting into Windows Vista. Blue screens related to the
Intel Turbo Memory hardware may reference a stop code of 8086 with
memory address locations of {0, 0, 0, 0}.
There are two main steps that you can take to help resolve blue screen issues related to Intel Turbo Memory.
Step 1: Update Intel Turbo Memory Driver
If the driver version is before version 1.0.1.1004-7.0.3.1001, please
update to this version.
To determine what version of the Intel Turbo Memory driver is installed:
1. Click Start, then click Control Panel.
2. Click System and Maintenance.
3. Click System.
4. Click Device Manager.
5. Expand the Storage controllers category.
6. Double-click Intel Flash Cache Logic Chip.
7. Click the Driver tab. Then you will see the driver version (for example, 1.0.1.1004).
The new driver and installation instructions can be found here.
Note: The Intel Matrix Storage Driver is updated with this package.
Step 2: BIOS version
If your BIOS version is older than those listed below, please update to the version listed.
How to check your BIOS version:
Turn off the system.
Turn on the system.
While the To interrupt normal startup, press the blue ThinkVantage button message is displayed at the lower-left area of the screen, press the F1 key.
The
BIOS Setup Utility menu will be displayed. If you have set a supervisor
password, the BIOS Setup Utility menu appears after you enter the
password.
Check BIOS Version and Embedded Controller Version.
Turn off the system.
System BIOS versions:
ThinkPad T61/T61p (14.1 inch widescreen with IEEE 1394 model) - BIOS version 1.22 (7LET52WW)
Please
remember that these updates do not solve every possible system blue
screen, but they do resolve several problems related to the Intel Turbo
Memory driver.
Message Edited by Tim_Lenovo on 11-30-2007 07:03 PM
Tim Supples
Lenovo Social Media
Got a question? Don't PM me, post it on the forum!
Lenovo Blogs
X60 Tablet SXGA+ primary, Z61p fully loaded workhorseThanks Tim,
I do have my T61p fully up-to-date to the latest drivers and updates (via System Update and the Drivers&Software web page when the former is not that up-to-date).
At the moment the most recurrent problem is this:
http://forum.lenovo.com/lnv/board/message?board.id=T_Series_Thinkpads&thread.id=55
which has been longly speculated here:
http://forum.thinkpads.com/viewtopic.php?t=47755
My other angst is the boot-time chkdsk hang-up problem:
http://forum.thinkpads.com/viewtopic.php?t=52765&highlight=chkdsk
I just wonder if this purely a Vista issue when using NV cache, the disk spinning down at almost exactly 1 hour from the beginning of the chdsk operation seems too much of a coincidence.
This is my T61p configuration:
Intel Core 2 Duo T7700 2.4GHz
BIOS version 1.26-1.06
4GB RAM 2 SO-DIMMs
nVidia Quadro FX 570m with 512MB VRAM
WUXGA LCD
Seagate 7200.2 160 GB
4GB RAM 2 SO-DIMMs
Windows Vista Ultimate 32bit (waiting to move to 64bit)
thanks,
andrea
Message Edited by abarbieri on 12-05-2007 03:48 PM
T61p - 15.4" - T7700 - FX 570M 256MB - 4GB RAM - ST916023AS - 4965AGN - BT - FPR - 9 cell - Vista Ult. x86
T21p - 14" - PIII 850MHz - S3 Savage/IX 8MB - 512MB RAM - 100GB 7200rpm - WinXP x86 -
Tips for blue screen (BSOD) errors with Windows Vista and Intel Turbo Memory on X61/X61s
Important note: The symptoms and solutions described below address only a small subset of the possible causes for blue screen errors, aka BSOD.
This information can help address blue screen errors specifically
related to Turbo Memory, but may not solve errors related to other
issues. Please read through the instructions completely, make sure they
apply to your system, and after attempting the solutions please post
back with your feedback for the community.
Some users may experience random blue screen errors with ThinkPad
systems running Windows Vista with Intel Turbo Memory hardware. These
blue screens may occur during normal usage on the system or they may
occur when booting into Windows Vista. Blue screens related to the
Intel Turbo Memory hardware may reference a stop code of 8086 with
memory address locations of {0, 0, 0, 0}.
There are two main steps that you can take to help resolve blue screen issues related to Intel Turbo Memory.
Step 1: Update Intel Turbo Memory Driver
If the driver version is before version 1.0.1.1004-7.0.3.1001, please
update to this version.
To determine what version of the Intel Turbo Memory driver is installed:
1. Click Start, then click Control Panel.
2. Click System and Maintenance.
3. Click System.
4. Click Device Manager.
5. Expand the Storage controllers category.
6. Double-click Intel Flash Cache Logic Chip.
7. Click the Driver tab. Then you will see the driver version (for example, 1.0.1.1004).
The new driver and installation instructions can be found here.
Note: The Intel Matrix Storage Driver is updated with this package.
Step 2: BIOS version
If your BIOS version is older than those listed below, please update to the version listed.
How to check your BIOS version:
Turn off the system.
Turn on the system.
While the To interrupt normal startup, press the blue ThinkVantage button message is displayed at the lower-left area of the screen, press the F1 key.
The
BIOS Setup Utility menu will be displayed. If you have set a supervisor
password, the BIOS Setup Utility menu appears after you enter the
password.
Check BIOS Version and Embedded Controller Version.
Turn off the system.
System BIOS versions:
ThinkPad X61 or X61s - BIOS version 1.06 (7NET25WW)
Please
remember that these updates do not solve every possible system blue
screen, but they do resolve several problems related to the Intel Turbo
Memory driver.
Tim Supples
Lenovo Social Media
Got a question? Don't PM me, post it on the forum!
Lenovo Blogs
X60 Tablet SXGA+ primary, Z61p fully loaded workhorseDear Tim,
First off, many thanks for the tips for resolving BSOD with Vista + Turbo Memory on X61. I've been suffering from this BSOD for countless times since I bought in my X61 7673-CW9 in April 2008.
Even prior to having the pleasure to visit this wonderful forum, I followed both steps as indicated, and updated my Intel Turbo Memory driver to 1.5.0.1013 and my BIOS to 7NETB4WW (2.14). However, the BSOD recurrs.
For the past two months, I've recovered my system to factory default settings using Rescue and Recovery for over twenty times, each time with the latest Intel Turbo Memory driver and BIOS. Notwithstanding that, BSOD recurrs.
During these painful experiences, I tried two options: 1) making my X61 up-to-date by using System Update and Windows Update (including Vista SP1 or excluding Vista SP1); 2) keeping my X61 the status as factory default (i.e. without updating through either System Update or Windows Update (the automatic/scheduled update function of both is turned off)). In either case, BSOD recurrs.
I'm 100% positive that the BSOD does not arise from any hardware or software/firmware I install. I never install any hardware (e.g. RAM). And, it is not caused by any software/firmware I install: the clear and unequivocal evidence is that at one time,I encountered BSOD while having restored back to factory setting and booting for the first time.
I live in Taiwan, and I seldom heard this BSOD here. All of my friends (as most of Taiwan residents) using X61 operate in Traditional Chinese environment, whereas I operate in English environment. In Taiwan, when booting for the first time after purchase/recovery, the Windows Vista Business system provides for lanuage choice (Traditional Chinese or English), and, once chosen, the language cannot be altered later on (unless, of course, the system is restored back to factory default settings).
My system specs are the same as the day I purchased it and are listed below (as I'm not sure if my machine type X61 7673-CW9 is applicable outside Taiwan):
Processor: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.4GHz
Memory: 1.00 G.B.
System: Windows Vista Business (32-bit)
Hard Drive: 160 G.B. @ 7,200 r.p.m.
And, of course, with Intel Turbo Memory 1 G.B.
I contacted the Lenovo support staff here in Taiwan for countless times, but they seem to be clueless. I learned that some friends at this forum downgraded their OS back to Windows XP, but I chose not to. The reason is simple: my purchase price for X61 7673-CW9 includes the Intel Turbo Memory, which cannot function under Windows XP (at least so far).
Therefore, I just wish to share my experience here and perhaps I can get some advice from you and other friends here. Any advice will be tremendously and enormously appreciated.
Kevin Chen @ Taiwan -
links plz for downloading windows 7 drivers ,no sound in win 7,using os lion
Hi, I don't know the answer to your problem, was hoping somebody would pipe in, but I guess not.
Maybe run Linux within OSX?
VirtualBox...
http://www.virtualbox.org/wiki/Downloads
Might even try asking over on my site...
http://x704.net/bbs -
T400 Windows XP Random Freezes / Lockups (no BSOD) - Intel Wireless issue?
Hi,
I installed Windows XP Pro SP3 on my new Thinkpad T400 purchased a few days ago. I installed all the latest drivers and thinkvantage software from the drivers matrix.
For two days now the system randomly freezes. The screen freezes, i cannot move the mouse or keyboard. Some FN buttons like the Thinklight still work, the rest does not and it ultimately requires a force power off by holding the power button pressed.
Interestingly enough the Wireless symbol still blinks even when the laptop is frozen. When i turn off the wireless switch, the bluetooth icon will turn off, yet the wireless KEEPS blinking (normally both turn off when the wireless switch is turned off).
I originally had the lenovo intel wireless 5100 drivers, now tried the intel.com drivers, no avail, same issue. The system also freezes when just sitting idle. I have not yet tried if the freezes occur with wireless turned off, will try later...
Kind of annoying as i had various BSODs due to the lenovo intel Matrix Storage driver (the original intel one made it go away), now this problem...is XP just not really supported by this machine?
Thinkpad T400 (Windows 7 Ultimate x64)Hi,
I installed Windows XP Pro SP3 on my new Thinkpad T400 purchased a few days ago. I installed all the latest drivers and thinkvantage software from the drivers matrix.
For two days now the system randomly freezes. The screen freezes, i cannot move the mouse or keyboard. Some FN buttons like the Thinklight still work, the rest does not and it ultimately requires a force power off by holding the power button pressed.
Interestingly enough the Wireless symbol still blinks even when the laptop is frozen. When i turn off the wireless switch, the bluetooth icon will turn off, yet the wireless KEEPS blinking (normally both turn off when the wireless switch is turned off).
I originally had the lenovo intel wireless 5100 drivers, now tried the intel.com drivers, no avail, same issue. The system also freezes when just sitting idle. I have not yet tried if the freezes occur with wireless turned off, will try later...
Kind of annoying as i had various BSODs due to the lenovo intel Matrix Storage driver (the original intel one made it go away), now this problem...is XP just not really supported by this machine?
Thinkpad T400 (Windows 7 Ultimate x64) -
Bsod after load attempt cycdisk.sys, no error name, massive help?
okay, I have two toshibas now, lol. thanks to my first with vista getting bsod. this bsod explains np error code, and comes after loading cycdisk.sys everytime... I have tried safe mode, system repair, everything... it will not let me on for two secnds to do anything. my husband purchased this laptop less than a year ago and I don't want to toss it because of bsod, that would suck.
long story short, I just blew more cash on another laptop to get online to try and repair this older one.
I am running Vista on the old one, and still under warranty. and ideas? I don't think I have enough time in the warranty to send it anywhere for repairs... but it's less than a year old and such a waste to consider a loss. any suggestions would be helpful.
I've done all the research I can on BSOD, but none of the suggestions online help. what should I do?
pardon the missing punctuation, it's four in the morning and I am tired.
model number: PSLB8U-027025.
all help is appreciated.Why wouldn't you have enough time to send it in? If it's still under warranty the repair is covered as long as you contact Toshiba and obtain the RMA PRIOR to it expiring. The repair doesn't have to be finished before it expires as long as the RMA Warranty Repair Process has been started.
If you don't post your COMPLETE model number it's very difficult to assist you. Please try to post in complete sentences with punctuation, capitals, and correct spelling. Toshiba does NOT provide any direct support in these forums. All support is User to User in their spare time.
Maybe you are looking for
-
Hi, I am new to Illustrator (CS5) and not fully comfortable with RGB vs CMYK. For instance, I created a logo for use on the web using Document Color Mode: RGB where my background color in RGB is 0, 0, 130. When I create a Print document using Docum
-
Office Web Apps deploy certificate error
IIS Using Domain Certificate, when access "https://fqdn/hosting/discovery" with certificate error. Office web apps using same CA with Front End Server. new web farm with this new certificate name. Any suggest? Thanks.
-
Why do I get a windows error every time I stop or close an executable?
Whenever I run an executable in any windows computer it runs fine but as soon as I stop or shut down the executable, I get and a windows error. The program that I have reads from compact Fieldpoints and processes those data. Once you close or stop th
-
Message length in a message class
hi all, I have a error message to be displayed in report , its length exceeds 74 character. What is the way to increase the default length? or is there another way to display the error where length is greater
-
I purchased a new computer and tried to download my lightroom 4 program onto it. It is still installed on my other lap top. Can some give me some direction on how I can download my software onto my new lap top? Thanks in advance.