BSOD POWER_STATE_FAILURE in Windows 7 64 bit

Hi all
I have a Sattelite P300, born with Vista-32 bit, which actually worked without any serious problems.
I upgraded the thing to Windows 7 Ultimate 64-bit, and now I get a particular problem several times a day.
I get the infamous Blue Screen Of Death with the text "POWER_STATE_FAILURE" and a minidump is generated before windows dies and restart.
Before you ask, the answer is Yes - I have upgraded all firmware, bios and available drivers - none of which have helped.
There is another symptom, which is that the power meter (right left corner) doesn't always seem to work. When it doesn't work, it is often after the PC have been disconnected from the power grid and then reconnected, but I can't tell for sure. When I say doesn't seem to work, I mean that cllicking on the battery icon do not work.
I've checked google numerous times and it certainly seems like other people are having the same problem with Toshiba laptops (various models). Unfortunately there is absolutely NO solutions anywhere. All threads seems to state the problem - someone suggests to upgrade all drivers and BIOS - this doesn't help and then the threads stop.
I hope this is not the case here. - By now I am convinced that this indeed IS a BIOS or driver problem, but apparently there is no fix available for my PC (model P300-13B, PSPC4E).
Could anyone please help me?
Best Regards
Henrik

No yellow exclamation / problems in device manager.
The only thing to be seen is the dump. I've ran several windows upgrades/repairs as well.
This is the minidump_
Opened log file 'c:\debuglog.txt'
0: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
0: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* 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: fffffa80051f8050, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8002a2b010, The blocked IRP
Debugging Details:
*** WARNING: Unable to verify timestamp for o2sdx64.sys
*** ERROR: Module load completed but symbols could not be loaded for o2sdx64.sys
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: o2sdx64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47c7d9dd
MODULE_NAME: o2sdx64
FAULTING_MODULE: fffff880043ed000 o2sdx64
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`00b9c4c8 fffff800`030e71b3 : 00000000`0000009f 00000000`00000003 fffffa80`051f8050 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`030846a6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c570 fffff800`03083a26 : fffff800`03228700 00000000`00042586 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`0308457e : 00000009`ded63ef4 fffff800`00b9cc58 00000000`00042586 fffff800`031f6348 : nt!KiProces***piredTimerList+0xc6
fffff800`00b9cc30 fffff800`03083d97 : 00000001`c3b0f2c1 00000001`00042586 00000001`c3b0f24d 00000000`00000086 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03080dfa : fffff800`031f2e80 fffff800`03200c40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_disk_IMAGE_o2sdx64.sys
BUCKET_ID: X64_0x9F_3_disk_IMAGE_o2sdx64.sys
Followup: MachineOwner
rax=fffff8000321d5f8 rbx=fffffa8002a2b010 rcx=000000000000009f
rdx=0000000000000003 rsi=fffffa8003b8b310 rdi=0000000000000000
rip=fffff80003078600 rsp=fffff80000b9c4c8 rbp=0000000000000001
r8=fffffa80051f8050 r9=fffff80000b9c518 r10=0000000000000000
r11=0000000000008000 r12=fffffa8002a2b010 r13=0000000000000000
r14=0000000000000001 r15=fffff800032282d0
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000246
nt!KeBugCheckEx:
fffff800`03078600 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`00b9c4d0=000000000000009f
Child-SP RetAddr : Args to Child : Call Site
fffff800`00b9c4c8 fffff800`030e71b3 : 00000000`0000009f 00000000`00000003 fffffa80`051f8050 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`030846a6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c570 fffff800`03083a26 : fffff800`03228700 00000000`00042586 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`0308457e : 00000009`ded63ef4 fffff800`00b9cc58 00000000`00042586 fffff800`031f6348 : nt!KiProces***piredTimerList+0xc6
fffff800`00b9cc30 fffff800`03083d97 : 00000001`c3b0f2c1 00000001`00042586 00000001`c3b0f24d 00000000`00000086 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03080dfa : fffff800`031f2e80 fffff800`03200c40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
start end module name
fffff800`00bad000 fffff800`00bb7000 kdcom kdcom.dll Tue Jul 14 03:31:07 2009 (4A5BDFDB)
fffff800`03008000 fffff800`035e4000 nt ntkrnlmp.exe Sat Feb 27 08:55:23 2010 (4B88CFEB)
fffff800`035e4000 fffff800`0362d000 hal hal.dll Tue Jul 14 03:27:36 2009 (4A5BDF08)
fffff880`00c00000 fffff880`00c5c000 volmgrx volmgrx.sys Tue Jul 14 01:20:33 2009 (4A5BC141)
fffff880`00c5c000 fffff880`00c6c000 PCIIDEX PCIIDEX.SYS Tue Jul 14 01:19:48 2009 (4A5BC114)
fffff880`00c6c000 fffff880`00c86000 mountmgr mountmgr.sys Tue Jul 14 01:19:54 2009 (4A5BC11A)
fffff880`00c86000 fffff880`00c8f000 atapi atapi.sys Tue Jul 14 01:19:47 2009 (4A5BC113)
fffff880`00c8f000 fffff880`00cb9000 ataport ataport.SYS Tue Jul 14 01:19:52 2009 (4A5BC118)
fffff880`00cbf000 fffff880`00d03000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 03:29:10 2009 (4A5BDF66)
fffff880`00d03000 fffff880`00d17000 PSHED PSHED.dll Tue Jul 14 03:32:23 2009 (4A5BE027)
fffff880`00d17000 fffff880`00d75000 CLFS CLFS.SYS Tue Jul 14 01:19:57 2009 (4A5BC11D)
fffff880`00d75000 fffff880`00da8000 pci pci.sys Tue Jul 14 01:19:51 2009 (4A5BC117)
fffff880`00da8000 fffff880`00dbd000 partmgr partmgr.sys Tue Jul 14 01:19:58 2009 (4A5BC11E)
fffff880`00dbd000 fffff880`00dc9000 BATTC BATTC.SYS Tue Jul 14 01:31:01 2009 (4A5BC3B5)
fffff880`00dc9000 fffff880`00dde000 volmgr volmgr.sys Tue Jul 14 01:19:57 2009 (4A5BC11D)
fffff880`00dde000 fffff880`00de9000 msahci msahci.sys Tue Jul 14 02:01:01 2009 (4A5BCABD)
fffff880`00de9000 fffff880`00df4000 amdxata amdxata.sys Tue May 19 19:56:59 2009 (4A12F2EB)
fffff880`00e00000 fffff880`00e0d000 vdrvroot vdrvroot.sys Tue Jul 14 02:01:31 2009 (4A5BCADB)
fffff880`00e0d000 fffff880`00e16000 compbatt compbatt.sys Tue Jul 14 01:31:02 2009 (4A5BC3B6)
fffff880`00e1b000 fffff880`00edb000 CI CI.dll Tue Jul 14 03:32:13 2009 (4A5BE01D)
fffff880`00edb000 fffff880`00f7f000 Wdf01000 Wdf01000.sys Tue Jul 14 01:22:07 2009 (4A5BC19F)
fffff880`00f7f000 fffff880`00f8e000 WDFLDR WDFLDR.SYS Tue Jul 14 01:19:54 2009 (4A5BC11A)
fffff880`00f8e000 fffff880`00fe5000 ACPI ACPI.sys Tue Jul 14 01:19:34 2009 (4A5BC106)
fffff880`00fe5000 fffff880`00fee000 WMILIB WMILIB.SYS Tue Jul 14 01:19:51 2009 (4A5BC117)
fffff880`00fee000 fffff880`00ff8000 msisadrv msisadrv.sys Tue Jul 14 01:19:26 2009 (4A5BC0FE)
fffff880`00ff8000 fffff880`01000000 intelide intelide.sys Tue Jul 14 01:19:48 2009 (4A5BC114)
fffff880`01000000 fffff880`01073000 cng cng.sys Tue Jul 14 01:49:40 2009 (4A5BC814)
fffff880`01073000 fffff880`010bf000 volsnap volsnap.sys Tue Jul 14 01:20:08 2009 (4A5BC128)
fffff880`010bf000 fffff880`010d2000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 01:21:51 2009 (4A5BC18F)
fffff880`010de000 fffff880`0112a000 fltmgr fltmgr.sys Tue Jul 14 01:19:59 2009 (4A5BC11F)
fffff880`0112a000 fffff880`0113e000 fileinfo fileinfo.sys Tue Jul 14 01:34:25 2009 (4A5BC481)
fffff880`0113e000 fffff880`0119c000 msrpc msrpc.sys Tue Jul 14 01:21:32 2009 (4A5BC17C)
fffff880`0119c000 fffff880`011d6000 rdyboost rdyboost.sys Tue Jul 14 01:34:34 2009 (4A5BC48A)
fffff880`011d6000 fffff880`011f0000 rassstp rassstp.sys Tue Jul 14 02:10:25 2009 (4A5BCCF1)
fffff880`01200000 fffff880`0121a000 ksecdd ksecdd.sys Tue Jul 14 01:20:54 2009 (4A5BC156)
fffff880`0121a000 fffff880`0122b000 pcw pcw.sys Tue Jul 14 01:19:27 2009 (4A5BC0FF)
fffff880`0122b000 fffff880`01235000 Fs_Rec Fs_Rec.sys Tue Jul 14 01:19:45 2009 (4A5BC111)
fffff880`01235000 fffff880`01256000 raspptp raspptp.sys Tue Jul 14 02:10:18 2009 (4A5BCCEA)
fffff880`0125c000 fffff880`013ff000 Ntfs Ntfs.sys Tue Jul 14 01:20:47 2009 (4A5BC14F)
fffff880`01400000 fffff880`0144a000 fwpkclnt fwpkclnt.sys Tue Jul 14 01:21:08 2009 (4A5BC164)
fffff880`0144a000 fffff880`0145a000 vmstorfl vmstorfl.sys Tue Jul 14 01:42:54 2009 (4A5BC67E)
fffff880`0145a000 fffff880`0145ee00 TVALZ_O TVALZ_O.SYS Tue Jul 14 04:19:26 2009 (4A5BEB2E)
fffff880`0145f000 fffff880`01467000 spldr spldr.sys Mon May 11 18:56:27 2009 (4A0858BB)
fffff880`01467000 fffff880`01479000 mup mup.sys Tue Jul 14 01:23:45 2009 (4A5BC201)
fffff880`01479000 fffff880`0156b000 ndis ndis.sys Tue Jul 14 01:21:40 2009 (4A5BC184)
fffff880`0156b000 fffff880`015cb000 NETIO NETIO.SYS Tue Jul 14 01:21:46 2009 (4A5BC18A)
fffff880`015cb000 fffff880`015f6000 ksecpkg ksecpkg.sys Fri Dec 11 07:03:32 2009 (4B21E0B4)
fffff880`015f6000 fffff880`015ff000 hwpolicy hwpolicy.sys Tue Jul 14 01:19:22 2009 (4A5BC0FA)
fffff880`01603000 fffff880`01800000 tcpip tcpip.sys Tue Jul 14 01:25:34 2009 (4A5BC26E)
fffff880`01800000 fffff880`0182f000 ndiswan ndiswan.sys Tue Jul 14 02:10:11 2009 (4A5BCCE3)
fffff880`01839000 fffff880`01873000 fvevol fvevol.sys Sat Sep 26 04:34:26 2009 (4ABD7DB2)
fffff880`01873000 fffff880`01889000 disk disk.sys Tue Jul 14 01:19:57 2009 (4A5BC11D)
fffff880`01889000 fffff880`018b9000 CLASSPNP CLASSPNP.SYS Tue Jul 14 01:19:58 2009 (4A5BC11E)
fffff880`018b9000 fffff880`018c6000 mouhid mouhid.sys Tue Jul 14 02:00:20 2009 (4A5BCA94)
fffff880`018c6000 fffff880`018d4000 point64k point64k.sys Wed Nov 04 03:55:38 2009 (4AF0ED2A)
fffff880`018d4000 fffff880`018e2000 crashdmp crashdmp.sys Tue Jul 14 02:01:01 2009 (4A5BCABD)
fffff880`018e2000 fffff880`018ee000 dump_dumpata dump_dumpata.sys Tue Jul 14 01:19:47 2009 (4A5BC113)
fffff880`018f1000 fffff880`0191b000 cdrom cdrom.sys Tue Jul 14 01:19:54 2009 (4A5BC11A)
fffff880`0191b000 fffff880`01924000 Null Null.SYS Tue Jul 14 01:19:37 2009 (4A5BC109)
fffff880`01924000 fffff880`0192b000 Beep Beep.SYS Tue Jul 14 02:00:13 2009 (4A5BCA8D)
fffff880`0192b000 fffff880`01950000 ehdrv ehdrv.sys Mon Apr 19 08:47:01 2010 (4BCBFC65)
fffff880`01950000 fffff880`0195e000 vga vga.sys Tue Jul 14 01:38:47 2009 (4A5BC587)
fffff880`0195e000 fffff880`01983000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 01:38:51 2009 (4A5BC58B)
fffff880`01983000 fffff880`01993000 watchdog watchdog.sys Tue Jul 14 01:37:35 2009 (4A5BC53F)
fffff880`01993000 fffff880`0199c000 RDPCDD RDPCDD.sys Tue Jul 14 02:16:34 2009 (4A5BCE62)
fffff880`0199c000 fffff880`019a5000 rdpencdd rdpencdd.sys Tue Jul 14 02:16:34 2009 (4A5BCE62)
fffff880`019a5000 fffff880`019ae000 rdprefmp rdprefmp.sys Tue Jul 14 02:16:35 2009 (4A5BCE63)
fffff880`019ae000 fffff880`019b9000 Msfs Msfs.SYS Tue Jul 14 01:19:47 2009 (4A5BC113)
fffff880`019b9000 fffff880`019ca000 Npfs Npfs.SYS Tue Jul 14 01:19:48 2009 (4A5BC114)
fffff880`019ca000 fffff880`019e8000 tdx tdx.sys Tue Jul 14 01:21:15 2009 (4A5BC16B)
fffff880`019e8000 fffff880`019f5000 TDI TDI.SYS Tue Jul 14 01:21:18 2009 (4A5BC16E)
fffff880`019f5000 fffff880`01a00000 dump_msahci dump_msahci.sys Tue Jul 14 02:01:01 2009 (4A5BCABD)
fffff880`0220a000 fffff880`02225000 USBSTOR USBSTOR.SYS Tue Jul 14 02:06:34 2009 (4A5BCC0A)
fffff880`02225000 fffff880`02233000 monitor monitor.sys Tue Jul 14 01:38:52 2009 (4A5BC58C)
fffff880`02233000 fffff880`0223fe00 tosrfusb tosrfusb.sys Thu Mar 19 06:07:44 2009 (49C1D320)
fffff880`02240000 fffff880`0226a680 tosrfbd tosrfbd.sys Mon Oct 06 10:56:56 2008 (48E9D2D8)
fffff880`0226b000 fffff880`02280a00 Tosrfhid Tosrfhid.sys Thu Mar 05 03:03:33 2009 (49AF32F5)
fffff880`02281000 fffff880`022a4000 luafv luafv.sys Tue Jul 14 01:26:13 2009 (4A5BC295)
fffff880`022a4000 fffff880`0237a000 eamonm eamonm.sys Wed Jun 16 16:39:33 2010 (4C18E225)
fffff880`0237a000 fffff880`0239b000 WudfPf WudfPf.sys Tue Jul 14 02:05:37 2009 (4A5BCBD1)
fffff880`0239b000 fffff880`023ab000 vmnetbridge vmnetbridge.sys Mon Aug 10 14:05:58 2009 (4A800D26)
fffff880`023ab000 fffff880`023c0000 lltdio lltdio.sys Tue Jul 14 02:08:50 2009 (4A5BCC92)
fffff880`02c00000 fffff880`02c3d000 portcls portcls.sys Tue Jul 14 02:06:27 2009 (4A5BCC03)
fffff880`02c3d000 fffff880`02c42200 ksthunk ksthunk.sys Tue Jul 14 02:00:19 2009 (4A5BCA93)
fffff880`02c43000 fffff880`02c51000 kbdhid kbdhid.sys Tue Jul 14 02:00:20 2009 (4A5BCA94)
fffff880`02c5b000 fffff880`02c9e000 ks ks.sys Tue Jul 14 02:00:31 2009 (4A5BCA9F)
fffff880`02c9e000 fffff880`02cb0000 umbus umbus.sys Tue Jul 14 02:06:56 2009 (4A5BCC20)
fffff880`02cb0000 fffff880`02cb8000 vmnetadapter vmnetadapter.sys Mon Aug 10 14:04:53 2009 (4A800CE5)
fffff880`02cb8000 fffff880`02cc2000 VMNET VMNET.SYS Mon Aug 10 14:04:50 2009 (4A800CE2)
fffff880`02cc2000 fffff880`02d1c000 usbhub usbhub.sys Tue Jul 14 02:07:09 2009 (4A5BCC2D)
fffff880`02d1c000 fffff880`02d31000 NDProxy NDProxy.SYS Tue Jul 14 02:10:05 2009 (4A5BCCDD)
fffff880`02d31000 fffff880`02ddd000 CHDMI64 CHDMI64.sys Wed Jun 24 01:28:17 2009 (4A416511)
fffff880`02ddd000 fffff880`02dff000 drmk drmk.sys Tue Jul 14 03:01:25 2009 (4A5BD8E5)
fffff880`03400000 fffff880`0341e000 bowser bowser.sys Tue Jul 14 01:23:50 2009 (4A5BC206)
fffff880`0341e000 fffff880`03436000 mpsdrv mpsdrv.sys Tue Jul 14 02:08:25 2009 (4A5BCC79)
fffff880`03436000 fffff880`03463000 mrxsmb mrxsmb.sys Sat Feb 27 08:52:19 2010 (4B88CF33)
fffff880`034a0000 fffff880`034f3000 nwifi nwifi.sys Tue Jul 14 02:07:23 2009 (4A5BCC3B)
fffff880`034f3000 fffff880`03506000 ndisuio ndisuio.sys Tue Jul 14 02:09:25 2009 (4A5BCCB5)
fffff880`03506000 fffff880`03512000 pnarp pnarp.sys Sat Jun 06 08:06:44 2009 (4A2A0774)
fffff880`03512000 fffff880`0351e000 purendis purendis.sys Sat Jun 06 06:32:06 2009 (4A29F146)
fffff880`0351e000 fffff880`03536000 rspndr rspndr.sys Tue Jul 14 02:08:50 2009 (4A5BCC92)
fffff880`03536000 fffff880`035fe000 HTTP HTTP.sys Tue Jul 14 01:22:16 2009 (4A5BC1A8)
fffff880`03a00000 fffff880`03a51000 rdbss rdbss.sys Tue Jul 14 01:24:09 2009 (4A5BC219)
fffff880`03a51000 fffff880`03a5d000 nsiproxy nsiproxy.sys Tue Jul 14 01:21:02 2009 (4A5BC15E)
fffff880`03a5d000 fffff880`03a68000 mssmbios mssmbios.sys Tue Jul 14 01:31:10 2009 (4A5BC3BE)
fffff880`03a68000 fffff880`03a77000 discache discache.sys Tue Jul 14 01:37:18 2009 (4A5BC52E)
fffff880`03a77000 fffff880`03a9b000 rasl2tp rasl2tp.sys Tue Jul 14 02:10:11 2009 (4A5BCCE3)
fffff880`03a9e000 fffff880`03b28000 afd afd.sys Tue Jul 14 01:21:40 2009 (4A5BC184)
fffff880`03b28000 fffff880`03b6d000 netbt netbt.sys Tue Jul 14 01:21:28 2009 (4A5BC178)
fffff880`03b6d000 fffff880`03b78000 ws2ifsl ws2ifsl.sys Tue Jul 14 02:10:33 2009 (4A5BCCF9)
fffff880`03b78000 fffff880`03b81000 wfplwf wfplwf.sys Tue Jul 14 02:09:26 2009 (4A5BCCB6)
fffff880`03b81000 fffff880`03ba7000 pacer pacer.sys Tue Jul 14 02:09:41 2009 (4A5BCCC5)
fffff880`03ba7000 fffff880`03bb6000 netbios netbios.sys Tue Jul 14 02:09:26 2009 (4A5BCCB6)
fffff880`03bb6000 fffff880`03bd1000 wanarp wanarp.sys Tue Jul 14 02:10:21 2009 (4A5BCCED)
fffff880`03bd1000 fffff880`03be5000 termdd termdd.sys Tue Jul 14 02:16:36 2009 (4A5BCE64)
fffff880`03be5000 fffff880`03c00000 raspppoe raspppoe.sys Tue Jul 14 02:10:17 2009 (4A5BCCE9)
fffff880`03c00000 fffff880`03c55000 SynTP SynTP.sys Fri Nov 30 02:17:43 2007 (474F64B7)
fffff880`03c55000 fffff880`03c60000 rdpbus rdpbus.sys Tue Jul 14 02:17:46 2009 (4A5BCEAA)
fffff880`03c62000 fffff880`03ce5000 csc csc.sys Tue Jul 14 01:24:26 2009 (4A5BC22A)
fffff880`03ce5000 fffff880`03d03000 dfsc dfsc.sys Tue Jul 14 01:23:44 2009 (4A5BC200)
fffff880`03d03000 fffff880`03d14000 blbdrive blbdrive.sys Tue Jul 14 01:35:59 2009 (4A5BC4DF)
fffff880`03d14000 fffff880`03d3a000 tunnel tunnel.sys Tue Jul 14 02:09:37 2009 (4A5BCCC1)
fffff880`03d3a000 fffff880`03d50000 intelppm intelppm.sys Tue Jul 14 01:19:25 2009 (4A5BC0FD)
fffff880`03d50000 fffff880`03d54500 CmBatt CmBatt.sys Tue Jul 14 01:31:03 2009 (4A5BC3B7)
fffff880`03d55000 fffff880`03d5f000 tosrfec tosrfec.sys Mon Oct 23 09:33:06 2006 (453C7032)
fffff880`03d5f000 fffff880`03d68000 wmiacpi wmiacpi.sys Tue Jul 14 01:31:02 2009 (4A5BC3B6)
fffff880`03d68000 fffff880`03dbe000 USBPORT USBPORT.SYS Tue Jul 14 02:06:31 2009 (4A5BCC07)
fffff880`03dbe000 fffff880`03dcd000 mouclass mouclass.sys Tue Jul 14 01:19:50 2009 (4A5BC116)
fffff880`03dcd000 fffff880`03ddd000 CompositeBus CompositeBus.sys Tue Jul 14 02:00:33 2009 (4A5BCAA1)
fffff880`03ddd000 fffff880`03df3000 AgileVpn AgileVpn.sys Tue Jul 14 02:10:24 2009 (4A5BCCF0)
fffff880`03df3000 fffff880`03dff000 ndistapi ndistapi.sys Tue Jul 14 02:10:00 2009 (4A5BCCD8)
fffff880`03e00000 fffff880`03e63000 yk62x64 yk62x64.sys Mon Feb 23 16:02:27 2009 (49A2BA83)
fffff880`03e63000 fffff880`03e6fd00 o2mdx64 o2mdx64.sys Tue Mar 04 01:00:23 2008 (47CC9117)
fffff880`03e70000 fffff880`03e71f00 USBD USBD.SYS Tue Jul 14 02:06:23 2009 (4A5BCBFF)
fffff880`03e72000 fffff880`03e73480 swenum swenum.sys Tue Jul 14 02:00:18 2009 (4A5BCA92)
fffff880`03e74000 fffff880`043af000 netw5v64 netw5v64.sys Thu Mar 26 17:21:24 2009 (49CBAB84)
fffff880`043af000 fffff880`043ed000 1394ohci 1394ohci.sys Tue Jul 14 02:07:12 2009 (4A5BCC30)
fffff880`043ed000 fffff880`043f8280 o2sdx64 o2sdx64.sys Fri Feb 29 11:09:33 2008 (47C7D9DD)
fffff880`04600000 fffff880`046d6000 vmx86 vmx86.sys Sat Jan 23 06:50:05 2010 (4B5A8E0D)
fffff880`046d6000 fffff880`04724000 mrxsmb10 mrxsmb10.sys Sat Feb 27 08:52:28 2010 (4B88CF3C)
fffff880`04724000 fffff880`04747000 mrxsmb20 mrxsmb20.sys Sat Feb 27 08:52:26 2010 (4B88CF3A)
fffff880`04747000 fffff880`04753000 hcmon hcmon.sys Sat Jan 23 05:08:59 2010 (4B5A765B)
fffff880`04753000 fffff880`0476b000 vmci vmci.sys Sat Jan 23 04:33:23 2010 (4B5A6E03)
fffff880`0477b000 fffff880`0479c000 epfwwfpr epfwwfpr.sys Mon Apr 19 08:43:18 2010 (4BCBFB86)
fffff880`0479c000 fffff880`047a0280 mdmxsdk mdmxsdk.sys Mon Jun 19 23:27:26 2006 (449716BE)
fffff880`047a1000 fffff880`047d7000 fastfat fastfat.SYS Tue Jul 14 01:23:28 2009 (4A5BC1F0)
fffff880`04800000 fffff880`0482f000 SCSIPORT SCSIPORT.SYS Tue Jul 14 02:01:04 2009 (4A5BCAC0)
fffff880`0482f000 fffff880`0484d000 i8042prt i8042prt.sys Tue Jul 14 01:19:57 2009 (4A5BC11D)
fffff880`0484d000 fffff880`04e64000 atikmdag atikmdag.sys Tue Aug 18 05:05:47 2009 (4A8A1A8B)
fffff880`04e64000 fffff880`04f58000 dxgkrnl dxgkrnl.sys Fri Oct 02 03:00:14 2009 (4AC5509E)
fffff880`04f58000 fffff880`04f9e000 dxgmms1 dxgmms1.sys Tue Jul 14 01:38:32 2009 (4A5BC578)
fffff880`04f9e000 fffff880`04fc2000 HDAudBus HDAudBus.sys Tue Jul 14 02:06:13 2009 (4A5BCBF5)
fffff880`04fc2000 fffff880`04fcf000 usbuhci usbuhci.sys Tue Jul 14 02:06:27 2009 (4A5BCC03)
fffff880`04fcf000 fffff880`04fe0000 usbehci usbehci.sys Tue Jul 14 02:06:30 2009 (4A5BCC06)
fffff880`04fe0000 fffff880`04fef000 kbdclass kbdclass.sys Tue Jul 14 01:19:50 2009 (4A5BC116)
fffff880`04fef000 fffff880`04ffa000 VMkbd VMkbd.sys Sat Jan 23 06:04:47 2010 (4B5A836F)
fffff880`05200000 fffff880`052cb000 CAX_CNXT CAX_CNXT.sys Fri Aug 03 20:04:26 2007 (46B36E2A)
fffff880`052d4000 fffff880`05380000 CHDRT64 CHDRT64.sys Wed Jun 24 01:28:17 2009 (4A416511)
fffff880`05380000 fffff880`053d3000 CAXHWAZL CAXHWAZL.sys Fri Aug 03 20:05:44 2007 (46B36E78)
fffff880`053d3000 fffff880`053e1000 hidusb hidusb.sys Tue Jul 14 02:06:22 2009 (4A5BCBFE)
fffff880`053e1000 fffff880`053fa000 HIDCLASS HIDCLASS.SYS Tue Jul 14 02:06:21 2009 (4A5BCBFD)
fffff880`05600000 fffff880`0560c000 Dxapi Dxapi.sys Tue Jul 14 01:38:28 2009 (4A5BC574)
fffff880`0560c000 fffff880`05629000 usbccgp usbccgp.sys Tue Jul 14 02:06:45 2009 (4A5BCC15)
fffff880`05629000 fffff880`05631000 UVCFTR_S UVCFTR_S.SYS Thu Jun 26 10:25:22 2008 (48635272)
fffff880`05631000 fffff880`0565e100 usbvideo usbvideo.sys Tue Jul 14 02:07:00 2009 (4A5BCC24)
fffff880`0565f000 fffff880`0566b000 dc3d dc3d.sys Wed Nov 04 03:55:41 2009 (4AF0ED2D)
fffff880`0566b000 fffff880`05673080 HIDPARSE HIDPARSE.SYS Tue Jul 14 02:06:17 2009 (4A5BCBF9)
fffff880`0567c000 fffff880`057ee000 CAX_DPV CAX_DPV.sys Fri Aug 03 20:08:37 2007 (46B36F25)
fffff880`057ee000 fffff880`057fd000 modem modem.sys Tue Jul 14 02:10:48 2009 (4A5BCD08)
fffff880`05e00000 fffff880`05e69000 srv2 srv2.sys Tue Jul 14 01:25:02 2009 (4A5BC24E)
fffff880`05ea7000 fffff880`05f4d000 peauth peauth.sys Tue Jul 14 03:01:19 2009 (4A5BD8DF)
fffff880`05f4d000 fffff880`05f58000 secdrv secdrv.SYS Wed Sep 13 15:18:38 2006 (4508052E)
fffff880`05f58000 fffff880`05f85000 srvnet srvnet.sys Tue Dec 08 09:32:26 2009 (4B1E0F1A)
fffff880`05f85000 fffff880`05f8d000 SSPORT SSPORT.sys Fri Aug 12 01:07:32 2005 (42FBDA34)
fffff880`05f8d000 fffff880`05f9f000 tcpipreg tcpipreg.sys Tue Jul 14 02:09:49 2009 (4A5BCCCD)
fffff880`05f9f000 fffff880`05fa9000 vmnetuserif vmnetuserif.sys Sat Jan 23 05:26:19 2010 (4B5A7A6B)
fffff880`05fa9000 fffff880`05fb5000 vstor2_ws60 vstor2-ws60.sys Mon Oct 12 23:06:26 2009 (4AD39A52)
fffff880`05fb5000 fffff880`05fbd000 xaudio64 xaudio64.sys Tue Aug 07 23:26:35 2007 (46B8E38B)
fffff880`0640d000 fffff880`064a5000 srv srv.sys Tue Dec 08 09:32:55 2009 (4B1E0F37)
fffff880`064a5000 fffff880`064d6000 WUDFRd WUDFRd.sys Tue Jul 14 02:06:06 2009 (4A5BCBEE)
fffff880`064d6000 fffff880`064e1000 asyncmac asyncmac.sys Tue Jul 14 02:10:13 2009 (4A5BCCE5)
fffff960`00070000 fffff960`0037f000 win32k win32k.sys unavailable (00000000)
fffff960`004f0000 fffff960`004fa000 TSDDD TSDDD.dll unavailable (00000000)
fffff960`007a0000 fffff960`007c7000 cdd cdd.dll unavailable (00000000)
fffff960`00900000 fffff960`00961000 ATMFD ATMFD.DLL unavailable (00000000)
Unloaded modules:
fffff880`064e1000 fffff880`06552000 spsys.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00071000
fffff880`0476b000 fffff880`0477b000 DgiVecp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00010000
fffff880`018b9000 fffff880`018c7000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
fffff880`018c7000 fffff880`018d3000 dump_pciidex
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000C000
fffff880`018d3000 fffff880`018de000 dump_msahci.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000B000
fffff880`018de000 fffff880`018f1000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00013000
Closing open log file c:\debuglog.txt

