WDF1000.sys

Earlier, I had a BSOD that I wasn't familiar with (analysis below). It says that the problem is with WDF10000,sys. I had intended to do a memory diagnostic later, so that I could let it run for a while, but then I just had another BSOD, which is Page Fault In Non Paged Area (0x50).

Since both of these appear to be memory related, I decided to go ahead with the diagnostics, but since the Windows disk was the first that I came to, and I hadn't tried the memory diagnostic on that, I went with it. I would have like it better if it had a burn in test, so that it would continue until I stopped it, but it only permits 2 passes. It did not appear to have found any problems, but according to what it said, it would display a log of the test when I logged in...it did not.

Anyway, I'm wondering if anyone can at least tell me how to determine if this is actually a hardware or software problem?

seekermeister said:

Earlier, I had a BSOD that I wasn't familiar with (analysis below). It says that the problem is with WDF10000,sys. I had intended to do a memory diagnostic later, so that I could let it run for a while, but then I just had another BSOD, which is Page Fault In Non Paged Area (0x50).

Since both of these appear to be memory related, I decided to go ahead with the diagnostics, but since the Windows disk was the first that I came to, and I hadn't tried the memory diagnostic on that, I went with it. I would have like it better if it had a burn in test, so that it would continue until I stopped it, but it only permits 2 passes. It did not appear to have found any problems, but according to what it said, it would display a log of the test when I logged in...it did not.

Anyway, I'm wondering if anyone can at least tell me how to determine if this is actually a hardware or software problem?

here is the info on that bug check
Usual causes: Memory corruption, Hardware (memory in particular), Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack.

Hmm, most of those potential causes can be eliminated, the RAM isn't mismatched and has been fine for quite a whlle. There hasn't been any recent drivers installed, the BIOS os the latest, no overclocking, no service pack to miss. I will recheck connections and device security, but I don't know of a way to determine whether the motherboard is faulty or not.

seekermeister said:

Hmm, most of those potential causes can be eliminated, the RAM isn't mismatched and has been fine for quite a whlle. There hasn't been any recent drivers installed, the BIOS os the latest, no overclocking, no service pack to miss. I will recheck connections and device security, but I don't know of a way to determine whether the motherboard is faulty or not.

What app did you use to test the memory? and for how long did it run?

I only used the Windows Memory Diagnostic, and it only lets you run two passes. I will run another test with Memtest86 later, and let it run a while.

Capt.Jack Sparrow said:

I would recommend to Run a AV or Malware scan because i search for this file some of them suspect it might be a Malware as well.

Edit: Found something which might help you SetPoint 4.60 Released.... - Logitech Forums

- Captain

If I understand what you are saying, you think that WDF1000.sys might be malware. I suppose that is possible, but it is an essential Windows system file and it is located where it should be.

I'm not sure what SetPoint has to do with this topic, but perhaps you were thinking of another thread where I posted regarding a mouse problem today. However that link is for 4.60 and I already have 4.80.