Sign in with
Sign up | Sign in
Your question

[Advanced] Driver issues causing random freezes/restarts

Last response: in Windows 8
Share
January 22, 2014 2:58:46 PM

Edit: See comments for details. This has switched from a driver issue to a likely hardware issue.

Ubuntu doesn't crash at all, and i've used three fresh installs of Windows (Vistax32, 8x64, 8.1x64) with all of them crashing. I don't know what driver is causing the issue.

Note: It also abnormally restarted many times during the install of Windows, but not Ubuntu.

All the drivers are up to date, and I've disabled all the unneeded ones (ie. audio, microphone, etc).

------------------------------------------------------------------------------------------------------------------------
Event Viewer shows a pattern that at the same time, or one second before, every critical unexpected shutdown (aka Kernel Error 41), there is this:
Microsoft-Windows-FilterManager 6 None File System Filter 'npsvctrig' (6.3, ‎2013‎-‎08‎-‎22T03:38:22.000000000Z) has successfully loaded and registered with Filter Manager.

At the same time as this message, there is also this one (not concerning me though):

\Microsoft-Windows-Ntfs 98 None Volume C: (\Device\HarddiskVolume1) is healthy. No action is needed.\

Shortly before all of this (~5 secs) there is a list of other activities that go on. That's where the pattern ends.

  1. Information 1/21/2014 7:00:31 PM Microsoft-Windows-FilterManager 6 None File System Filter 'WdFilter' (6.3, ‎2013‎-‎08‎-‎22T03:39:34.000000000Z) has successfully loaded and registered with Filter Manager.
  2. Information 1/21/2014 7:00:31 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileInfo' (6.3, ‎2013‎-‎08‎-‎22T03:38:45.000000000Z) has successfully loaded and registered with Filter Manager.
  3. Information 1/21/2014 7:00:30 PM Microsoft-Windows-Kernel-Boot 30 None The firmware reported boot metrics.
  4. Information 1/21/2014 7:00:30 PM Microsoft-Windows-Kernel-Boot 32 None The bootmgr spent 0 ms waiting for user input.
  5. Information 1/21/2014 7:00:30 PM Microsoft-Windows-Kernel-Boot 18 None There are 0x1 boot options on this system.
  6. Information 1/21/2014 7:00:30 PM Microsoft-Windows-Kernel-Boot 27 None The boot type was 0x0.
  7. Information 1/21/2014 7:00:30 PM Microsoft-Windows-Kernel-Boot 20 None The last shutdown's success status was false. The last boot's success status was true.

-------------------------------------------------------------------------------------------------------------------

System Specs:
Athlon II x3 455 3.3ghz CPU
Antec Basiq 550w PSU/Logisys 480W PSU (Currently in use)
PNY 4gb(1x4gb) 1333mhz RAM
Radeon HD 7750 GPU (Currently in use)/GTX 660 2gb GPU
Western Digital 250gb HDD/Hitachi 250gb HDD(The one Windows is currently on)
Asrock 970 Extreme3 Motherboard

------------------------------------------------------------------------------------------------------------------------
I've searched around and it appears MS does not offer much information about this pattern, and other people experiencing the issue didn't have much luck fixing it besides disabling a driver, which i've tried.

Progress:
- Swapped PSUs
- Swapped HDDs
- Swapped RAM slots (but not the RAM)
- Swapped GPUs
- Ran Memtest86+/Windows Memory Diagnostics
- Ran chkdsk/Other HDD testers
- Reset BIOS
- Updated BIOS
- Updated Drivers
- Disabled all unnecessary drivers
- Reseated all components
- Installed Windows Vista 32bit on one HDD
- Installed Windows 8 and Windows 8.1 separately on the other HDD
- Tested for temperature issues

Any help is appreciated.

Edit: I am not familiar with the process of file dumping when Windows experiences these errors. Is it possible that Filter Manager has nothing to do with the shutdowns and it's just recorded when the PC boots back up? If that's the case there is a second pattern which is less consistent (happens about 50% of the time). An error stating "the shutdown at xx:xx:xx was unexpected" links to either Dhcpv6 or Dhcpv4 starting up at the same time or between 1-5 secs before the crash.

Here is the full event log if anyone needs it:
http://speedy.sh/uR87p/Shutdowns.evtx
a b \ Driver
a b * Windows 8
January 22, 2014 3:05:57 PM

A complete listing of your system specs (make/model of all components) might be useful in isolating the problem.
m
0
l
January 22, 2014 3:10:04 PM

Forgot about that, sorry.

System Specs:
Athlon II x3 455 3.3ghz CPU
Antec Basiq 550w PSU/Thermaltake TLR2 600W/Logisys 480W PSU (Currently in use)
PNY 4gb(1x4gb) 1333mhz RAM
Radeon HD 7750 GPU (Currently in use)/GTX 660 2gb GPU
Western Digital 250gb HDD/Hitachi 250gb HDD(The one Windows is currently on)
Asrock 970 Extreme3 Motherboard

The ones with multiple parts indicate that i've swapped them in attempt to fix the issue. The others have only been through tests.
m
0
l
Related resources
a b \ Driver
a b * Windows 8
January 22, 2014 7:33:17 PM

Is your motherboard BIOS up to date? Also, are your HDDs operating in IDE or AHCI (under SATA mode)?
m
0
l
January 22, 2014 8:24:23 PM