Similar Messages

BSOD Caused on Windows 7 64-bit while watching Netflix Instant in Firefox 4.0

Starting with the latest version of Firefox 4 - I'm getting BSoD's in Windows 7 64-bit SP1 while watching Netflix Instant. My system will crash with a DirectX DLL file being labelled as the culprit.

Disregard, it turns out to be an issue with the latest WHQL nVidia drivers, I rolled back to a previous version and the problem stopped. I only found this out after experiencing the same exact crash in IE9.

BSOD 0x00000124 for Windows 7 64 bit

Can anybody help me with this issue? I am unsure how to output the log to a dump file for further analysis.
My computer info is:
   Processor: 2.30 GHz AMD Phenom 9600 Quad-Core
   MB: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H
   Video Cards: ATI Radeon HD 3200 onboard video, Radeon HD 4670
   OS: Windows 7 64 bit
I've been checked the hotfixes offered by Microsoft but there aren't any available for Windows 7 64 bit. I do not know if the hotfixes for Windows Vista 64 bit can be used to fix this problem or not.
I've tried updating my BIOS and then restoring my BIOS to its factory settings but neither seemed to work. I've installed drivers via windows update, from the gigabyte website, and from the ATI website trying to update to the latest drivers. I've used Ultimate
Boot CD to test my RAM and HDD, I've used Hot CPU Tester Pro 4 to test my CPU, I've tried using my PCI-E video card and my onboard video card (separately of course), but all these tests have not shown any errors or problems with the hardware devices. The only
ones that I haven't really tested are my PSU and MB (the sound card is onboard). I've even performed a clean installation of windows 7 64 bit (previously using Windows Vista 32 bit) but the problem still persists. I am not sure what else to test without just
buying new hardware.
This error normally happens when I play a video game (like World of Warcraft) but lately when I try to install patches or games in general I seem to get the BSOD.
Can anyone help me please? Just let me know if you would need more information about my system or how I can get to my logs (the dump files) so I can provide more information.
Thanks

