BSOD BUGCODE_US​B_DRIVER (fe)

Hi,
I've been getting the above mentioned BSOD almost everyday. I initially thought I may have developed some motherboard issue, so I purchased a replacement motherboard for my system. It all seemed to be stable for a few days after replacing the motherboard. Today I decided to go to the GYM and noticed that my itouch was dead flat and plugged it in so it can charge.
When the itunes application loaded, i was prompted to update to the latest itunes version. I clicked OK or next or some thing like that and while it was downloading I received the same BSOD BUGCODEUS​BDRIVER (fe)again.
So decided to uninstall itunes and now the system seems stable again. I can't beleive it, I'm so upset that I went and purchased another motherboar, cost me $100 and to find that there is nothing wrong with the original board is very disappointing to say the least.
So, upset and all now, could someone tell me if there are any known issues with itunes causing BSOD BUGCODEUS​BDRIVER (fe)and if so what is the fix. I did google search and found hit http://www.pcreview.co.uk/forums/thread-296705.php mentions a problem with CD/DVD Burn feature in itunes. to try stopping some service to see if that helps. if that being the case, what kind of a stupid feature is that, and why should it cause BSOD?
Anyone have any ideas?
Here is one of my original memory dumps when the problem first occured, I haven't bothered to check the latest BSOD....
0: kd> !analyze -v
* Bugcheck Analysis *
BUGCODEUSBDRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODEINVALID_PHYSICALADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: 86b240e0, Device extension pointer of the host controller
Arg3: 10de056a, PCI Vendor,Product id for the controller
Arg4: 87b905d0, Pointer to Endpoint data structure
Debugging Details:
Unable to load image \SystemRoot\system32\DRIVERS\usbehci.sys, Win32 error 0n2
* WARNING: Unable to verify timestamp for usbehci.sys
* ERROR: Module load completed but symbols could not be loaded for usbehci.sys
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
* WARNING: Unable to verify timestamp for sptd.sys
* ERROR: Module load completed but symbols could not be loaded for sptd.sys
* Your debugger is not using the correct symbols *
* In order for this command to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* Type referenced: usbport!DEVICEEXTENSION *
CUSTOMERCRASHCOUNT: 1
DEFAULTBUCKETID: VISTADRIVERFAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: services.exe
CURRENT_IRQL: 2
LASTCONTROLTRANSFER: from 916341ee to 82d2bd10
STACK_TEXT:
8078ada0 916341ee 000000fe 00000005 86b240e0 nt!KeBugCheckEx+0x1e
8078adcc 916804fa 98999a80 86b24028 87b905d0 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x152
WARNING: Stack unwind information not available. Following frames may be wrong.
8078adf0 91681eca 86b24fe0 87b905d0 86b24c6c usbehci+0x44fa
8078ae40 91684cd2 86b24fe0 87b905d0 8078ae6c usbehci+0x5eca
8078ae50 9163428a 86b24fe0 87b905d0 82c8f354 usbehci+0x8cd2
8078ae6c 916326c2 86b240e0 87b90402 82c8f354 USBPORT!MPf_PollEndpoint+0x96
8078ae90 916325ca 00000004 87b904ac 0000000e USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xef
8078aeb0 916339cb 86b24028 87b90430 0000000e USBPORT!USBPORT_iSetGlobalEndpointState+0x18
8078aed8 91633d18 87b90430 86b24720 86b24002 USBPORT!USBPORTCore_UsbHcIntDpcWorker+0x158
8078aefc 8baba894 86b2472c 86b24002 00000000 USBPORT!USBPORTXdpcWorker+0x173
8078af48 82cb73b5 86b2472c 86b24720 00000000 sptd+0x11894
8078afa4 82cb7218 82d78d20 85a23d48 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 82cb69dc bf6cdce4 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 bf6cdce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82cb69dc 00000000 0000001a 00d6850f bb830000 0xbf6cdce4
STACK_COMMAND: kb
FOLLOWUP_IP:
usbehci+44fa
916804fa ?? ???
SYMBOLSTACKINDEX: 2
SYMBOL_NAME: usbehci+44fa
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbehci
IMAGE_NAME: usbehci.sys
DEBUGFLR_IMAGETIMESTAMP: 4ae27b7f
FAILUREBUCKETID: 0xFEINVALID_PHYSICAL_ADDRusbehci+44fa
BUCKET_ID: 0xFEINVALID_PHYSICAL_ADDRusbehci+44fa
Followup: MachineOwner
0: kd> !drivers
The !drivers command is no longer supported.
Please use the 'lm t n' command.
Consult the debugger documentation for the supported 'lm' command options.
The WinDbg "Modules" window can also be used to display timestamps.
The "Modules" window supports sorting on name or timestamp values
0: kd> lm t n
start end module name
80b9e000 80ba6000 kdcom kdcom.dll Tue Jul 14 11:08:58 2009 (4A5BDAAA)
822b0000 824fa000 win32k win32k.sys Sun May 02 00:49:02 2010 (4BDC3F5E)
82510000 82519000 TSDDD TSDDD.dll Tue Jul 14 10:01:40 2009 (4A5BCAE4)
82540000 8255e000 cdd cdd.dll unavailable (00000000)
82c18000 82c4f000 hal halmacpi.dll Tue Jul 14 09:11:03 2009 (4A5BBF07)
82c4f000 8305f000 nt ntkrpamp.exe Sat Feb 27 18:33:35 2010 (4B88CACF)
8321b000 83293000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 11:06:41 2009 (4A5BDA21)
83293000 832a4000 PSHED PSHED.dll Tue Jul 14 11:09:36 2009 (4A5BDAD0)
832a4000 832ac000 BOOTVID BOOTVID.dll Tue Jul 14 11:04:34 2009 (4A5BD9A2)
832ac000 832ee000 CLFS CLFS.SYS Tue Jul 14 09:11:10 2009 (4A5BBF0E)
832ee000 83399000 CI CI.dll Tue Jul 14 11:09:28 2009 (4A5BDAC8)
83399000 833e1000 ACPI ACPI.sys Tue Jul 14 09:11:11 2009 (4A5BBF0F)
8ba00000 8ba2a000 pci pci.sys Tue Jul 14 09:11:16 2009 (4A5BBF14)
8ba2a000 8ba9b000 Wdf01000 Wdf01000.sys Tue Jul 14 09:11:36 2009 (4A5BBF28)
8ba9b000 8baa9000 WDFLDR WDFLDR.SYS Tue Jul 14 09:11:25 2009 (4A5BBF1D)
8baa9000 8bb9c000 sptd sptd.sys Mon Oct 12 07:54:02 2009 (4AD245EA)
8bb9c000 8bba5000 WMILIB WMILIB.SYS Tue Jul 14 09:11:22 2009 (4A5BBF1A)
8bba5000 8bbcb000 SCSIPORT SCSIPORT.SYS Tue Jul 14 09:45:55 2009 (4A5BC733)
8bbcb000 8bbd3000 msisadrv msisadrv.sys Tue Jul 14 09:11:09 2009 (4A5BBF0D)
8bbd3000 8bbde000 vdrvroot vdrvroot.sys Tue Jul 14 09:46:19 2009 (4A5BC74B)
8bbde000 8bbef000 partmgr partmgr.sys Tue Jul 14 09:11:35 2009 (4A5BBF27)
8bbef000 8bbff000 volmgr volmgr.sys Tue Jul 14 09:11:25 2009 (4A5BBF1D)
8bc00000 8bc21000 srvnet srvnet.sys Tue Dec 08 19:05:06 2009 (4B1E08B2)
8bc31000 8bc7c000 volmgrx volmgrx.sys Tue Jul 14 09:11:41 2009 (4A5BBF2D)
8bc7c000 8bc83000 pciide pciide.sys Tue Jul 14 09:11:19 2009 (4A5BBF17)
8bc83000 8bc91000 PCIIDEX PCIIDEX.SYS Tue Jul 14 09:11:15 2009 (4A5BBF13)
8bc91000 8bca7000 mountmgr mountmgr.sys Tue Jul 14 09:11:27 2009 (4A5BBF1F)
8bca7000 8bcb0000 atapi atapi.sys Tue Jul 14 09:11:15 2009 (4A5BBF13)
8bcb0000 8bcd3000 ataport ataport.SYS Tue Jul 14 09:11:18 2009 (4A5BBF16)
8bcd3000 8bcdc000 amdxata amdxata.sys Wed May 20 03:57:35 2009 (4A12F30F)
8bcdc000 8bd10000 fltmgr fltmgr.sys Tue Jul 14 09:11:13 2009 (4A5BBF11)
8bd10000 8bd21000 fileinfo fileinfo.sys Tue Jul 14 09:21:51 2009 (4A5BC18F)
8bd21000 8bdd8000 ndis ndis.sys Tue Jul 14 09:12:24 2009 (4A5BBF58)
8bdd8000 8bdf2000 WudfPf WudfPf.sys Tue Jul 14 09:50:13 2009 (4A5BC835)
8be00000 8be0e000 pcw pcw.sys Tue Jul 14 09:11:10 2009 (4A5BBF0E)
8be0e000 8be17000 Fs_Rec Fs_Rec.sys Tue Jul 14 09:11:14 2009 (4A5BBF12)
8be2b000 8bf5a000 Ntfs Ntfs.sys Tue Jul 14 09:12:05 2009 (4A5BBF45)
8bf5a000 8bf85000 msrpc msrpc.sys Tue Jul 14 09:11:59 2009 (4A5BBF3F)
8bf85000 8bf98000 ksecdd ksecdd.sys Tue Jul 14 09:11:56 2009 (4A5BBF3C)
8bf98000 8bff5000 cng cng.sys Tue Jul 14 09:32:55 2009 (4A5BC427)
8c016000 8c054000 NETIO NETIO.SYS Tue Jul 14 09:12:35 2009 (4A5BBF63)
8c054000 8c079000 ksecpkg ksecpkg.sys Fri Dec 11 15:04:22 2009 (4B21C4C6)
8c079000 8c1c2000 tcpip tcpip.sys Tue Jul 14 09:13:18 2009 (4A5BBF8E)
8c1c2000 8c1f3000 fwpkclnt fwpkclnt.sys Tue Jul 14 09:12:03 2009 (4A5BBF43)
8c1f3000 8c1fb380 vmstorfl vmstorfl.sys Tue Jul 14 09:28:44 2009 (4A5BC32C)
8c200000 8c217000 tdx tdx.sys Tue Jul 14 09:12:10 2009 (4A5BBF4A)
8c217000 8c222000 TDI TDI.SYS Tue Jul 14 09:12:12 2009 (4A5BBF4C)
8c22e000 8c26d000 volsnap volsnap.sys Tue Jul 14 09:11:34 2009 (4A5BBF26)
8c26d000 8c275000 spldr spldr.sys Tue May 12 02:13:47 2009 (4A084EBB)
8c275000 8c2a2000 rdyboost rdyboost.sys Tue Jul 14 09:22:02 2009 (4A5BC19A)
8c2a2000 8c2b2000 mup mup.sys Tue Jul 14 09:14:14 2009 (4A5BBFC6)
8c2b2000 8c2ba000 hwpolicy hwpolicy.sys Tue Jul 14 09:11:01 2009 (4A5BBF05)
8c2ba000 8c2ec000 fvevol fvevol.sys Sat Sep 26 12:24:21 2009 (4ABD7B55)
8c2ec000 8c2fd000 disk disk.sys Tue Jul 14 09:11:28 2009 (4A5BBF20)
8c2fd000 8c322000 CLASSPNP CLASSPNP.SYS Tue Jul 14 09:11:20 2009 (4A5BBF18)
8c322000 8c33d000 luafv luafv.sys Tue Jul 14 09:15:44 2009 (4A5BC020)
8c33d000 8c350000 rspndr rspndr.sys Tue Jul 14 09:53:20 2009 (4A5BC8F0)
8c354000 8c373000 cdrom cdrom.sys Tue Jul 14 09:11:24 2009 (4A5BBF1C)
8c373000 8c37a000 Null Null.SYS Tue Jul 14 09:11:12 2009 (4A5BBF10)
8c37a000 8c381000 Beep Beep.SYS Tue Jul 14 09:45:00 2009 (4A5BC6FC)
8c381000 8c38d000 vga vga.sys Tue Jul 14 09:25:50 2009 (4A5BC27E)
8c38d000 8c3ae000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 09:25:49 2009 (4A5BC27D)
8c3ae000 8c3bb000 watchdog watchdog.sys Tue Jul 14 09:24:10 2009 (4A5BC21A)
8c3bb000 8c3c3000 RDPCDD RDPCDD.sys Tue Jul 14 10:01:40 2009 (4A5BCAE4)
8c3c3000 8c3cb000 rdpencdd rdpencdd.sys Tue Jul 14 10:01:39 2009 (4A5BCAE3)
8c3cb000 8c3d3000 rdprefmp rdprefmp.sys Tue Jul 14 10:01:41 2009 (4A5BCAE5)
8c3d3000 8c3de000 Msfs Msfs.SYS Tue Jul 14 09:11:26 2009 (4A5BBF1E)
8c3de000 8c3ec000 Npfs Npfs.SYS Tue Jul 14 09:11:31 2009 (4A5BBF23)
8c3ec000 8c3fe000 intelppm intelppm.sys Tue Jul 14 09:11:03 2009 (4A5BBF07)
90c00000 90c0e000 blbdrive blbdrive.sys Tue Jul 14 09:23:04 2009 (4A5BC1D8)
90c0e000 90c2f000 tunnel tunnel.sys Tue Jul 14 09:54:03 2009 (4A5BC91B)
90c2f000 90c39000 usbohci usbohci.sys Tue Jul 14 09:51:14 2009 (4A5BC872)
90c3b000 90c95000 afd afd.sys Tue Jul 14 09:12:34 2009 (4A5BBF62)
90c95000 90cc7000 netbt netbt.sys Tue Jul 14 09:12:18 2009 (4A5BBF52)
90cc7000 90cce000 wfplwf wfplwf.sys Tue Jul 14 09:53:51 2009 (4A5BC90F)
90cce000 90ced000 pacer pacer.sys Tue Jul 14 09:53:58 2009 (4A5BC916)
90ced000 90cfb000 netbios netbios.sys Tue Jul 14 09:53:54 2009 (4A5BC912)
90cfb000 90d0e000 wanarp wanarp.sys Tue Jul 14 09:55:02 2009 (4A5BC956)
90d0e000 90d1e000 termdd termdd.sys Tue Jul 14 10:01:35 2009 (4A5BCADF)
90d1e000 90d5f000 rdbss rdbss.sys Tue Jul 14 09:14:26 2009 (4A5BBFD2)
90d5f000 90d69000 nsiproxy nsiproxy.sys Tue Jul 14 09:12:08 2009 (4A5BBF48)
90d69000 90d73000 mssmbios mssmbios.sys Tue Jul 14 09:19:25 2009 (4A5BC0FD)
90d73000 90d7f000 discache discache.sys Tue Jul 14 09:24:04 2009 (4A5BC214)
90d7f000 90de3000 csc csc.sys Tue Jul 14 09:15:08 2009 (4A5BBFFC)
90de3000 90dfb000 dfsc dfsc.sys Tue Jul 14 09:14:16 2009 (4A5BBFC8)
91600000 9160c000 kbdhid kbdhid.sys Tue Jul 14 09:45:09 2009 (4A5BC705)
9160c000 91617000 mouhid mouhid.sys Tue Jul 14 09:45:08 2009 (4A5BC704)
91617000 9162e000 USBSTOR USBSTOR.SYS Tue Jul 14 09:51:19 2009 (4A5BC877)
91631000 9167c000 USBPORT USBPORT.SYS Tue Jul 14 09:51:13 2009 (4A5BC871)
9167c000 9168b000 usbehci usbehci.sys Sat Oct 24 14:58:55 2009 (4AE27B7F)
9168b000 916b7000 1394ohci 1394ohci.sys Tue Jul 14 09:51:59 2009 (4A5BC89F)
916b7000 916ce000 raspptp raspptp.sys Tue Jul 14 09:54:47 2009 (4A5BC947)
916ce000 916e5000 rassstp rassstp.sys Tue Jul 14 09:54:57 2009 (4A5BC951)
916e5000 916f2000 mouclass mouclass.sys Tue Jul 14 09:11:15 2009 (4A5BBF13)
916f2000 91700000 cledx cledx.sys Tue May 10 04:08:41 2005 (427FA729)
91700000 9170e000 umbus umbus.sys Tue Jul 14 09:51:38 2009 (4A5BC88A)
9170e000 91752000 usbhub usbhub.sys Sat Oct 24 15:00:05 2009 (4AE27BC5)
91752000 91763000 NDProxy NDProxy.SYS Tue Jul 14 09:54:27 2009 (4A5BC933)
91763000 9176d000 Dxapi Dxapi.sys Tue Jul 14 09:25:25 2009 (4A5BC265)
9176d000 9177a000 crashdmp crashdmp.sys Tue Jul 14 09:45:50 2009 (4A5BC72E)
9177a000 91785000 dump_dumpata dump_dumpata.sys Tue Jul 14 09:11:16 2009 (4A5BBF14)
91785000 9178e000 dump_atapi dump_atapi.sys Tue Jul 14 09:11:15 2009 (4A5BBF13)
9178e000 9179f000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 09:12:47 2009 (4A5BBF6F)
9179f000 917aa000 monitor monitor.sys Tue Jul 14 09:25:58 2009 (4A5BC286)
917aa000 917ba000 lltdio lltdio.sys Tue Jul 14 09:53:18 2009 (4A5BC8EE)
917c1000 917d8000 usbccgp usbccgp.sys Tue Jul 14 09:51:31 2009 (4A5BC883)
917d8000 917e3000 hidusb hidusb.sys Tue Jul 14 09:51:04 2009 (4A5BC868)
917e3000 917f6000 HIDCLASS HIDCLASS.SYS Tue Jul 14 09:51:01 2009 (4A5BC865)
917f6000 917fc480 HIDPARSE HIDPARSE.SYS Tue Jul 14 09:50:59 2009 (4A5BC863)
91c00000 91c0d000 CompositeBus CompositeBus.sys Tue Jul 14 09:45:26 2009 (4A5BC716)
91c0d000 91c0e380 swenum swenum.sys Tue Jul 14 09:45:08 2009 (4A5BC704)
91c12000 91d72700 HCW85BDA HCW85BDA.sys Wed Jul 15 06:44:20 2009 (4A5CEE24)
91d73000 91d76000 BdaSup BdaSup.SYS Tue Jul 14 09:51:23 2009 (4A5BC87B)
91d76000 91daa000 ks ks.sys Tue Jul 14 09:45:13 2009 (4A5BC709)
91daa000 91daf280 GEARAspiWDM GEARAspiWDM.sys Mon May 18 22:16:53 2009 (4A1151B5)
91db0000 91df4880 nvmf6232 nvmf6232.sys Fri Jul 31 09:47:55 2009 (4A72312B)
91df5000 91dfe000 wmiacpi wmiacpi.sys Tue Jul 14 09:19:16 2009 (4A5BC0F4)
91dfe000 91dff700 USBD USBD.SYS Tue Jul 14 09:51:05 2009 (4A5BC869)
92200000 9220d000 kbdclass kbdclass.sys Tue Jul 14 09:11:15 2009 (4A5BBF13)
9220e000 92c8bdc0 nvlddmkm nvlddmkm.sys Sat Jul 10 07:15:14 2010 (4C379162)
92c8c000 92c8d040 nvBridge nvBridge.kmd Sat Jul 10 07:10:11 2010 (4C379033)
92c8e000 92d45000 dxgkrnl dxgkrnl.sys Fri Oct 02 10:48:33 2009 (4AC54DE1)
92d45000 92d7e000 dxgmms1 dxgmms1.sys Tue Jul 14 09:25:25 2009 (4A5BC265)
92d7e000 92d86000 serscan serscan.sys Tue Jul 14 10:14:46 2009 (4A5BCDF6)
92d86000 92d98000 AgileVpn AgileVpn.sys Tue Jul 14 09:55:00 2009 (4A5BC954)
92d98000 92db0000 rasl2tp rasl2tp.sys Tue Jul 14 09:54:33 2009 (4A5BC939)
92db0000 92dbb000 ndistapi ndistapi.sys Tue Jul 14 09:54:24 2009 (4A5BC930)
92dbb000 92ddd000 ndiswan ndiswan.sys Tue Jul 14 09:54:34 2009 (4A5BC93A)
92ddd000 92df5000 raspppoe raspppoe.sys Tue Jul 14 09:54:53 2009 (4A5BC94D)
92df5000 92dff000 rdpbus rdpbus.sys Tue Jul 14 10:02:40 2009 (4A5BCB20)
9c80f000 9c894000 HTTP HTTP.sys Tue Jul 14 09:12:53 2009 (4A5BBF75)
9c894000 9c8ad000 bowser bowser.sys Tue Jul 14 09:14:21 2009 (4A5BBFCD)
9c8ad000 9c8bf000 mpsdrv mpsdrv.sys Tue Jul 14 09:52:52 2009 (4A5BC8D4)
9c8bf000 9c8e2000 mrxsmb mrxsmb.sys Sat Feb 27 18:32:02 2010 (4B88CA72)
9c8e2000 9c91d000 mrxsmb10 mrxsmb10.sys Sat Feb 27 18:32:21 2010 (4B88CA85)
9c91d000 9c938000 mrxsmb20 mrxsmb20.sys Sat Feb 27 18:32:11 2010 (4B88CA7B)
9c950000 9c9e7000 peauth peauth.sys Tue Jul 14 10:35:44 2009 (4A5BD2E0)
9c9e7000 9c9f1000 secdrv secdrv.SYS Wed Sep 13 23:18:32 2006 (45080528)
9c9f1000 9c9fe000 tcpipreg tcpipreg.sys Tue Jul 14 09:54:14 2009 (4A5BC926)
a0c02000 a0c51000 srv2 srv2.sys Tue Jul 14 09:14:52 2009 (4A5BBFEC)
a0c51000 a0ca2000 srv srv.sys Tue Dec 08 19:05:37 2009 (4B1E08D1)
a0ca2000 a0cc2480 WUDFRd WUDFRd.sys Tue Jul 14 09:50:44 2009 (4A5BC854)
a0cc3000 a0d9ea80 ksaud ksaud.sys Tue Dec 15 13:22:59 2009 (4B26F303)
a0d9f000 a0db8000 drmk drmk.sys Tue Jul 14 10:36:05 2009 (4A5BD2F5)
beaa3000 beaac000 asyncmac asyncmac.sys Tue Jul 14 09:54:46 2009 (4A5BC946)
beaac000 beaad580 MSPQM MSPQM.sys Tue Jul 14 09:45:07 2009 (4A5BC703)
beaae000 beaaf700 MSPCLOCK MSPCLOCK.sys Tue Jul 14 09:45:08 2009 (4A5BC704)
Unloaded modules:
bea39000 beaa3000 spsys.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0006A000
9c938000 9c950000 parport.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00018000
91c0f000 91c11000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00002000
917aa000 917c1000 usbccgp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00017000
912eb000 91304000 drmk.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00019000
9120f000 912eb000 ksaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 000DC000
8c322000 8c32f000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000D000
8c32f000 8c33a000 dump_ataport
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000B000
8c33a000 8c343000 dump_atapi.s
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00009000
8c343000 8c354000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00011000