Thanks for the reply,

Yes i've updated it recently in an attempt to solve this.

They are SATA. Something to note is that I have to unplug one of them to get the other detected in BIOS, so i'm only using one at a time.

Also, the shutdowns are random. Windows was recently up for an hour before it crashed, then in the next 5 minutes it crashed 3 times.
m
0
l
a b \ Driver
a b * Windows 8
January 23, 2014 3:21:07 AM

I understand that you have SATA drives, but what mode are the SATA drives operating in? Go into your BIOS and look for the SATA settings. There you find an entry called SATA mode. Usually 3 choices (IDE, AHCI, or RAID). See page 48 of the motherboard manual (linked below):

ftp://66.226.78.21/manual/970%20Extreme3.pdf

That is an Asrock link, by the way.
m
0
l
January 23, 2014 6:04:51 AM

Each drive is operating in IDE mode.

I'm not too sure if this is a driver issue anymore because even Safe Mode crashes on 3 different installs of Windows, but its confusing because Ubuntu doesn't crash at all.
m
0
l
a b \ Driver
a b * Windows 8
January 23, 2014 6:43:16 AM

IDE mode is the slowest, but most compatible of the modes. This really sounds like some sort of controller/driver conflict with your HDDs. I say that because you mentioned that the "one at a time" issue.

If only the Hitachi is connected, does the system work properly (in Windows)?

m
0
l
January 23, 2014 9:12:32 AM

I can't test that right now, but i'll update this when I can.

What I can say is that this problem originally started as a crash or two a day. Then three or four the next day, and so on. Then I had issues booting. This occurred on the WD HDD (Windows 8 64-bit), which was the only one plugged in at the time, so it's likely that Windows would still experience crashes.

For now I leave both HDDs with the SATA Power cables in, however only use one data cable at a time so I can easily swap between them. Could this cause issues?
m
0
l
a b \ Driver
a b * Windows 8
January 23, 2014 9:21:45 AM

It shouldn't matter because one HDD is not aware of the other when not connected.

If connecting the 2 HDDs causes (via data cables) the failure, then that is where the problem lies. What are the specific models of the 2 HDDs?
m
0
l
January 23, 2014 2:32:09 PM

Bear with me, I know this is a lot of info:

Hard Drives:
Hitachi HDP725025GLA380 (ATA Device) and Western Digital Caviar SE16 WD2500KS-00MJB0 (ATA Device).
I currently have both completely plugged in, and only the Windows 8 HDD was recognized (Hitachi).
Note: It's come to my attention that it is only not recognized in the boot order, however under Storage Devices both HDDs are shown. If I have the WD plugged in, then plug in the Hitachi, only the WD is in the boot order. Same goes if I have the Hitachi plugged in first.
I did notice something strange this time. Before I could always access the other HDD via Explorer, however it doesn't exist now. Device Manager does show it though.

Memory:
RAM got 2 passes on memtest, however it froze after that. It typically freezes within 5 minutes. This is not the same freeze as I experience with crashes. The display is not frozen, however the test stops and all input is ineffective.
I have forced it to run at 1333mhz at 9-9-9-24 timings with 1.5V.

Other:
Windows crashed 3 times while trying to edit this. Twice when attempting to load windows and once when it loaded (Most crashes seem to happen when trying to boot or right after boot, after that I can do stuff for 10min-20hours or so)

More info:
These are the only other errors/warnings that are given, not being time related to the shutdowns, but they are consistent:
- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. (And a bunch of other variations)
- The Service KMSELDI service terminated unexpectedly. It has done this 1 time(s).
- Name resolution for the name _ldap._tcp.dc._msdcs.WORKGROUP timed out after none of the configured DNS servers responded.
- The driver \Driver\WudfRd failed to load for the device SWD\SensorsAndLocationEnum\LPSensorSWDevice.


Big Edit:
Linux crashed as soon as I hit enter on the login screen. It doesn't seem to crash once it is booted. Now I know its some form of hardware issue. Perhaps since Linux is less demanding it lasts longer and is less likely to crash.
m
0
l
July 19, 2014 12:17:45 AM

Hey gumby, did you happen to find a solution? I am experiencing a very similar issue and would like to know how you solved the problem.
m
0
l
July 19, 2014 10:03:38 AM

I reduced my RAM speed from 1333 to 800MHz and it did the trick. The thing is these issues can be caused by so many things.
m
0
l
July 19, 2014 5:17:03 PM

gumbykid said:
I reduced my RAM speed from 1333 to 800MHz and it did the trick. The thing is these issues can be caused by so many things.


Interesting, that is the problem with these kind of issues, there's no obvious solution or definite error log to guide you. The only info I know is that it's either GPU, CPU, RAM or PSU as the error I get is in the Northbridge. I have a new power supply on the way which is considered "one of the good ones" although I did think corsair was in that category as well but I have been having the same issues as you with restarts with a CX750 and an R9 290.

This is an interesting idea which I will try tomorrow to see if it helps at all but seems like quite a compromise as I use a lot of RAM intensive programs. Actually I will probably try the new PSU first and then if the issue persists I will try and drop the RAM speed.

Anyway I appreciate the response! Most people once they have solved the issue they tend to abandon a forum so I am grateful that you have offered an alternative to try :) 
m
0
l
!