New
#21
ARC------I ran driver verifier for about 36 hours. There were a number of crashes during this period. I looked at the results before I disabled the program.
Last edited by dagaraelder; 12 Mar 2014 at 12:18.
ARC------I ran driver verifier for about 36 hours. There were a number of crashes during this period. I looked at the results before I disabled the program.
Last edited by dagaraelder; 12 Mar 2014 at 12:18.
Driver verifier is not any specific. So it is doubtful that it is actually a driver issue.
At this point, it would be best for you to opt for a clean install. If still the situation is the same, I would blame the hardware.Code:BugCheck C1, {fffff9801463eea0, fffff9801463e387, e10160, 23} Probably caused by : netbt.sys ( netbt!NTIoComplete+85 ) Followup: MachineOwner ----------------------------------------------------- BugCheck 1E, {ffffffffc0000005, fffff88003713d80, 0, 0} Probably caused by : tunnel.sys ( tunnel!LwEnqueue+71 ) Followup: MachineOwner ---------------------------------------- BugCheck C1, {fffff98015694f10, fffff98015694f07, f540f8, 32} Probably caused by : wfplwf.sys ( wfplwf!FilterOidRequestComplete+113 ) Followup: MachineOwner ---------
I agree. I highly suspect the motherboard.