Forum Home
Press F1
 
Thread ID: 141588 2016-01-16 08:40:00 New motherboard or is it safe to buy second hand? karbren (14078) Press F1
Post ID Timestamp Content User
1414556 2016-01-17 00:49:00 Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 17/01/2016 1:41:32 p.m.
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: SYSTEM
Computer: SHOPPINGTROLLEY
Description:
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{3420c958-bca1-11e5-824e-806e6f6e6963}#0000000000100000.
Event Xml:
<Event xmlns="schemas.microsoft.com
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>219</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>212</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2016-01-17T00:41:32.554105400Z" />
<EventRecordID>242</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="152" />
<Channel>System</Channel>
<Computer>SHOPPINGTROLLEY</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DriverNameLength">70</Data>
<Data Name="DriverName">SWD\WPDBUSENUM\{3420c958-bca1-11e5-824e-806e6f6e6963}#0000000000100000</Data>
<Data Name="Status">3221226341</Data>
<Data Name="FailureNameLength">14</Data>
<Data Name="FailureName">\Driver\WudfRd</Data>
<Data Name="Version">0</Data>
</EventData>
</Event> 		karbren (14078)
1414557 2016-01-17 00:51:00 Log Name: System
Source: Microsoft-Windows-DriverFrameworks-UserMode
Date: 17/01/2016 1:43:58 p.m.
Event ID: 10001
Task Category: Installation or update of device drivers.
Level: Information
Keywords:
User: SYSTEM
Computer: SHOPPINGTROLLEY
Description:
The UMDF service LocationProvider (CLSID {fb2ad313-39e9-44a7-8fe0-c09928485ef2}) was installed. It requires framework version 2.0.0 or higher.
Event Xml:
<Event xmlns="schemas.microsoft.com
<System>
<Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2E35AAEB-857F-4BEB-A418-2E6C0E54D988}" />
<EventID>10001</EventID>
<Version>1</Version>
<Level>4</Level>
<Task>48</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000000</Keywords>
<TimeCreated SystemTime="2016-01-17T00:43:58.499657700Z" />
<EventRecordID>251</EventRecordID>
<Correlation />
<Execution ProcessID="3764" ThreadID="3776" />
<Channel>System</Channel>
<Computer>SHOPPINGTROLLEY</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<UMDFServiceInstall upgrade="false" xmlns:auto-ns2="schemas.microsoft.com xmlns="www.microsoft.com
<Service clsid="{FB2AD313-39E9-44A7-8FE0-C09928485EF2}" name="LocationProvider">
</Service>
<MinimumFxVersion>2.0.0</MinimumFxVersion>
</UMDFServiceInstall>
</UserData>
</Event> 		karbren (14078)
1414558 2016-01-17 03:06:00 The section " Driver\WudfRd failed to load for the device SWD\WPDBUSENUM" Means A driver has failed to load, this can be a Plug and Play device, so if you have any USB devices attached unplug them, with the exception of the Keyboard & mouse ( if they are USB) The trouble also is that Windows 10 sees a Hard Drive Even Connected Via SATA as a Plug and play Device. So it could also be a HDD fault.

Have a look in the device manager - are there any exclamation marks or Question Mark s on anything ?


As quoted from other forums :
The power supply may detect too low voltage on one line, or too much current being pulled by a device and tells the motherboard to shutdown to protect it. So it could also be a faulty Power Supply or some other piece of hardware.

See if you can do this -- Click Start / Settings / update & security -- Check for updates, let it run -- Windows 10 can sometimes take several hours, and several times to run through and download new drivers.

It looks like Driver Frameworks may need an update Windows updates willdownlaod that automatically if its available.

Check one setting as well.

In Search, type Services scroll down, locate Windows Driver Foundation - User-mode Driver Framework -- See what its set to (double click it) If its set to manual, change to Automatic in the startup type, sometimes fixes things sometimes doesn't.

6914


Aint fault finding FUN :D

If the System Ran OK on an earlier OS then I doubt unless its real bad luck the hardware is the problem.

You can try safe mode as well to see if anything different happens - how-to-enter-windows-10s-safe-mode.html (www.pcworld.com) Thats the easiest way of the several options Shift Key + restart 		wainuitech (129)
1414559 2016-01-17 03:39:00 I have changed ata cord for the HDD . It hasn't seemed to have done much but it is starting better I must admit and freezing less. It is currently in W8.1 Pro not W10. It rolled back after the failed install last time. karbren (14078)
1414560 2016-01-17 04:13:00 I have changed ata cord for the HDD . It hasn't seemed to have done much but it is starting better I must admit and freezing less. It is currently in W8.1 Pro not W10. It rolled back after the failed install last time. Awhh Ok, so its not a SATA drive ? but an IDE Drive or was that a typo ?

Found a picture of the two. ( saves me taking one ) :D
6915

8.1 or 10, doesn't matter much of a muchness with those system Settings. 		wainuitech (129)
1414561 2016-01-17 04:26:00 Sorry yes it was a typo. I have now changed the power supply as after my other changes it kept restarting constantly karbren (14078)
1414562 2016-01-18 20:41:00 These days it's best if RAM sticks are exact matching pairs, from the same supplier, with the exact same specs.

Treating them all like the same logo block and stuffing in any combo of sticks is a known recipee for issues.

Sometimes you can get away with it, sometimes you cant. 		Paul.Cov (425)
1414563 2016-01-21 01:17:00 Looks like it was the power supply. I have fixed a couple of similar situations by replacing the power supply. PENTIUM (426)
1 2