You may boot in Clean Boot Mode as BSOD can be caused by programs that are running in kernel mode.
Perform a clean startup to determine whether background programs are interfering with your game or program
If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files,
rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver
is the root cause.
Another way is enable muni-dump and use Windbg. Please refer:
How to read the small memory dump files that Windows creates for debugging
You may paste the result in your next post for analyzing.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

ITunes 9.1 (64-bit) causing BSOD crashes with Windows 7

I installed iTunes 9.1 (64-bit) this evening and my computer running Windows 7 (64-bit) repeatedly experienced the blue screen of death (BSOD). The computer would restart in safe mode. Upon restart, the BSOD would occur again within a few minutes.
iTunes was successfully installed and was operable up until the blue screen.
I completed a system restore and my system is stable once again. However, certain iTunes files were removed and now iTunes will not function.
Does anyone have a link to an iTunes 9.0.3 for Windows 7 (64-bit)?
Has anyone experienced a similar problem and have a solution that allows 9.1 to work without crashing my machine?

FF,
I had the exact same problem. I upgraded iTunes to 9.1 and it caused a BSOD. I booted into Windows Safe Mode (Hit F8 as soon as you see the Windows start up screen) and disabled the itunes services. Rebooted and the system is now working. I'm not sure what the deal is with the iTunes 9.1 but it definately breaks Windows 7.

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 workhorse

