BSOD 000F4 and 0004C Kernal Data Inpage Error

kochane · 30 Jan 2012

Hi All

I really hope you can help as I am completely at my wits end. I have a relatively new Dell XPS L502X laptop and the other week while watching a film it crashed for the first time with a BSOD and a Kernal Data Inpage Error message. It just froze on this screen and had to manually restart with the power button. This happened a few times.

I run Win7 64 Home Premium and 4gb ram with i5 processor.

I had not installed any new hardware but did try connecting my Virgin wireless network usb on one occassion when my internet was down and was wondering whether it was something to do with the inbuilt wireless connector.

The next few days this BSOD was really frequent until I moved a lot of stuff off the laptop (films, music etc) and it was fine for a few days. I then started getting the Kernal Inpage Error message again but only maybe once a day. I put on some other music and films onto the laptop and the same thing happened again but more frequently. I googled the problem and found some advice about the windows debugging tool which I downloaded but I could not get it to locate symbols although it did state the F4 critical error.

I am now finding that the laptop will not go 5 minutes without crashing with a F4 error and automatically restarting but either into the BIOS screen (like a F8 press) or to another page of text stating

Intel UNDI PXE-2.1
Copyright 1997 - 2000

This product is covered by one or more of the following patents (etc etc)

Realtek PCIe GBE Family Controller Series v2.37
cLIENT mAC Addr: (etc etc)

The thing is I am not a technical person at all and have tried to sort with a google search which is what has bought me here. I downloaded that Dump app and got some files exported before the laptop crashed but could not get a performance report (see attached for what I have)

If anyone could point me in the right direction as to what to do I would be so grateful, as I cannot even connect my externall hdd to take stuff off as there is no time before the laptop crashes. I have started in Safe Mode with networking and it still crashes.

One thing to note is that I have done a checkdisk and it did find some bad sectors the first time which it repaired but hasnt picked up anything since. I have also tried to defrag but it does always seem to crash whenever anything touches one of the system files (no idea what though)

Thank you

Gordon

usasma · 30 Jan 2012

The collection application didn't finish before you zipped it up. Please run it again and let it run for a longer while before zipping the files up.

The memory dumps are split evenly between Daemon Tools and an I/O error (likely a hardware problem).

Daemon Tools (and Alcohol % software) are known to cause BSOD's on Win7 systems due to the sptd.sys driver.
Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

Then please run the free hardware diagnostics from this link: Hardware Diags
In particular, run the hard drive diagnostics on all of your hard drives.

Also, you have a 2005 version of Pinnacle Studio's Marvin Bus which is likely to cause you problems. Please uninstall the program.

Win7 does not like wireless USB adapters - especially with older drivers. You have a wireless USB device with drivers from 2008. Here's my rant on these devices:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

