After awaiting at the login screen for a 3-4 hours (doing nothing), my PC suddenly restarted. I checked the event logger and saw a critical error 0x133. I'm attaching all information as described in the forum, in the attached zip file.
I would also like to add, that after running sfc /scannow, the system scan detected corrupt files but was unable to fix all of them (as it is saying). It also reports that details are included in C:WindowsLogsCBSCBS.log. Should I upload this file also ?
I've been encountering BSOD Critical_process_died twice in 2 days. What is making me scratch my head is that this issue occur when there is a loud humming noise in my tower/cpu (what ever you call it). Tried searching the source of the noise but it doesn't seem to be the cpu fan or the gpu fan. Also this loud humming noise happens randomly and when it does, my computer starts to hang/lags before the BSOD takes place. Besides that, after a couple of restarts the loud humming noise seems to disappear and the computer works fine again.
Went to turn on my computer today and got a screen with the Dell Logo and a message "Boot manager has recovered from a critical error." It went on to say there were missing or corrupt files that were restored from the default configuration. I did a Google search and found absolutely nothing about this error. This laptop is only 2 months old. I couldn't find anything in the event viewer either.
Recently, my computer started freezing up at startup. It BSODs with the error in the title before making it to the login screen. Up to this point, I have run chkdsk /r /x which took two days and reported no errors and have attempted to run SFC /scannow /offbootdir=c: /offwindir=e:windows which gave me the "windows resource protection could not start the repair service". I don't know how to get the scan to work and have already tried to manually start the trustedinstaller service.
The system is Windows 8.1 on a 2tb raid array (mirror)
Here is all the debugging information I have from the memory dump:
Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:MEMORY.DMP] Kernel Bitmap Dump File: Only kernel address space is available
Memtest came back good. No errors. Also thought I should mention temps are just fine, nothing going above 50C.
(I was running 8.1 before the reinstall) So randomly about a week ago my computer started to bsod out of nowhere saying Critical Prcoess died. Then I started getting Kernal data inpage error. I, of course, googled the issue and there seems to be no solid fix for them. After some fiddlig I seemed to make the bsods stop (could have been luck) and then I was only getting hard locks. No bsod, but everything, including the cursor, was frozen. No ctrl alt del could fix it, it was stuck and required a hard reset. Some thought it was registry errors, others thought it was hardware.
I think I have ruled out software after a reinstall, and still having the issue.
System info: Windows 8 (previously 8.1 before reinstall) both 64bit Intel i5 4670k 16GB Kingston HyperX 128gb Samsung 840 SSD 1TB Seagate baracuda 500GB WD green EVGA GTX 670 Corsair AX850 PSU Gigabyte Z87M-D3H mobo Bios: American Megatrends Inc. F4 4/16/2013
I've recently started getting frequent BSODs and I am not entirely sure why. There doesn't seem to be anything I know that would be causing it. I had the pagefile disabled on my ssd and recently enabled it again to catch the dump file if I BSOD again and I just did. Attached is the SF Diagnostic file with the relevant information.
I've been dealing with shoddy drivers for about three months now and recently it got so bad I had 9 BsoD's in one day. At that point I made major changes and got rid of everything that was unnecessary. Unfortunately I'm still having problems, with two BSoD's here in the last hour.
I'll attach the two BSoD's I've just had along with the data from msinfo32 in hopes this can finally stop.
I bought a new custom built PC from EveTech around 2 months ago for $1900.00. I installed windows 8.1 on it, and have just been receiving ENDLESS BSODs. At first I found out that Windows 8.1 does have issues with BSOD, so I installed Windows 8, hoping this would have been the solution.
I started doing some investigations on how to read BSODs, and initially I thought it was because of outdated drivers, bad memory etc, because all the posts that I read said that this is MOSTLY the cause of BSODs. I installed every program under the sun to search my drivers, and all stated that everything is updated...
Going further in the investigations, I thought it was because of overclocked CPU and GPU hardware, but even after resetting it back to factory default, I am still having this issue.
The absolute worst part of this, is that the BSODs are never the same - they are constantly throwing a new .sys file stating that "this is the problem".
Previously with win7, I had a Windows 8 dually installed. Back then, I used to get the first error only, very frequently, and only in Windows 8. I had ignored them because I had Windows 8 installed only for testing purposes, and I thought they would go away. But now, they just keep popping up, with the reference by pointer error popping up 4 damn times in a row. And may I also add just how slow my PC gets before a BSOD?
I've tried looking them up, but the solutions seem to involve the removal of different drivers. So I thought of just creating a new thread instead. I have a few games installed and I do overclock my pc sometimes, but the recent BSOD (irql) took place when I was watching a video on youtube. I am attaching the SF grab and a bluescreenview report (the 5th error in it is the dpc watchdog violation).
This might be completely irrelevant, but I'll mention it anyway. The previous Windows 8 is still installed. I tried deleting it from msconfig, and was successful, but the files are still there and it seems to be the 'system partition' right now. See my previous thread for more info.
Happened again. Uploading SF grab with bluescreenview report.
Happened a few more times. I'm trying to keep the logs updated. Another thing; my PC now seems to be very slow and sometimes when a crash occurs, all the online accounts I'm logged into (Facebook, Eight Forums, etc.) automatically logout. This was also the case in my earlier Windows 8 installation. And the latest crash appears to be of a different driver.
I'm getting quite regular BSODs and crashes, previously I was getting crashes from AMD 14.7 beta drives so I swapped down to the 14.4 drivers. Now I'm not getting BSODs from atikmdag.sys, but I'm getting BSODs from what looks like ntoskrnl.exe. Additionally sometimes my computer will freeze, the display will show a static image, and the computer won't respond to keyboard/mouse input. Sounds can be heard to play as normal indefinitely (I haven't left it for more than a minute so not sure how long it would continue). This suggests to me that it's a display driver problem.
Here's the list of BSODs as shown by BlueScreenView:
Highlighted in blue are the crashes before changing drivers.
This is my dxdiag, I'm running an A10-7850k, 8gb corsair vengence pro 2400mhz, fm2a88x-itx+ and an 840 evo ssd.
I can upload any requested dump files or information.
I couldn't use SF diagnostic tool because I don't have .NET framework 3.5 installed, and when trying to install it I got error code 0x800F0906, and following all of MS's instructions failed (could still connected to update server, just not for .NET 3.5, using install media failed probably because 8 is different to 8.1).
This is what BlueScreenView calls a "minidump" (this is for the most recent crash shown above. I'm not sure if this is any different from what SF Debug collects).
I've been trying to troubleshoot an issue with my fan speed running at max speed from boot to Windows 8.1 desktop loading. This happened after installing Alienware Command Control which, unbeknownst to me, was not compatible with Windows 8.1 x64 and has, I think, loaded an incompatible (with Windows 8.1 x64) firmware version to my MIO board.
To try to remedy this I have:
Uninstalled that software. Performed a power drain to see if that would reset the MIO board (which controls fan speeds). Tried restoring a previous disk image. Tried installing a fresh copy of Windows 8.1 - this step went wrong for some reason and didn't complete. Tried a CMOS reset.
None of this has worked and now I'm stuck in a loop I can't get out of.
If I try to boot from the drive I fresh installed Windows 8.1 on, I get BSOD "whea_uncorrectable_error".
If I try not boot from a Windows 8.1 install disc or my Macrium Reflect repair disc, I get BSOD "Machine Check Exception".
I've tried a CMOS reset a couple more times, made sure the time is correct and have loaded optimal defaults.
I'm at a loss what to try next. Prior to the BSOD's, I'd decided to gamble on it being a MIO board problem and ordered a new one from eBay.
If I can't install Windows then the new board is useless. I don't believe the MIO board is causing the BSOD's - it booted fine (albeit loudly) after restoring to a previous disc image of Windows.
I use lenovo z510i i7 4702QM 8gb laptop.Nearly everyday i'm getting a bsod while working.I only use my laptop for my job,never play games or make hard use.I belive that bsods are from device drivers of microsoft.All intel and nvidia drivers are updated from their own sites and other from lenovos site.*.zip file attached to this message contains the dump file of last crash.
In the last months I have been experiencing many BSODs, with no particular pattern. Sometimes, the BSOD happens when I have left the computer alone for some minutes. Others, the system crashes when I am using it, primarily for work.
A couple months ago I put together a new computer with these specs: Asus M5A99FX MotherboardAMD FX-4300 3.8Ghz Quad Core CPU8GB Corsair Dominator RAMThermaltake TR2-600 PSUAsus Silent 210 Video CardWindows 8 ProfessionalWestern Digital 1TB Black Hard Drive
It seemed to work fine for the first month and then suddenly every day or two it would throw a BSOD and not always the same one. The various BSOD stop codes have been 0x00000139, 0x0000001a, 0x00000019, 0x00000001, 0x0000000a and as far as I can tell no one happens more than any other. Also not only BSOD's but I've seen a number of disk related errors as well:A corruption was discovered in the file system structure on volume C:.
A corruption was discovered in the file system structure on volume Boot The driver detected a controller error on DeviceHarddisk1DR1 I believe that the BSOD's preceded the start of the disk related errors. Various things that I've tried to identify a hardware problem: Ran Seagate Seatools both short and long test and the hard drives passes bothRan Memtest86+ for a full day with no errorsUpdated the Catalyst chipset drivers from the version on the driver cd to the latest available from the AMD websiteSwapped the Thermaltake PSU for a Corsair PSU
I've put together four AMD based machines in the last four months with various Asus motherboards and mostly similar specs, the first three have Windows 7 Pro installed and work perfectly but this fourth one nothing I've done has made any difference and I can't find a hardware based problem although I suppose there's always a chance it's a bad CPU or motherboard. If that's the case how would I know that and which part it is?
my PC's been plagued by various issues for a while now, such as various BSODs and programs suddenly crashing and unwilling to start again until a reboot. I'm hoping the fix for the latter is the same as the fix for the BSODs.
Since the blue screens usually seem to reference some form of memory, be it physical or virtual, I've had windows memory diagnostics do a bunch of extended passes, but it found no problems, and Samsung Magician says the SSD is fine too, which means I'm increasingly hopeful it's just a software issue.
Latest dump was made with driver verifier, by the way.
PC is an Asus Z87 pro mobo, with i7 4770k CPU and Geforce GTX 780.
What I've already tested: 1) Disks full scanned in HD Tune (no problem). About SMART: Samsung shows warning state in C7, but other programs don't see any problem. It shows 1348 and had not increased. 2) RAM tested separately for 3,5 and 7 hours - no errors. But it showed strange timings (19-15-15-31) when bios and CPU-Z says correct: 9-9-9-24 3) PSU tested with multimeter. Voltages are same in idle and stress: 5 V: 5,20-5,23, 12 V: 12,10-12,15, 3,3 V: 3,35-3,39. They were changing continuously between the varies, don't know if it's correct. 4) Temperatures are OK 5) No OC 6) 10 min Furmark - no problems
BSoD info: 1st: PC was quite idle - I left it for download games on Origin and Steam 2nd: computer was idle, maybe chrome and instant messenger on but I didn't use the PC 3rd: It was at the end or even after the origin finished downloading a update and when watching flash player video
I have a Samsung Series 5 laptop that I got last summer that has given me a series of problems, the biggest of which was the Windows 8.1 upgrade. That's been undone now and it boots properly and works well again, except that when starting up, or waking from sleep, it will restart and give me the little message that says my computer had a problem and had to restart and do I want to send the dumps to Microsoft. It used to do this before Windows 8.1. It has done it twice in the past 24 hours and I tried to read my minidumps but of course cannot without installing the whole SDK which I hope not to do. I downloaded the diagnostic tool and ran it and have the result to attach. I hope this is right.
The PC is a Samsung running Windows 8, 64bit. I have Online Armor firewall, Emsisoft Antimalware, and Avast antivirus. Did I have omitted anything. I have the minidumps zipped up, if they are not included in the diagnostic file.
I did a fresh install hoping that it would get rid of my BSODs which were numerous. So far, I only have 5 BSODs that I have had the patience to allow Windows to get to 100% on. I easily BSOD once a day, most are with MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL.
I have run memtest86+ ad nauseum with no errors, as well as Prime 95 for over 24 hours, I am stable and these are not temperature errors (30c idle, 71c at load).
For a while now I've been getting BSODs, sometimes while playing games, sometime when watching Youtube, sometimes when using other programs. I'm suspicious of a driver issue, but when I tried using verifier.exe and rebooting I get another BSOD - "driver_verifier_iomanager_violation" followed by it rebooting a couple of times, more BSODs, giving an error and forcing a system restore.
Zip attached - I have a whole load other minidumps going back a couple of months if they're useful!