BSODs and CPU at 100%

Toggle sidebar Toggle sidebar
S

sola_guy

Prominent
May 28, 2017
6
0
520
Hi,
I've been searching hundreds of forums for a solution, but it's probably too specific.

Firstly specs:
OS: Win 7 Proffessional
Motherboard: MSI Z44A-G43
BIOS: V2.13B2
CPU: Intel i7-3770
Graphicscard: Nvidia Geforce Gtx MSI Gaming X 6G
RAM: 16 Gb DDR3

Here's the issue:
My old graphics card (AMD Radeon HD 280X) died and I got a new Gtx 1060. I uninstalled the old drivers via DDU and installed the new geforce drivers. I noticed an issue when waking the pc up from sleep mode, which was fixed with the new 382.33 driver.
Now for the symptoms: A few days after I started using the new card (played games like WoW or Dragon Age: Inquisition without a problem) I experienced BSODs (IRQL_NOT_LESS_OR_EQUAL). Culprit was the svchost.exe, Sometimes I got PAGE_FAULT_IN_NONPAGED_AREA with the process being adksetup.exe. Both said memory_corruption. I also experienced random CPU-Jumps to 100% with the "system"-process taking up to 99%-100% of the processing power. It appeared while watching videos on youtube or using the internet browser in general, or doing other random tasks, but not gaming. Sometimes it happened a few minutes after booting, sometimes it took hours, before it occured, sometimes the PC crashed before it could happen. I was not able to recreate it, nor was I able to scan it with process explorer or kern rate viewer, since it never occured, when I was monitoring the system.
I reinstalled the nvidia driver because I thought, it was corrupt, and it worked again for a few days and then the same crashes and issues appeared again. But now there are no more crash dumps (neither minidumps, nor kernel dumps) generated, even though I didn't change any settings and the pagefile size is set to ~16400mb.

Now for the troubleshooting I already did:
When using the verifier-cmd, a BSOD happened on boot up (normal mode) with cause being wdf01000.sys.
Unplugging all USB-peripherals doesn't prevent this BSOD from happening.
Sfc /scannow results in no violations detected.
Chkdsk system partition shows no integrity issues.
Anti-Malware scan was not able to run, because it crashed at random points (once right in the beginning, once at around 34%).

I am at a loss here. Since I am unable to analyze crash dumps now that there are none generated anymore I don't know how to troubleshoot this. Is a fresh install of windows the only solution? It sounds like a driver issue, might there be another issue? Maybe even hardware related?

Edit: This is my first post on this forum, so please excuse any missing information, styling mistakes or else. Please feel free to point out any mistakes and. I am thankful for any advice that helps me solving this issue!
 
Solution
S
Hello all of you!
I wanted to make a quick update, because it seems my PC is working right now. No crashes, bluescreens or weird processor high loads for almost a week now. According to "never fix a running system" I will leave it at that and hope the problem really just was a driver issue that fixed itself by reinstalling most of the crucial drivers.

I'm really thankful for the help, both of you. Kudos to you!

Kind regards,
S-G
Sort by date Sort by votes
goku1234567890

goku1234567890

Distinguished
Nov 6, 2012
1,799
0
20,460
Hello there, how are you? Hope you are having a nice day. To me it looks more and more like a virus or malware. I had same issues some time back. BSOD at random and malware being the culprit. Have you tried running whole system scan with anti-virus? Have you tried running the system in safe mode? If it doesnt crash in safe mode i would say its a malware or virus for sure. Also try running anti-malware and system scan from anti virus in safe mode although it wont be as much effective since not all load points are loaded in safe mode but its worth a try.
 
Upvote 1 Downvote
S

sola_guy

Prominent
May 28, 2017
6
0
520
Thanks for the reply. I will certanly try that. Had a complete scan running the whole day with no findings (Software: MSE), will try MBAM as well, and in Safe mode, too.

Will update soon. Thanks again :)

Edit: I ran MBAM and MSE in Safe Mode without any findings. Might there be a driver issue that doesn't appear in safe mode, because it's not loaded?

Edit2: I tried uninstalling all the drivers I don't need, but I still get crashes in verifier. Although might that be related to running verifier on all elegible drivers instead of a specific one? The crashing driver is always wdf01000.sys.
 
Upvote 0 Downvote
RALPH50

RALPH50

Prominent
May 29, 2017
20
0
520
Hey sola-guy, I guess I would uninstall the graphics driver first and then run the verifier because your wrote, "When using the verifier-cmd, a BSOD happened on boot up (normal mode) with cause being wdf01000.sys." So that would mean that you are able to recreate it. You are going to have to narrow it down and I guess uninstalling the recent Nvidia driver should be first. Try to recreate the BSOD's without the driver installed. If no BSOD'S, then reinstall Nvidia driver and check again. You might want to also try Memtest and check your memory cards. Memory violations can be caused by many things and the wdf01000.sys just indicates where it stopped, but may not be the cause. I also know you said that no new crash dumps are being created, but do you have any previous ones? It would be helpful if you could upload any old ones.

P.S. And I would run MBAM in normal mode. Safe mode does not load all the drivers. You might have a virus being loaded on normal boot up.
 
Upvote 1 Downvote
S