Dear 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

BSOD after installing Windows Vista Update Package

Ok, so I am not good with computers, so I have no idea what to do. I have looked everywhere and still cannot find a solution that seems plausible with my error.
The other day I was on my computer and it was running perfectly fine. No freezing, no slowness, perfect. Then, my update thing told me that the most recent Vindows Service pack was available for update, and I like to keep up-to-date with them, so I installed and it was set to automatically update.
I have an IBM ThinkPad t61p with Windows Vista Ultimate.
After restarting the computer I left for a while and came back to the checkdisk running. I had not told it to run, and it had frozen at 74% on step 5/5 of the checkdisk, which I am assuming means that I have some sort of hard drive corruption. So, I was forced to turn off with holding the power button and when it turned on again it went straight to the diskcheck and I watched it until it froze at the same point again. The next time I restarted I got the blue screen of death and now that is all I get whether I start in safe mode, or any other mode.
I had a virus or something a while ago that kept freezing my computer, but I think I got rid of it as it has been working fine over the past 5/6 weeks. I also don't think it is a problem with not having enough RAM because I just uninstalled a couple programs that were taking up a lot of space, and even before that it wasn't close to full.
I get stop: 0x00000024 error and it goes into a restart loop
When I press the blue ThinkVantage button and go to the F11 menu it tries to open rescue and recovery, but after about 2 minutes it goes back to the infinite restart loop.
I also tried running the hard drive diagnostics program and IDK how to interpret the results, but it says:
Main Hard Disk Drive.......HDD0: HITACHI (gives me the id code)
Status......Test in progress 100%
Result......Pass: Controller Diag, Pass: Read verification and speed test
I have no idea what is wrong and it is so frustrating!!!!!!! What should I do if I can even do anything?! I need help!!!! T_T
(As a last resort I also tried installing XP on my Vista machine. I didn't think it would work, but I put boot CD in the first spot, and put cd in, but it just goes to the BSOD again.)

this error is so much obvius.
just look on internet on how to disable readyboost. additional just turn off the hybrid function and u will never see this bsod again, even i dont know how dumb ur mediacenter edition is and want to give u other bsods. btw i only seen bsods couse of **bleep** driver on my devices. donno how u manage to get such bluescreens......
btw according to the results i recommning ya to use ckhdsk /f to ur disk. mstWorker is mentioned wich means read write issues on access files. mstworker is microsoft Tiworker, an process wich examines files an bit. used by winupdate and the indexer.

BSOD when installing Windows XP on ThinkPad x220

Hi,
I have just bought a ThinkPad x220 (4293-AA6) with no OS installed. I am trying to install Windows XP (32-bit), but have not yet been successful.
I have carefully followed section in the User Guide called "Installing Windows XP", but this has not worked for me. In summary, the procedure I followed was:
In BIOS, set "Serial ATA (SATA)" to "AHCI",
Set "UEFI/Legacy Boot" to "Both" or "Legacy Only" (makes no difference to my problem)
Boot from Win XP SP2 CD
Press F6 when prompted, put the Lenovo "Intel Rapid Storage Technology Driver drivers" in floppy drive, and select "Intel MobileExpress Chipset SATA AHCI Controller". Drivers were extracted from this file: this file
Continue the installation
The result is a Blue Screen of Death (BSOD) just after the setup screen says "Setup is starting Windows", with the error message:
"STOP: 0x0000007B (0xf78d2524,0xc0000034,0x00000000,0x00000000)"
Other things I have tried:
Followed the alternative procedure outlined in the User Guide, under "If you do not have a diskette drive..."
Updated the BIOS from 1.15 to 1.17
Ran memtest86+ (resulted in no errors)
Tried the "Intel Rapid Storage Technology Driver" from the Intel website rather than the Lenovo website
Selected the "Intel 5 Series 6 Port SATA AHCI Controller" instead of the other one when installing the drivers
Tried using a WinXP SP3 CD instead of SP2
Formatted the disk using diskpart
Installed Ubuntu 11.04 to the harddrive (successfully!!) then tried installing Windows XP again
But I always get the same BSOD.
I have also tried installing Windows 7 (64-bit), which also failed! It booted into the installation program, but then it stopped and said it couldn't find a driver for a CD/DVD drive. After installing the appropriate 64-bit Lenovo IRST driver and rebooting, this resulted in the following Blue Screen of Death: "STOP: 0x000000F4 (0x0000000000000003,..."
Is anyone able to help me with getting Windows (XP or even 7) installed? Any help or ideas would be much appreciated, and I'm happy to provide more information/tests if needed.
Thanks in advance,
Roy

Waldo000000 wrote:
Oh, perhaps I should emphasise that this X220 model comes with the "160GB Solid State Drive". Perhaps that needs a different driver or something...??
SSDs are Advanced Format disks, which XP does not know anything about. Please read the white paper which can be found here.....
http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-76990
This will give you guidance on what to do.
Cheers,
Bill
I don't work for Lenovo

BSOD when installing Windows 7 on MacBook Pro Retina

I tried everything I could but I'm unable to install Windows 7 on my MBP Retina using Boot Camp because of recurring blue screens always happening at exactly the same time.
After creating a new partition with Boot Camp and restarting to the point where the MBP is supposed to boot from the Windows 7 installation CD or USB flash drive (tried both), the black and white "Windows is loading files" passes without problems but I ALWAYS get a BSOD a few seconds after the Windows splash screen appears.
Here are some examples of the errors I get:
I tried reformatting and reinstalling Lion on my SSD several times, I even ran extensive memtest batteries but the RAM appears to be OK. I really don't know what to do anymore.
I read that Windows has issues with the HFS file system which can cause BSODs but since the error appears before I can even install Windows I cannot modify anything in the Windows installation. Then again it could be a ton of other things...

Could be you khave a corrupted Win 7 install file/files.
Try downloading the Win 7 ISO for the version you have from here.
http://www.mydigitallife.info/download-windows-7-iso-official-32-bit-and-64-bit- direct-download-links/
Then burn that ISO to a USB or DVD, USB would be better.

Random BSOD after installing Windows 8.1 on Lynx K3011

I upgraded the graphics drivers as intructed her in another thread and that works now. However I keep getting a random BSOD with the error MEMORY_MANAGEMENT.
I did a bug check analysis and this is the result:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101413-9031-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 8 Kernel Version 9600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16384.x86fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0x81c14000 PsLoadedModuleList = 0x81e0e218
Debug session time: Mon Oct 14 12:47:54.837 2013 (UTC - 7:00)
System Uptime: 0 days 0:00:09.648
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis                                    *
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {1238, 85ea6368, 802, 0}
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+4c )
Followup: MachineOwner
3: kd> !analyze -v
*                        Bugcheck Analysis                                    *
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00001238, The subtype of the bugcheck.
Arg2: 85ea6368
Arg3: 00000802
Arg4: 00000000
Debugging Details:
BUGCHECK_STR: 0x1a_1238
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 81d63c8d to 81d14ce4
STACK_TEXT:
8b90ebf0 81d63c8d 0000001a 00001238 85ea6368 nt!KeBugCheckEx
8b90ec38 82d1abb4 85ea6368 8506b040 00000162 nt! ?? ::FNODOBFM::`string'+0x355e7
8b90ec54 82d18dec 00000000 8506bd10 00000001 rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+0x4c
8b90ecc4 82d1704b 00000000 86291040 8506b008 rdyboost!ST_STORE<SMD_TRAITS>:tDmPageRemove+0x3ac
8b90ed00 82d1739e 00000000 8506c200 83a4b040 rdyboost!ST_STORE<SMD_TRAITS>:tWorkItemProcess+0xf3
8b90ed40 82d266a0 ce25f08e 00000000 8506c200 rdyboost!SMKM_STORE<SMD_TRAITS>:mStWorker+0xfc
8b90ed70 81cc36a8 8506b008 61b2fcc6 00000000 rdyboost!SMKM_STORE<SMD_TRAITS>:mStWorkerThread+0x1d
8b90edb0 81d2a701 82d26683 8265bf68 00000000 nt!PspSystemThreadStartup+0x58
8b90edbc 00000000 00000000 2444c718 80000010 nt!KiThreadStartup+0x15
STACK_COMMAND: kb
FOLLOWUP_IP:
rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+4c
82d1abb4 6a00            push    0
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: rdyboost!ST_STORE<SMD_TRAITS>:tReleaseRegion+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: rdyboost
IMAGE_NAME: rdyboost.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52158f40
BUCKET_ID_FUNC_OFFSET: 4c
FAILURE_BUCKET_ID: 0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_:tReleaseRegion
BUCKET_ID: 0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_:tReleaseRegion
Followup: MachineOwner
Any ideas? Probably more incompatible drivers. If I can't get Windows 8.1 running correctly, does anyone know how to restore the system image?
Solved!
Go to Solution.

this error is so much obvius.
just look on internet on how to disable readyboost. additional just turn off the hybrid function and u will never see this bsod again, even i dont know how dumb ur mediacenter edition is and want to give u other bsods. btw i only seen bsods couse of **bleep** driver on my devices. donno how u manage to get such bluescreens......
btw according to the results i recommning ya to use ckhdsk /f to ur disk. mstWorker is mentioned wich means read write issues on access files. mstworker is microsoft Tiworker, an process wich examines files an bit. used by winupdate and the indexer.

BSOD issues with windows 8.1

I often get BSOD while playing battlefield 4 but sometimes i get BSOD while im on firefox. I have been looking for an answer but never got one. I think my drivers are up-to-date but im not really sure beacuse i'm not an expert of computers. My dump files
can be found here: https://onedrive.live.com/redir?resid=B104A9FADF76B2%21178
This is a major problem so I would be pleased if someone could help me .

Hi,
Both of the attached DMP files are of the
PFN_LIST_CORRUPT (4e) bug check.
This indicates that the page frame number (PFN) list is corrupted.
This error is typically caused by a driver passing a bad memory descriptor list.
3: kd> k
Child-SP RetAddr Call Site
ffffd000`25f8cf88 fffff800`3dc78b3f nt!KeBugCheckEx
ffffd000`25f8cf90 fffff800`3dad17c3 nt!MiBadShareCount+0x4b
ffffd000`25f8cfd0 fffff800`3de79b9c nt!MmUnmapViewInSystemCache+0x9b3
ffffd000`25f8d2e0 00000000`00000000 nt!CcUnmapVacb+0x58
^^ nt!MiBadShareCount called into the bugcheck, and we have other memory related calls there as well. Looks like faulty RAM at first glance, so I'd like to go ahead and run Memtest first as opposed to checking for a driver causing corruption.
I checked the modules list and there doesn't appear to be anything problematic that would lead to such memory corruption, aside from maybe an out of date Creative driver, but it wouldn't be the first time I was wrong about that.
Ensure your Creative driver is 100% up to date -
http://support.creative.com/
-- AFAIK, Creative marks their latest drivers for Windows 8 as 'beta' and do not have an official version yet, at least for my sound card. Yours may be the same, just some food for thought. They are still okay to download and install if this is the case for
you as well.
If you crash after the above, let's run Memtest for NO LESS than ~8 passes (several hours):
Memtest86+:
Download Memtest86+ here:
http://www.memtest.org/
Which should I download?
You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary
files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).
How Memtest works:
Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.
The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because
of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.
Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance
is error-free with these faster settings.
Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.
This information, if available to the program, can be displayed via a menu option.
Any other questions, they can most likely be answered by reading this great guide here:
http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting
Regards,
Patrick

BSOD when starting windows 7

My original processor in my HP Pavillion laptop went and I replaced it with a Core i5 480M but when I start the computer all it does is BSOD! I uninstalled the graphics drivers and when I try to use the ATi Radeon graphics, all I get is "Windows has stopped this device because it has reported problems"
This question was solved.
View Solution.

Munk451 wrote:
Spoke too soon, all it does is BSOD!
Start in safe mode and uninstall the AMD drive and redownload the HP AMD driver on their site and install that and reboot and see if the BSOD goes away?
I am a Volunteer to help others on here-not a HP employee.
Replies aren't online 24/7 because of Time Zone differences.
Remember in this Day and Age of Computing the Internet is Knowledge at your fingertips if you choose understand it. -2015-

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 workhorse

Thanks 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

BSOD when installing Windows XP

I have two R500 ThinkPads that came with Vista Home Basic sp1. I need to install Windows XP Pro sp2 on the laptops but I keep getting a BSOD when I boot from the XP installation cd. The BSOD error is:
A problem has been detected and windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:
Check for viruses on your computer. Remove any newly installed hard drives or hard drive controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer.
Technical information:
*** STOP: 0x0000007B (0xF7C04524, 0xC0000034, 0x00000000, 0x00000000)
The laptops are both brand new, I did make recovery disks of the vista install, but I really need XP installed on them to work with our system. Any help would be greatly appreciated.

There's a slightly easier way than slipstreaming.
The issue is that XP doesn't have driver support for the SATA AHCI controller on that system. However, you can download that driver here: http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-70477
You'll need to extract that and put it in the root of a floppy (yeah, a floppy... looking for the A: drive is hardcoded in to the XP install).
When you boot to the XP CD, press F6 when prompted (it'll say "Press F6 to install third-party SCSI controller" or something similar along the bottom).
Windows will load some files and eventually bring you to a screen with a couple of options. It'll tell you your current controller is "<none>" and allow you to press S to specify a driver. Once you do, it'll scan the A drive and load up the entries from the txtsetup.oem file you extracted from the driver.
The selection you want doesn't show up by default. There aren't any scroll bars, but you can scroll through the list using the arrow keys. You want "Intel(R) ICH9M-E/M SATA AHCI Controller" which is the 7th from the bottom.
Select that, Windows will load it, the install will continue and you'll be golden.
If you don't want to bother with scrolling, you can open the txtsetup.oem file and find this line (near the top):
[Defaults]
scsi = iaStor_ICH8MEICH9ME
Change that to:
[Defaults]
scsi = iaAHCI_ICH9MEM
And the proper controller will be highlighted by default so you don't have to arrow through the list.
If all of that is too much of a pain, you can go in to the BIOS under Config->SATA and change AHCI to Compatibility and load Windows w/o the IMSM driver. Once Windows is loaded, you can install the driver and enable AHCI mode using the install.cmd file in the PREPARE directory of the driver linked above.
Hope this helps.
Full disclosure: Lenovo issues my paychecks.

BSOD while installing Windows 7

Hi everyone , I got a different BSOD problem while installing Windows 7 from Recovery CDs i made .
first i got HP Pavilion dv6-6155ee Entertainment Notebook
The problem starts approximately from two weeks , Win 7 starts to stop while i am
working so i made a recovery through the rec. partition i got two OS Ubuntu and WIn 7 , Making the recovery make a
problem in boot so i used Boot repair Disk , and i do the recovery
[url=http://postimg.org/image/65ojt3p7n/][img]http://s13.postimg.org/65ojt3p7n/20130810_011028.jpg[/img][...
but the BSOD problem doesn't go off i tried to Update the drives , i used Driver Verifier but it seems as it is not working , i made a CHKDSK But no error appeared .
i decided to install a fresh windows from the rec. Cds and i chose Factory reset
[url=http://postimg.org/image/jsxld146b/][img]http://s21.postimg.org/jsxld146b/20130817_183029.jpg[/img][...
but here is the problem that i face now during installing software
[url=http://postimg.org/image/v1rwir8v1/][img]http://s22.postimg.org/v1rwir8v1/ded.jpg[/img][/url]
BSOD appears in different errors
[url=http://postimg.org/image/trj26q4kd/][img]http://s22.postimg.org/trj26q4kd/20130810_181958.jpg[/img][...
[url=http://postimg.org/image/s4yfz8hwd/][img]http://s22.postimg.org/s4yfz8hwd/20130810_163605.jpg[/img][...
[url=http://postimg.org/image/e8hj8jwtz/][img]http://s15.postimg.org/e8hj8jwtz/IMG_20130816_WA0012.jpg[/i...
[url=http://postimg.org/image/ktu98bcon/][img]http://s15.postimg.org/ktu98bcon/20130817_174511.jpg[/img][...
[url=http://postimg.org/image/upiit7jlt/][img]http://s16.postimg.org/upiit7jlt/20130813_182434.jpg[/img][...
[url=http://postimg.org/image/pdzdwsb4z/][img]http://s21.postimg.org/pdzdwsb4z/20130812_190022.jpg[/img][...
[url=http://postimg.org/image/kub7buie5/][img]http://s22.postimg.org/kub7buie5/20130812_172515.jpg[/img][...
[url=http://postimg.org/image/c43k35oe1/][img]http://s12.postimg.org/c43k35oe1/20130812_015335.jpg[/img][...
[url=http://postimg.org/image/f8uo2d8tr/][img]http://s11.postimg.org/f8uo2d8tr/20130810_223406.jpg[/img][...
I also tried to change the Bios Date from 2013 to 2011 but nothing , i make sure that the wifi is on , i do memrytest 86 - Memory Test - HDD Test and no error detected
[url=http://postimg.org/image/p1j99450t/][img]http://s14.postimg.org/p1j99450t/20130814_042942.jpg[/img][...
[url=http://postimg.org/image/ylbyflnxj/][img]http://s23.postimg.org/ylbyflnxj/20130810_190505_1.jpg[/img...
[url=http://postimg.org/image/45a015pwt/][img]http://s14.postimg.org/45a015pwt/20130814_042942.jpg[/img][...
i read that using kill disk will fix it So i used it for the rec. partition and c: partition
and nothing changed
and of course F8 wont help as there is no windows now .
so do you have any ideas that may Help and thanks in advance

see this topic as the images can't be displayed : http://www.tomshardware.com/answers/id-1770940/bsod-errors.html

Which windows bit to use with parallels

I'm a Newby, and I"m looking to use Parallels with my new Mac Pro 13" duo processor I7. So, I need to get Parallels and was looking at a Windows 7 OEM disk. Never have thought much about 32 or 64 bit, what's the difference and is one better then the other for everyday computing?

Hi for what it is worth ...
I am using a MacBook Pro with 8G ram, and due to some of the applications I have to run for work, I run Parallels and Windows 7 64 bit
I find the Windows platform VERY stable. I went for Parallels, as I want to run Windows inside my Mac environment, and bit not want to dual boot i.e. have to shut down programs to switch from one to the other.
All the updates work very well, all the applications I run in the Windows environment are stable, and cause me no problems at all.
Everything on the MAC runs well, with no effect on the processes. When I plug anything into the USB ports, I am then given the option if I want teh device to run in the Mac environment or the Windows,
Hope that helps

BSOD POWER_STATE_FAILURE in Windows 7 64 bit

Similar Messages

Maybe you are looking for