You have a 2008 version of an Adobe product (it's file system driver). Please update it.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


iaStor.sys                  Wed Jan 12 20:50:12 2011 (4D2E5A54)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
mfenlfk.sys                 Mon Oct 10 16:41:04 2011 (4E935860)
mfehidk.sys                 Mon Oct 10 16:40:22 2011 (4E935836)
PxHlpa64.sys                Tue Oct 20 14:08:42 2009 (4ADDFCAA)
jswpslwfx.sys               Thu May 15 06:28:50 2008 (482C1062)
mfewfpk.sys                 Mon Oct 10 16:40:40 2011 (4E935848)
stdcfltn.sys                Fri Aug 20 14:05:01 2010 (4C6EC3CD)
nvpciflt.sys                Thu Apr 21 21:06:40 2011 (4DB0D4A0)
dtsoftbus01.sys             Mon Mar 14 09:15:36 2011 (4D7E14F8)
dump_iaStor.sys             Wed Jan 12 20:50:12 2011 (4D2E5A54)
mfefirek.sys                Mon Oct 10 16:44:46 2011 (4E93593E)
iwdbus.sys                  Wed Mar 09 18:43:23 2011 (4D78109B)
MarvinBus64.sys             Fri Sep 23 17:17:03 2005 (433470CF)
WDKMD.sys                   Wed Mar 09 18:43:12 2011 (4D781090)
nusb3hub.sys                Thu Feb 10 00:52:32 2011 (4D537D20)
SynTP.sys                   Fri Dec 17 11:51:13 2010 (4D0B9501)
GEARAspiWDM.sys             Mon May 18 08:17:04 2009 (4A1151C0)
Accelern.sys                Mon Dec 13 12:33:51 2010 (4D0658FF)
HECIx64.sys                 Tue Oct 19 19:33:43 2010 (4CBE2AD7)
igdkmd64.sys                Fri Mar 25 21:17:43 2011 (4D8D3EB7)
TurboB.sys                  Mon Nov 29 18:02:31 2010 (4CF43107)
CtClsFlt.sys                Thu Jun 16 02:40:18 2011 (4DF9A552)
NETwNs64.sys                Tue Dec 21 12:08:43 2010 (4D10DF1B)
nusb3xhc.sys                Thu Feb 10 00:52:33 2011 (4D537D21)
Rt64win7.sys                Wed Feb 16 04:03:57 2011 (4D5B92FD)
qicflt.sys                  Thu Jul 01 21:46:34 2010 (4C2D44FA)
RTKVHD64.sys                Fri Feb 18 04:55:19 2011 (4D5E4207)
IntcDAud.sys                Fri Oct 15 04:28:17 2010 (4CB810A1)
mfeavfk.sys                 Mon Oct 10 16:41:51 2011 (4E93588F)
adfs.SYS                    Thu Jun 26 16:52:37 2008 (48640195)
mfeapfk.sys                 Mon Oct 10 16:41:23 2011 (4E935873)
TuneUpUtilitiesDriver64.sys Thu Sep 17 07:54:52 2009 (4AB2238C)
cfwids.sys                  Mon Oct 10 16:45:40 2011 (4E935974)
mferkdet.sys                Mon Oct 10 16:42:13 2011 (4E9358A5)
nvlddmkm.sys                Thu Apr 21 21:05:37 2011 (4DB0D461)
nvBridge.kmd                Thu Apr 21 21:01:09 2011 (4DB0D355)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\013012-50388-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 30 07:31:12.168 2012 (UTC - 5:00)
System Uptime: 0 days 0:26:46.049
BugCheck F4, {3, fffffa80086b5b30, fffffa80086b5e10, fffff8000498e8b0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`086b5b30 fffffa80`086b5e10 fffff800`0498e8b0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\013012-22573-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 29 19:25:50.245 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:13.525
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 )
BUGCHECK_STR:  0xc9_23e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308
Bugcheck code 000000C9
Arguments 00000000`0000023e fffff880`04214308 fffff980`0c4e8e10 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\013012-38423-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 29 19:16:55.454 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:10.360
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 )
BUGCHECK_STR:  0xc9_23e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308
Bugcheck code 000000C9
Arguments 00000000`0000023e fffff880`03f8f308 fffff980`09e6ce10 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012612-15272-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 26 17:01:47.820 2012 (UTC - 5:00)
System Uptime: 0 days 1:33:49.100
BugCheck F4, {3, fffffa8006b04060, fffffa8006b04340, fffff800037e28b0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`06b04060 fffffa80`06b04340 fffff800`037e28b0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

kochane · 31 Jan 2012

Thanks for your reply.

I will take a look at your suggestions.
The problem I have also is that the laptop is now crashing within 5 minutes of loading - that is why I could not finish the collection application of the dump files - I will try it again after uninstalling the programmes you mentioned.

I did also rerun the Dell diagnostics cd and it came up with a hardrive error code of 0f00 1332 which a google search suggests means the hdd is dying - is this correct? Could a hdd die if the laptop is only 5 months old or could it be because of the drivers and programmes installed?

With the wireless WDA netgear adapter I seem to be unable to uninstall it (it says the uninstall file is missing) - not sure if I should reinstall it to uninstall it (if that makes sense)?

Thanks again for your advice

usasma · 31 Jan 2012

Most likely it is the hard drive dying. I've seen then come out of the box dead.
BACKUP your stuff IMMEDIATELY!!! There's no telling when it'll stop working, so you MUST get your data off NOW!!!

Try a Linux distro, or the Ultimate Boot CD (both are free with a Google search) to recover your data to an external device.

After the backup/data recovery, try this free hard drive diagnostic procedure to make sure that there is a problem: HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

Next, if you're able, ensure that you create the system recovery disks that the computer asks you to create. If the hard drive is dying, you'll need these to reinstall Windows. Dell is in the process of switching from providing DVD's to making you make them yourself - be sure to check (we make the customer provide these disks or we don't reinstall Windows for them - even under warranty).

The system/hard drive is likely to still be under warranty. If that's the case, take it in and make them fix it for you.
Remember the recovery disks as they'll need them to reinstall Windows for you.

If the hard drive passes the test that I mentioned, post back and we'll work from there.

kochane · 31 Jan 2012

OK Thanks again for your advice - it will be later in the day as I am at work at the minute

kochane · 31 Jan 2012

OK I managed to get the collection application to run all the way through and uninstalled Daemon tools and some of my videos/music

I have attached here

Thanks

Gordon

usasma · 31 Jan 2012

MSINFO32 still shows issues with Daemon Tools.
Did you run the free removal tool that I linked to?
Still has Daemon Tools stuff in the Startup Programs section also.

The verifier enabled memory dumps blame Daemon Tools. It's essential that you remove all traces of it.
Worst case, reinstall it - then uninstall it - followed by the sptd.sys removal tool.

You have a 2005 version of MarvinBus64.sys (part of Pinnacle Studio's Marvin Bus). Please uninstall the software.

You have a 2008 version of an Adobe File System filter driver. Please update all Adobe products.

You have a 2008 version of a wireless USB adapter driver. Win7 doesn't like these devices, and with older drivers they can cause continual BSOD's. Here's my rant on the subject:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

The other 2 memory dumps show I/O errors, so I'd still recommend checking your hard drive to see if it's failing. The link is Hardware Diags

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


iaStor.sys                  Wed Jan 12 20:50:12 2011 (4D2E5A54)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
mfenlfk.sys                 Mon Oct 10 16:41:04 2011 (4E935860)
mfehidk.sys                 Mon Oct 10 16:40:22 2011 (4E935836)
PxHlpa64.sys                Tue Oct 20 14:08:42 2009 (4ADDFCAA)
jswpslwfx.sys               Thu May 15 06:28:50 2008 (482C1062)
mfewfpk.sys                 Mon Oct 10 16:40:40 2011 (4E935848)
stdcfltn.sys                Fri Aug 20 14:05:01 2010 (4C6EC3CD)
nvpciflt.sys                Thu Apr 21 21:06:40 2011 (4DB0D4A0)
dtsoftbus01.sys             Mon Mar 14 09:15:36 2011 (4D7E14F8)
dump_iaStor.sys             Wed Jan 12 20:50:12 2011 (4D2E5A54)
mfefirek.sys                Mon Oct 10 16:44:46 2011 (4E93593E)
iwdbus.sys                  Wed Mar 09 18:43:23 2011 (4D78109B)
MarvinBus64.sys             Fri Sep 23 17:17:03 2005 (433470CF)
WDKMD.sys                   Wed Mar 09 18:43:12 2011 (4D781090)
nusb3hub.sys                Thu Feb 10 00:52:32 2011 (4D537D20)
SynTP.sys                   Fri Dec 17 11:51:13 2010 (4D0B9501)
GEARAspiWDM.sys             Mon May 18 08:17:04 2009 (4A1151C0)
Accelern.sys                Mon Dec 13 12:33:51 2010 (4D0658FF)
HECIx64.sys                 Tue Oct 19 19:33:43 2010 (4CBE2AD7)
igdkmd64.sys                Fri Mar 25 21:17:43 2011 (4D8D3EB7)
TurboB.sys                  Mon Nov 29 18:02:31 2010 (4CF43107)
CtClsFlt.sys                Thu Jun 16 02:40:18 2011 (4DF9A552)
NETwNs64.sys                Tue Dec 21 12:08:43 2010 (4D10DF1B)
nusb3xhc.sys                Thu Feb 10 00:52:33 2011 (4D537D21)
Rt64win7.sys                Wed Feb 16 04:03:57 2011 (4D5B92FD)
qicflt.sys                  Thu Jul 01 21:46:34 2010 (4C2D44FA)
RTKVHD64.sys                Fri Feb 18 04:55:19 2011 (4D5E4207)
IntcDAud.sys                Fri Oct 15 04:28:17 2010 (4CB810A1)
mfeavfk.sys                 Mon Oct 10 16:41:51 2011 (4E93588F)
adfs.SYS                    Thu Jun 26 16:52:37 2008 (48640195)
mfeapfk.sys                 Mon Oct 10 16:41:23 2011 (4E935873)
TuneUpUtilitiesDriver64.sys Thu Sep 17 07:54:52 2009 (4AB2238C)
cfwids.sys                  Mon Oct 10 16:45:40 2011 (4E935974)
mferkdet.sys                Mon Oct 10 16:42:13 2011 (4E9358A5)
nvlddmkm.sys                Thu Apr 21 21:05:37 2011 (4DB0D461)
nvBridge.kmd                Thu Apr 21 21:01:09 2011 (4DB0D355)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\013012-50388-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 30 07:31:12.168 2012 (UTC - 5:00)
System Uptime: 0 days 0:26:46.049
BugCheck F4, {3, fffffa80086b5b30, fffffa80086b5e10, fffff8000498e8b0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`086b5b30 fffffa80`086b5e10 fffff800`0498e8b0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\013012-22573-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 29 19:25:50.245 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:13.525
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 )
BUGCHECK_STR:  0xc9_23e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308
Bugcheck code 000000C9
Arguments 00000000`0000023e fffff880`04214308 fffff980`0c4e8e10 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\013012-38423-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 29 19:16:55.454 2012 (UTC - 5:00)
System Uptime: 0 days 0:00:10.360
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1308 )
BUGCHECK_STR:  0xc9_23e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308
Bugcheck code 000000C9
Arguments 00000000`0000023e fffff880`03f8f308 fffff980`09e6ce10 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012612-15272-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 26 17:01:47.820 2012 (UTC - 5:00)
System Uptime: 0 days 1:33:49.100
BugCheck F4, {3, fffffa8006b04060, fffffa8006b04340, fffff800037e28b0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`06b04060 fffffa80`06b04340 fffff800`037e28b0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

kochane · 31 Jan 2012

Hmm I did run the sptd tool and it said there was nothing there - just gave me the option to install or exit

I have contacted Dell and think its a hdd issue as had loads of errors in a test they run - its still under warranty so am going to send back for a new hdd to be installed

Thanks for your help though

Gordon

usasma · 31 Jan 2012

If they're going to replace the hard drive, then all the Daemon Tools stuff will be gone anyway!
Good luck!