hello,
i'm just wondering how i can get support for this problem? I want to use my itouch to listen to music and i can't run itunes because it crashes my PC with the above mentioned memory dump. Does apple support look at these forums? I am so disappointed that I went out buying a new motherboard and still get the same problem when the problem all along was itunes!
is there a solution for this problem? can someone help? should i get my money back and buy instead another music thing to listen to my music? I have had the itouch for about 4 months now is it too late to return and request for money back? I'd rather someone from support provide a solution...

Similar Messages

  • Tecra M9-136 - BSOD during Vista SP2 update

    Tecra M9-136 asked this morning to update to Vista SP2 and during the process the BSOD 0x0000007E arrived. Restarted in Safe Mode and the installer continued and then finally reported that the update had failed - and reverted to SP1. This took most of the morning.
    It will start in Safe Mode but on a normal boot-up, Vista SP1 gets through the fingerprint recognition and then fails with the same BSOD (it doesn't get as far as displaying the desktop).
    The laptop has BIOS level 1.80. I've tried in Safe mode to install 1.90 but it tells me that the battery has insufficient charge and the power adapter isn't attached. Both untrue.
    Stuck - need advice. Could this be a hard fault? Can't see how I can update anything if it's a soft fault.
    thanks

    The message with the BSOD mentioned checking BIOS and driver versions. Anyway, no change made to that.,
    I tried System Restore but the only available restore point was the SP2 installation. I thought Vista was supposed to save a restore point every 24 hours even if nothing new had been installed.
    I've now found in System Information / Windows Error Reporting several messages like this:
    28/09/2009 12:08 Windows Error Reporting Fault bucket 0x7E_NULL_IP_DRVNDDM+57bd, type 0
Event Name: BlueScreen
Response: None
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\Mini0928 09-04.dmp
C:\Users\me\AppData\Local\Te mp\WER-75660-0.sysdata.xml
C:\Users\me\AppData\L ocal\Temp\WER7D78.tmp.version.txt
& #x000d;
These files may be available here:
C:\Users\me\AppData\Local\Mic rosoft\Windows\WER\ReportArchive\Report06d1c4b5

  • Pavilion Elite e9180f freezes, crashes, BSOD

    I am one of the many unhappy customers who bought this piece of junk (Pavilion Elite e9180f) and waited too long to return it because in my naivete, I thought it was some kind of simple software issue.  Nope!  It's definitely something wrong with the hardware, because the freezes and crashes have been happening since day 1, right when I took the thing out of the box.
    Yeah, the system is fast and runs Windows Vista great, when it's actually WORKING, which is usually only guaranteed for about the first 5 minutes after you power the system on and boot windows.  After that, it's just buying time before it crashes again.  Forget trying to get anything done on this computer.  Forget about asking this PC to play a video or music file without the files "stuttering" during playback.  Even my 7 year old Sony Vaio which is running XP can handle playing an MP3 file without stuttering and crashing!
    Like everyone else, the freezes and crashes happen either one of two ways:
    1) The machine begins to "stutter", stutter more, then freeze/crash.  When I say stutter, I mean I move the mouse, the pointer graphic will hesitate on the screen and lag behind.  If you start to play a video or music file, this manifests in an audible "stutter".  The stuttering gets worse and worse as minutes pass until eventually it freezes for good, blasting that 1/50th second moment of audio into infinity.  You have to reboot immediately if you don't want to go deaf or be driven mad.
    2)  I will be doing nothing at the time (example, I close all programs out and leave Windows sitting on the main desktop screen), I'll walk out of the room for a minute, then come back and find I can't move the mouse. This system will often lock-up without any warning!
    Sometimes I'll get a BSOD or error screen, sometimes I won't (in which case your only option is to do a cold re-boot.)  When I do get the BSOD, the error is ALWAYS the "did not get a response from the secondary processor" yada yada.  I wish HP would just admit they shipped this model out with a bad processor/motherboard/whatever and do an official recall.  I have owned PCs for the last 13 years and this is the worst and most consistently disappointing experience I have ever had.
    What is the hardware issue?  Which part is the lemon part?  The motherboard?  The processor?  The BSODs seem to indicate a bad processor.  I do have the Pegatron Truckee version 1.03 motherboard.  Is that the problem?
    P.S.  I have contacted HP on many occasions about this, literally stayed on the phone for hours with "customer support" (according to one HP rep, 80% of their customer service reps are based outside of the United States...good luck getting any "technical" help from them) to no avail.  I did talk to one nice tech support guy in Canada who said "it sounds like your unit has a bad processor", so he had HP send me a box to ship my unit to their repair center so they can replace the processor.  However, I have also had HP reps tell me it could be anything from the memory to the hard drive.  Multiple HP reps claimed to me that they have "received no complaints" about this system.  One guy told me he "thought he got an email last week" regarding "something" about the system, but couldn't remember what it was and he put me on hold while he searched for the email.  He never found it.  What a joke.
    EDIT:  Just to clarify, the crashing issue has been happening since day one, but initially I thought it was an issue with Vista.  I had never owned or used Vista before, so I thought maybe Vista was just unstable.  Nope.  I know several people who own Vista and have never experienced these issues.  I have downloaded every update from Microsoft/Windows Update.  I have upgraded to Vista SP2 with all the latest drivers and software for all of my hardware.  No luck.  It is definitely a hardware issue.  Thank god HP's warranty is good for 1 year (I bought my Elite in July).
    Message Edited by Doonyman on 09-24-2009 02:58 AM

    Unfortunately I have to add my disastrous encounter with HP's E9180F a true lemon HP is selling. I must take some responsibility for not carefully researching this model before I purchased, but I trusted the HP name and got stung- big time.
    The scoundrel  :
    HP and its Pavilion Elite e9180f
    Windows 7 64bit
    motherboard - Pegatron  Truckee ver 1.03
    BIOS ver  5.22Intel Core i7 920 @ 2.67GHz
    Memory 9206 MB Ram   
    As so many others have reported my HP E9180f started locking up and going to BSOD right out of the box. My first freeze-up came when I was doing the Windows update process. At first I didn't think much about it but I started getting random freezes a couple time a day. At that point I went online to see if others had experienced the same problem and perhaps had a fix. What I found was very troubling;  I found extensive documentation describing my exact problems and what was really horrifying was the reports of how ridiculous HP's help services were treating people with the problem. At first I didn't totally believe what I was reading on HP's own customer forum; I do now.
    ·         I've went through the total recovery process three times now, HP techs have spent hours remotely running my computer, (yes it did lock up on them to)
    ·         I had to upgraded the BIOS. (HP tech tried, said he had, but he hadn't)
    ·         I was directed to clear the BIOS (luckily for me I had the tools
    ·         Updated all drivers again and again.
    ·         Next I was asked to remove the video card, memory, and motherboard power cable and reseat them. I declined because I didn't want to give HP any reason to void my HP 2 year House Call Care Pack which covers this unit. When I invited HP to send a service tech out to perform these tasks, they said that house call only covers part replacement, we weren't replacing a part. I couldn't believe what I was told. Are you feeling my frustration?  
    Keep in mind that each time HP requests that I make changes, they then ask me to test the system, which I did and each time with the same result, BSOD
    I'm heading into my fifth week of working with HP to fix this problem. and I still haven't even been able to get my case moved up to a senior case manager, what a joke HP's help process is.
     One conversation I loved was;
    HP tech: "I'll have a senior case manager call you within 24 hours."
    Skeptical me: "What should I do if I don't get a call?"
    Silence, no response.
    Me again: "What should I do if I don't get a call?"
    HP tech: "That's an impossibility."
    Guess what? The impossibility became reality (I bet you guessed) .
    HP's last stall tactic was to have me fax them my proof of purchase and invoice and call back in 24 hours. Where have I heard that before? Apparently nothing can go forward until they receive it. So I faxed them the stuff within 10 minutes, and when I called back 24 hours later, guess what, you're right it wasn't on their system yet. I asked couldn't I be escalated to a senior case manager  (it's apparent that only a senior case manager can do anything). "No," was the tech's reply, "call back again later".
    Please if anyone out there knows the secrete to getting a senior case manager, or an HP tech support number here in the U.S. so I can get this thing fixed I'd love to know it.
    Fast becoming HP never again.      

  • BSOD K8N2 AMD X2 3800

    Noticed problem accessing E drive = error message
    tried defrag, chkdsk /f and couldn't complete
    nothing before today stored in system restore
    started getting BSOD IRQ_EQUAL_TO_NOT_LESS_THAN Stop 0x000000000xA
    tried to start copying files from E with bsod after a 1-2 min of copy process
    ran Hitachi drive diag and drive failed in basic and advanced mode
    ran ontrack drive diag and drive would stop after a few min on the read test
    so...thought drive was bad...copied what I could from drive and returned for warranty replacement
    installed and formatted new SATA drive...copied files to E
    now getting BSOD on copying all files
    cannot complete virus check on any drive... bsod on all drive access after a few minutes
    updated BIOS and mobo drivers
    no change... did Win Repair
    now computer really runs like crap...getting fail on spoolsv.exe
    booted into safe mode and did virus check ccleaner and spybot check
    ??? should I fix ccleaner registry problems?
    didn't BSOD during safe mode
    went back to normal mode, same spoolsv.exe error
    kept saying I need to update to sp2, but hangs during 'finishing install'
    tried running sp3 candidate...hangs
    what would you do?
    should I give up and try to upgrade to Vista and hope it fixes everything?

    Seems like your OS files have gotten corrupted - from Command Prompt try SFC /SCANNOW with the OS CD-ROM in a drive.  You also need to calm down and run some basic diagnostics, e.g. memtest86+ like someone else said and then run WDC diags on your remaining drives and a full Windows scan of at least the boot drive with CHKDSK /R or "Scan for and attempt recovery of bad sectors" with the Windows scanner.
    Which nForce3 driver pack are you using - the last from nVidia was 5.10 (5.11 is bad so do not use).  Where did you DL the SATA/RAID drivers?  If from MSI and it's the version with V5.34 NVATABUS.SYS I wouldn't use that - the 5.10 pack SATA is OK but the best SATA/IDE driver, if you must, is the V4.79 SATA-IDE which is only available as part of an aborted attempt at a unified driver pack, 6.37Beta, by nVidia... available here http://downloads.guru3d.com/nForce-6.37-Beta-Drivers-download-971.html BUT use only the drivers in the IDE folder, which you'd have to install manually.  You could also do a custom remix, like I have, by replacing the IDE folders in the 5.10 pack with the ones from the 6.37Beta pack.
    BTW forget about Vista with a nForce3 mbrd - nVidia has removed all "compatibility" notices and their official stance is that it(Vista+nForce3) does not work with a dual-core CPU and they will not be doing drivers.

  • Usb 6501 unresponsive causing BSOD(Blue Screen Error)

    There are a lot posts about the same issue but mine is a little peculiar so i decided to post it.
    I am using two usb DAQ in the same pc(usb-6501, usb-6001), connected to the usb port on the back. The usb-6501 is used to obtain digital inputs from read switches, Sensors through an ssr. The usb-6001 is used to control 2 double valve solenoid, 1 dc motor, 2 indicator lamps. usb-6001 is also used to read analog values of current(using hall effect sensor) and voltage(using potentiometer).
    At first i was facing problems with the usb-6001(the usb-6501 was working fine at this point) resetting during operation accompanied by BSOD. Then i learned it was due to my relay, which requires 30 mA of current to switch so i used the ULN2003a to interface the usb-6001 with the relays and after that the application was running perfectly for 4 days.
    Now the usb-6501 is having the same problem and when i perform "Self Test" from NI MAX it shows "Error Code:50405" and i am able to reset the device from NI MAX only sometimes, other times i would have to unplug the USB device then plug it back in. As the application is used for an automated test rig the customer is frustrated by this problem. Once the card becomes unresponsive(or after the card is reset) BSOD occours.
    I have checked all the device drivers and OS for any errors but they are fine. i have even tried changing the ram to solve the BSOD with no use.
    System Details:
    Windows 7 SP1
    NI MAX 14.0
    power saving is disabled 
    I have attached the latest mini dump files as they might help in finding out the reason behind this problem(File extensions changed for the purpouse of uploading).
    I need to know: Is there any permanent solution for this problem? and what is the reason for this problem.
    Attachments:
    060115-12480-01.txt ‏315 KB
    053015-12324-01.txt ‏315 KB
    052615-17440-01.txt ‏315 KB

    Additional info : i did an analysis of the dump files and this is the result
    0: kd> !analyze -v
    * Bugcheck Analysis *
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff88009fe10b1, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800657922e, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c30e8
    fffff88009fe10b1
    CURRENT_IRQL: 2
    FAULTING_IP:
    nifslk+822e
    fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    BUGCHECK_STR: 0xD1
    PROCESS_NAME: System
    TRAP_FRAME: fffff80000b9c6b0 -- (.trap 0xfffff80000b9c6b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88009fe10b2 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffff80000b9c8e0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800657922e rsp=fffff80000b9c840 rbp=fffff88009fe10b1
    r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    nifslk+0x822e:
    fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1] ds:c8e0:fffff880`09fe10b1=??
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff80003091be9 to fffff80003092640
    STACK_TEXT:
    fffff800`00b9c568 fffff800`03091be9 : 00000000`0000000a fffff880`09fe10b1 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b9c570 fffff800`03090860 : fffffa80`06adc250 fffffa80`05c3a060 fffffa80`06adc250 00000000`0000ffff : nt!KiBugCheckDispatch+0x69
    fffff800`00b9c6b0 fffff880`0657922e : fffff880`05d47468 fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 : nt!KiPageFault+0x260
    fffff800`00b9c840 fffff880`05d47468 : fffff880`01d91f90 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 : nifslk+0x822e
    fffff800`00b9c848 fffff880`01d91f90 : 00000000`00000000 fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 : 0xfffff880`05d47468
    fffff800`00b9c850 00000000`00000000 : fffff880`09fe0770 fffff880`09fe17a0 fffff880`09fe10b1 fffff800`00b9c8e0 : nipalk+0x75f90
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nifslk+822e
    fffff880`0657922e 0fb650ff movzx edx,byte ptr [rax-1]
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: nifslk+822e
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nifslk
    IMAGE_NAME: nifslk.dll
    DEBUG_FLR_IMAGE_TIMESTAMP: 51f2daeb
    FAILURE_BUCKET_ID: X64_0xD1_nifslk+822e
    BUCKET_ID: X64_0xD1_nifslk+822e
    Can anyone help me with what this means?

  • Win XP BSOD while capture video on MSI GF FX 5900XT-VTD128

    Hello.
    I have such a problem. While capture video (overlay mode, 720x576) very
    often (but not always) Windows XP crashes on BSOD with the following error:
    DRIVER_IRQL_NOT_LESS_OR_EQUAL
    STOP: 0x000000d1 (0xF0504000, 0x00000002, 0x00000001, 0xF7A2CE57)
    nv4_mini.sys - address F7A2CE57 base at F7A1A000, datestamp 4061d74b.
        My system configuration is:
    Hardware: MB Epox EP-8RDA3I (latest BIOS version), CPU AMD Athlon XP 2400+,
    RAM DDR PC3200 512 MB dual channel (Kingston), Video MSI GeForce FX 5900
    XT-VTD 128 (VIVO, Philips SAA 7114). NO overclocking!
    Software: Windows XP Prof SP1, DirectX v.9.0.b, Nvidia Nforce driver v.4.24
    WHQL, Nvidia ForceWare driver v.56.72 WHQL (default settings), MSI WDM capture driver v.3.08 (late). Capture software: VirtualDUB, iuVCR and any other.
        What anyone will advise me?
        Thank You.
        Best regards, Dmitry.

    61.21 driver is a beta driver. its not 100%. wait until they release a full working driver. it will be released on http://www.nvidia.com.

  • MSI K7N2 Delta-ILSR (MS-6570) BSOD problems grrr

    I recently purchased this board and although it is an awesome product, I'm having a problem with BSOD's when I play a game for a certain period of time
    Specs:
    MSI K7N2 Delta-ILSR  (7.6 BIOS)
    AMD Athlon XP 2800+ Barton
    512MB (2x256MB) Samsung PC-2700 DDR memory (2.5-3-3-6 1T)
    MSI 128MB GeForce4 Ti 4200 (4X AGP)
    NVIDIA nForce on-board sound
    Western Digital 80GB drive w/ 8MB cache
    MSI X48 CD/CD-RW/DVD combo drive
    Windows XP Professional SP1
    PSU:
    Turbolink 420watt (came with case)
    +3.3V is 28A
    +5V is 40A
    +12V is 18A
    So what happens is I get a STOP error during the game that shows the kmixer.sys driver as the culprit. Sometimes it's accompanied by PAGE_FAULT_IN_NON_PAGED_AREA too. I read somewhere that kmixer.sys has to do with windows audio and that it's a 3rd party driver issue or a memory issue. I'm using the latest NVIDIA 3.13 nForce platform drivers. I ran Memtest lastnight for 12 hours straight and 0 errors. I'm thinking the memory may not be compatible with the board nor dual channel, is this possible? I have also tried several different drivers for both video and chipset including MSI's own and I still get the kmixer.sys BSOD when playing games. My previous motherboard was an MSI KT3 Ultra2-R (MS-6380E) which I had no issues with. Any help would be greatly appreciated. Thank you in advance.
    --Update--
    I just tried to play a game with audio disabled and it crashed this time with DRIVER_IRQL_NOT_LESS_OR_EQUAL with nv4_mini.sys as the problem. My IRQ table shows some sharing, but device manager shows no conflicts.

    Ok I tried running the DTM-CB3 module which is nForce2 approved at 3-4-4-11 2T timings and experienced the same result even at 2.6 and 2.7v. I tried both in dual-channel and same thing happened. However, I downloaded a program called Prime95 and ran the CPU torture test and the system returned a fatal error within the first few minutes. CPU Temp was at 57 C and the warning beep (set to 60C though) sounded intermittentley which is strange. I let it cool down then ran the torture test again and about 5min. later the system either seized completely or the program crashed. IE has also crashed randomly on me. I did this several times, before trying a different FSB/DRAM ratio. So I left the system at 200 FSB and used a 6:5 ratio so my memory was running at DDR333 and processor was a 3200+. I ran Prime95 again and the system locked up just as it did the other times.  So after I did this a few times with consistent results. I went back and set the FSB to 166 and tried a 5:6 ratio so the memory was DDR400 and processor was the normal 2800+. I ran it again and to my suprise it passed all the tests and after an hour of this, I tried a game and that was perfectly fine as well. I checked the temps and CPU was only 45 C this time. So I'm thinking the processor can't handle anything above 50C or it's just plain overheating. I ordered a Thermaltake Silent Boost HSF today which is tested up to 3400+ so this should fix my problem. If not, then I'm going to replace the memory with a 512MB Geil PC3200 golden dragon dual-channel kit.

  • BSOD / Lock-ups with new Q9550 in P965 Platinum

    MSI P965 Platinum Mobo
    E6700 CPU, recently upgraded to Q9550
    Zalman Cu heat sink + fan.
    4GB Corsair 6400 C4 (4-4-4-12 800 MHz)
    MSI 8800 GTX graphics
    Auzentech Meridian sound
    2 x 36GB Raptors RAID 0 (System)
    2 x 250 GB Western Digital Caviar WD2500KS RAID 0 (Data)
    Corsair HX620W PSU
    All drives attached to the ICH8R Intel RAID controller.
    BIOS: 1.8 (latest)
    Vista Ultimate 32 bit SP1 + latest patches
    Intel Matrix Storage Manager v8.6
    Hi all,
    I have run with the above hardware specification since Jan 2007 without experiencing any hardware problems at all. Two weeks ago I upgraded the CPU from an E6700 dual-core to a Q9550 quad. I was a little concerned about doing this, because the P965 supports a max FSB of 1066 and the Q9550 is rated at 1333. In any case, I Googled around and found that some flavours of the Q9550 had been tested on my mobo (http://www.cpu-upgrade.com/mb-MSI/P965_Platinum_(MS-238).html) and also MSI list the Q9550 stepping C1 as being compatible so I took the leap.
    Early indications were good - Vista detected the new chip and I rebooted when prompted. However, in the space of two weeks I have experienced  around one or two BSODs per day STOP 101 or 124 codes. Hmm!
    I have switched back to my trusty E6700 chip and the system is then as solid as a rock. I see 3 possibilities here:
    1.The Mobo website (MSI P965) lists the Q9550 stepping type C1 as being compatible. There is no mention of E0 or C0 which seem to be the other two variants. I have no idea which stepping type mine is as the product numbers for the Q9550 chips are all the same (EU80569PJ073N or BX80569Q9550) regardless of whether it is a C0, C1 or E0 stepping. Is there any way to tell which on I have - I tried with CPU-Z but didn't spot the stepping type? In any case, could this be the problem or am I off-base?
    2. It's possible I have a faulty chip. How likely is this do you think? I could ask for a swap with Novatech but could be back in the same boat, and they will reject the return unless it is 'proven faulty'.
    3. I need to mod the clocking on my rig to support the Q9550. If so, can anyone advise on what I should do?
    I doubt the problem is caused by an OS factor as I ran some tested in an XP pre-boot environmet and still got the lock-ups.
    What should I do? i don't really want to ebay the chip at say a £50 loss if i can help it.
    Many thanks in advance.

    Quote
    I have no idea which stepping type mine is as the product numbers for the Q9550 chips are all the same (EU80569PJ073N or BX80569Q9550) regardless of whether it is a C0, C1 or E0 stepping.
    No, the OEM Order Code is different, and the sSpec Number also.
    Have a look at these links
    Q9550=SLAWQ=C1--> http://processorfinder.intel.com/details.aspx?sSpec=SLAWQ
    Q9550=SLB8V=E0 --> http://processorfinder.intel.com/details.aspx?sSpec=SLB8V

  • BSODs lock ups and flakey firewire port - help ??

    Okay I'm really getting fustrated over this laptop it's nearly 2 weeks old
    and I've already had 2 BSODs the odd crash where the mouse moves but nothing
    else around it works so a forced reboot was needed.
    Today I had a BSOD all i did was run some untility from the taskbar called
    network doctor or something.
    error message:
    PAGE_FAULT_IN_NONPAGED_AREA (no address information supplied)
    STOP: 0x00000000050
    someone suggested that I may have a memory problem or my page file is corrupt.
    anyway here's a run down on what i've installed so far with my laptop.
    - Installed all XP security updates and patches
    - Installed Firefox 1.0.1 (don't trust IE6.0 yet)
    - Installed iriver download manager (my mp3 player)
    - Installed winamp 2.0 and Creative Notebook Cam.
    I've ran a forced boot chkdsk and no problems found.
    Another thing I found interesting was nearly everytime my laptop bsods I usually
    find a a yellow marker over my 1394 net adapter (firewire port) in device mananger
    ("cannot start device") don't know if that's related or not. A reboot seems to
    clear this yellow marker but I am rather unhappy BSODs are no laughing matter.
    My laptop model is the Equium A60-181 (Intel P4 HT 3.2Ghz 512Mb RAM)
    Anyone else had similar problems or recommendations?
    cheers,
    Richard S.

    Hi Richard
    I understand you that you are unhappy with this all problems but there can be a lot of reasons for that. In my opinion this can happened because of some unnecessary update or some drivers installed by third-party software that you installed on your notebook.
    Please reinstall OS using Recovery CD. After firs boot check in device manager if there is some hardware problem. If not you than try to start Config free (Connectivity doctor) and some other Toshiba tools to check if everything is ok.
    If everything is ok try to install SP2 if you dont have it on your machine (just SP2 and not separately updates and patches). I am not sure but some of A60 are delivered with SP2.
    Install all your programs slowly and follow carefully what happened after every step that you done.

  • Audigy 2 on Neo2 Platinum causes LOCK UPs/BSODs!!! Help!

    I have a videocard with a HUGE, I mean HUGE custom CPU heatsink attached to it.  This leaves me only ONE slot available for my Audigy 2.  And that slot is the last slot 5, orange color.  
    Its the ONLY ONE AVAILABLE.  I read on these forums about some incompatibility of Audigy 2 with MSI Neo2 Platinum.  Thats what I have.  I tried several later and older BIOSes including the official one and the latest beta one.
    Still, when I play UT2004 or some other games that demand EAX/Hardware 3D sound - I get a dark blue BSOD without a message (its like a non-WinXP BSOD, its a hardware BSOD as I call it, dark blue color).  It comes with a sqeeking sound.  I have to restart my PC afterwards.  
    It happens after 3-4 minutes of playing.
    When I REMOVE the soundcard - everything is fine, NO BSOD.  
    I tried different Audigy 2 drivers, but they all give the same result.  This did not happen on my old ASUS A7N8X-Deluxe 2.0, and the soundcard was in PCI Slot 5 as well.  I tried to format, and etc., - same thing if the soundcard is in the PCI slot!  
    I have PCI lock ENABLED (AGP set to 67Mhz, and PCI LOCK DETECTION set to ENABLED).
    How do I fix this problem?

    Quote
    Originally posted by MonarchX
    I have PCI lock ENABLED (AGP set to 67Mhz, and PCI LOCK DETECTION set to ENABLED).
    When you said that you have PCI lock enabled and PCI lock detection enabled, were you talking about the same thing?  If not, where in the BIOS is the PCI lock? I could only find PCI Lock Detection.

  • Lock up, BSOD, freezing, ad infinitum.

    Compaq SR5333WM Desktop
    Windows 7 (almost installed)
    last known error: STOP: Error 0x000008e
    No changes made before the error. tried to reinstall windows, failed. got a new hard drive and tried to install windows, failed. memtest checks out ok. cannot get to the dump files due to not even getting past the BIOS. Restarted BIOS, failed.
    The desktop freezes and usually an image displayed on the screen will repeat, for lack of a better discription. I searched the error code when it BSOD'd on me but it didn't say anything about a video card error. I'm at the end of my techical knowledge and need a hand for anyone who has the time to do so. Thanks for reading.

    Edric, welcome to the forum.
    The symptoms that you describe sound like a failed/ing power supply unit (PSU).  Here is a guide to help you troubleshoot the problem.  I suggest disconnecting any unnecessary components before testing.
    Please click "Accept as Solution" if your problem is solved.
    Signature:
    HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
    HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
    HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
    HP Photosmart 7520 AIO
    ++++++++++++++++++
    **Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
    Intelligence is God given; Wisdom is the sum of our mistakes!
    I am not an HP employee.

  • K8N Neo4 Platinum random lock-ups and BSOD

    I built a new PC about 3 months ago and from day 1 it has always locked up / frozen at random intervals. Sometimes it also BSOD's with a Machine Check Exception. Seems to lock up / freeze more often when have multifple windows open eg. Multiple IE running but really is random. I have replaced the Mobo and Ram but keep having the same issues. Have tried a clean install but no luck either. Did a clean install on an old IDE HDD and seemed fine but it did not have all of the software that I run on the SATA drive. Thinking the SATA drive may be the issue? Please Help!!!
    System is as follows:
    MSI K8N Neo4 Platinum [Bios 1.D]
    AMD Athlon 64 X2 3800+ DC [AMD Drivers]
    2 x Kingston 1024Mb ram [Dual Channel]
    Nvidia 6800 Ultra [Latest Drivers 91.31]
    Thermaltake Purepower 460W PSU +3.3V 30A, +5V 30A +12V 15A
    Western Digital 200G SATA II HDD [SATA Port 5 i think]
    1 x LG DVD +-R/RW [IDE Master] IDE port closest to edge of Mobo
    1 x LG CDR/RW [IDE Slave]
    MS XP Home SP2

    Quote from: davePC on 09-August-06, 09:06:44
    Did a clean install on an old IDE HDD and seemed fine but it did not have all of the software that I run on the SATA drive. Thinking the SATA drive may be the issue? Please Help!!!
    Seemed fine?
    There isn't really be any difference between an IDE drive and a sata.
    Except that the sata drive needs some drivers as your installing the os.
    Check your ram timings in bios but likely it's your psu.
    Which components are on which rail?
    The ones that use the +12v are your cpu,cdrom,dvdrom and graphics card.
    Try disconnecting both roms and see if it improves things?

  • Disgusted with HP Elite m9280a constant/random freezes, lock ups, BSOD, black screen

    constant/random freezes, lock ups, BSOD, black screen.
    I have been trying to trouble shoot this PC for almost a day now. weird problems like when 3 sticks of memory is present it wil not boot but it will boot on 1 and on 2 sticks will have hangs?
    disappointed tot the max... u think HP TOTAL CARE  - u pay extra thinking u are going to get a decent system...
    i have run diagnostics on all major components... still no luck
    someone please help - i have never spent sooo much time trying to repair a pc

    Try this bootable memory diagnostic tool: 
    Download memtest86 iso file and burn it to disk using Imgburn.
    HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
    HP Photosmart Premium C309G, HP Photosmart 6520
    HP Touchpad, HP Chromebook 11
    Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
    Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
    Windows 7/8 UEFI/Legacy mode, MBR/GPT

  • Windows 8.1 kernel_data_inpage_error BSOD

    Hey there, had a windows update last night when i logged off, did the usual update and shut down, and it carried on this morning when i switched my PC on.
    Since then i have had 3 lock ups of sorts, everything stops responding but the mouse still moves, only way was to hold the power button down on my tower and restart that way.
    I then had a BSOD with windows 8.1 kernel_data_inpage_error, iv done a ram check/test and all was fine, scanned/checked my C drive, all is fine, however, doing the /scannow it is saying found corrupt files but was unable to fix some,  details in the
    CBS log iv attached the log, any help please? :)
    http://1drv.ms/1tp6fxb
    I also looked for a mini dump file but i couldnt see/find the minid ump folder

     We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers
    were loaded, and what was responsible.  
    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask
    If you are using Blue screen view, who crashed, or a similar application, don't.  They are wrong at least as often as they are correct
    Wanikiya and Dyami--Team Zigzag

  • [K8N Neo2 Platinum] BSOD - have had enough of them!

    My first K8N Neo2 was a DAO - no current to the PCI slots. Got a new one as replacement, seemed to work fine. "Seemed", indeed.
    I've had plenty of sudden resets and BSODs.
    I've seen:
    STOP 0x000000FC (no error or driver named)
    STOP 0x000000EA in ATI2DVAG
    STOP 0x00000050, PAGE_FAULT_IN_NONPAGED_AREA in win32k.sys (also saw some 0x00000050 without the PAGE_FAULT error or driver name)
    STOP 0x0000008E
    Just yesterday I had two BSODs, just when surfing the internet.
    System - Athlon 64 3200+ (boxed), Tagan 380W PSU with 22A on the +12V rail, ATi Radeon X800 Pro, Creative Labs Audigy 2ZS, Promise Ultra133TX2, 3x Maxtor 7200rpm HD, 2x GEiL 512mb PC3500 DDR-RAM (running at PC3200), Lite-On DVD+RW and Lite-On CD+RW.
    Please note that my videocard, PCI cards and harddrives worked perfectly in my previous system (Soltek SL-75FRN2-L, nForce2 Ultra400 chipset with a Enermax 350W PSU). I've already tried running without the PCI cards.
    Voltages very near to specs, according to Corecenter -- 3.33V on the +3.3V rail, 5.05V on the +5V rail and 11.96V on the +12V rail. That's at this specific moment, under high stress (due to encoding a DVD to XVid).
    Memtest86+ : 30 passes, no errors.
    3DMark 2005: one full benchmark pass, no errors or graphical artifacts.
    Seti@Home: can run for days without any problems.
    I have noticed reproducable problems: encoding a DVD to XVid with GordianKnot and encoding DVD9 to DVD5 with DVD Rebuilder. Both resulted in me waking up and finding the login screen of Windows XP (SP2, latest Athlon 64 CPU driver, latest drivers for everything else).
    What could be causing this?
    Currently I'm running the system with only one stick of RAM, to determine if it's some kind of dual-channel problem or if Memtest86+ somehow didn't find an error while actually something was wrong...
    I should note that somewhere in the past week my floppy drive controller must have died, it was working last week and not anymore at the moment. It's recognized by Windows, but no matter which floppydrive I attach it won't work. I've also tried swapping floppy drive cables and even the powerconnector. All of no avail.
    So what's most likely to be the problem? Faulty motherboard? Faulty PSU? Faulty videocard? Or perhaps even a faulty CPU?

    Quote from: WaltC on 21-February-05, 21:29:11
    My first (and only) K8N Neo2P has consistently worked well from the start--with the exception of some blue-screen STOP and MACHINE CHECK errors which I no longer have any problem with after doing a couple of things:
    (1) At first I couldn't even boot into WinXP (locked up every time with a MACHINE CHECK BSOD) unless I entered the bios and turned off UDMA in the IDE config and set everything connected to the onboard IDE to PIO4 manually.  After that, I could boot into Windows without error--but of course without UDMA which was unsatisfactory, too.
    (2) Next thing I did was to update the firmware in both my optical drives after being reminded about the need to look at that by Glenn, a moderator in this forum.  Well, that fixed the UDMA bootup problem I'd been having as all of my drives would correctly boot as UDMA devices with IDE bios config set to "auto," and I could at last correctly boot into WinXP without error.  But then I noticed another problem...
    (3)For some reason, about 60% of the time while booting the optical drive attached to IDE 1 as slave was not being detected by the bios as anything except "NONE", and so when Windows would detect it in software at boot it would automatically incorrectly configure it as a PIO4 drive.  Fixing that problem was easy once I'd guessed the cause--replacing the orange MSI IDE cable that came with the board with another UDMA IDE cable immediately and permanently solved the detection problem I'd been having with the slave IDE optical drive.
    Of course, now I wonder if the entire IDE configuration problems I'd had weren't caused by the faulty orange rounded MSI IDE cable that shipped with my motherboard--such that possibly all I need have done from the start was replace the IDE cable...  But, of course, it didn't hurt to  update my optical drive firmware anyway.
    Anyway--after these steps I've had no more trouble with the Neo2P in any capacity.  Your solution may not lie here, but I thought you should know about mine in case it might help you sort this out.
    Thanks for your reply. However, I haven't used MSI's cables at all. I used the ones from my previous system...
    Besides, I haven't had any issues with detection of the IDE-devices.
    Edit: Update - I'm currently running with only one DIMM (in slot 1) instead of two DIMMs (slot 1 and 2, also tried slot 3 and 4). An encode from DVD to XVid would cause a reset previously, now with only one DIMM the encode completed succesfully.
    By no means is this a 100% assurance that the RAM was causing the problems, but it sure looks like it. This night I'll try an encode from DVD9 to DVD5 using DVD Rebuilder, previously that wouldn't complete succesfully either. If it does now, I'm quite sure the RAM was causing the problems.

Maybe you are looking for