sola_guy

Prominent
May 28, 2017
6
0
520
Hi, thank you, both of you, for your suggestions! I will try them all out. I uploaded a zipped folder with all the crash dumps, as well as some additional system info from HWiNFO and msinfo32 (might be useful) to my dropbox. Here's the link:
Dropbox Link!

The crash dumps show the same BSODs I had after re-installing the nvidia graphics driver, so I guess, they are somewhat connected to the issue. The crashes from the crash dumps happened 2 days, after I installed the new nvidia graphics driver for the first time.

MBAM in normal mode found nothing. Will try out verifier-cmd with no nvidia graphics driver installed next. I'll let memtest run during the night, so I'll update that tomorrow.

Thanks for the help so far! :)

Edit: So I tried several things with verifier. First I ran it, only targeting the wdf01000.sys-driver. It didn't crash on startup, but when the desktop loaded and the crashing driver was rzudd.sys this time (a razer driver, I think, which makes sense, because in the moment it crashed, Razer Synapse was synchronizing with their cloud.
I uninstalled Razer Synapse and targeted wdf01000.sys once again and no crash occured at all.
Then I reinstalled razer synapse and uninstalled the graphics driver with DDU and ran verifier once with targeting all drivers, and once targeting only the wdf01000.sys-driver. Verifier checking all drivers resulted in a BSOD on startup caused by wdf01000.sys. Verifier targeting wdf01000.sys resulted in the same rzudd.sys-crash...
THen I uninstalled Razer Synapse, verifier set to target all drivers and the wdf01000.sys crashed on startup. When running only targeting wdf01000.sys without Synapse or nvidia driver installed, nothing crashed.

I hope this wasn't too confusing. :)
 
Upvote 0 Downvote
RALPH50

RALPH50

Prominent
May 29, 2017
20
0
520
Hey sola_guy, that was too confusing. I had to read it like 4 times. :(

You said in your Edit: 4th line"I uninstalled Razer Synapse and targeted wdf01000.sys once again and no crash occured at all." Then you said on the 8th line "THen I uninstalled Razer Synapse, verifier set to target all drivers and the wdf01000.sys crashed on startup." Which tests did you have Nvidia installed?

My suggestions:

1. If you're going to use Verifer, you have to target all drivers. You can not just target wdf01000.sys. That is a kernel-mode driver for the OS. That would not be the problem because you said earlier that you did a Sfc /scannow and found no violations.

2. If Razer Synapse is causing a problem at startup, try disabling it on startup. It's trying to update or reconfigure your graphics card settings on startup from cloud. I'm figuring your a heavy gamer. Maybe check your control panel/administrative tools/system configuration/startup and uncheck it if it's there and then reboot. It could also be under services.

3. After checking the dump files that you uploaded, I still believe you have a bad memory ram stick. If you don't want to run Memtest which takes forever, you can test your PC by taking out one of the rams and do your verifier checks. Test each ram separately.

4. I also think you should disable Verifer (delete the settings) and see what happens without it running.

5. You might also want to try to fix your Dump saving issue first. https://support.microsoft.com/en-us/help/130536/windows-does-not-save-memory-dump-file-after-a-crash


 
Upvote 1 Downvote
S

sola_guy

Prominent
May 28, 2017
6
0
520
Sorry for the confusing edit.
Goku1234567890, I tried running verifier with Razer Synapse uninstalled and Nvidia drivers installed and it didn't crash when targeting wdf01000.sys, but it did crash to BSOD when targeting all drivers.

RALPH50, yes, you're right, I am a gamer. I'd test the RAM first and see, what happens, because both of you advised me to check that. And I'll fix the dumps asap. I'm not entirely sure if the driver testing with verifier will yield any more useful results, because, as you said, wdf01000.sys is a kernel driver and this won't tell us, what the cause is.

My only problem with testing the RAM is, that my CPU heatspreader blocks one of the RAM slots, so I can't remove one of my four memory modules without taking of the CPU fan and heat spreader (and I don't own any thermal paste). Will testing work, if I test only the one I can't take out first and, if that one shows no issues, continue with that one and another one inserted at a time?
 
Upvote 0 Downvote
goku1234567890

goku1234567890

Distinguished
Nov 6, 2012
1,799
0
20,460
Well you dont to re apply thermal paste everytime you remove your heat sink. You can carefully remove it and carefully put it back making sure you dont wipe it or it doesnt spread. Although you can try your method first and see what result you get. And then for surety you can try running memtest afterwards.
 
Upvote 1 Downvote
S

sola_guy

Prominent
May 28, 2017
6
0
520
Alright, I will try that (but I can probably only do it next week, because I am away from tomorrow until monday). I will update, when I finished testing.

Thanks again for the time and suggestions!
 
Upvote 0 Downvote
S

sola_guy

Prominent
May 28, 2017
6
0
520
Hello all of you!
I wanted to make a quick update, because it seems my PC is working right now. No crashes, bluescreens or weird processor high loads for almost a week now. According to "never fix a running system" I will leave it at that and hope the problem really just was a driver issue that fixed itself by reinstalling most of the crucial drivers.

I'm really thankful for the help, both of you. Kudos to you!

Kind regards,
S-G
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom