Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: ntoskrnl.exe BSOD Randomly every few days

25 Jun 2014   #21
Broken Hyoid

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by essenbe View Post
Please explain. What you are describing is a restart of the computer and not a classic BSOD. BOODs (Blue Screen of Death) is when the screen turns blue and text appears telling you a bunch of stuff. Like this

[LEFT]Is that what you are getting or something else?
Okay I have never gotten that screen, the PC just restarts, and once I am at my dekstop again, I get a window such as this one :

Then once I click ''View Problem Details'' , it tells me it was a blue screen etc and ofcourse the 'Check for solution' button does nothing helpful... Also all the restarts do come up in BlueScreenViewer. What I was just saying was that I used to go straight to my dekstop after a PC BSOD restart and get that window shown above but now it brings me to this screen first :

and then once I am back onto my desktop I get that window as shown above again.


But yes, I have never actually gotten the physical ''Blue Screen'' that you posted upon restarts.

Will do the new tests you advised now and post results. Thanks.


My System SpecsSystem Spec
.
25 Jun 2014   #22
Broken Hyoid

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by essenbe View Post

Next, Open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Also, please go into bios and give us the reading of the +12V, +5V and +3.3V.
The cmd sfc /scannow file checker resulted in no integrity violations. Also the voltage readings are as follows:

VCORE Voltage: 1.2724V
3.3V : 3.304V
5V: 5.100V
12V: 12.105V

not sure if these values are good or not?

Also, a question about driver verifier, I have enabled it and re booted my PC as per your instructions, however I am confused as to what I am looking for. Do I keep it on for 24hrs and it posts results somewhere which I have to upload? Or do I just look for increased number of BSODs and take note of them manually? So far I don't see any difference in my PC since the reboot except for the fact that my CPU usage is highly fluctuating, from 10% all the way to the 90%s when idle(usually between 20-70, but it fluctuates alot), is this due to the driver verifier(my pc was stable CPU usage at 10% idle before this), should I keep an eye on my CPU temperatures(so far they are stable at 30-45 degrees)? Thanks.
My System SpecsSystem Spec
25 Jun 2014   #23
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Create a restore point so you can get back to where you were before Driver Verifier was enabled. System Restore Point : Create at System Startup

Driver verifier should be enabled on non Microsoft drivers. It will make your system run sluggish. It puts stress on your drivers, trying to make the weaker ones BSOD, thus being able to identify the offending driver, if there is one. That is the purpose of driver verifier. So, although the BSOD code says it is a hardware error, we are trying to make sure a driver is not causing the hardware error. Does that make it a little more understandable? I hope so, if not, ask away. BTW, to answer your question more fully, no it creates no file. It has to BSOD to identify the driver that is causing your issues to work, that is assuming it is a driver.
My System SpecsSystem Spec
.

25 Jun 2014   #24
Broken Hyoid

Windows 7 Home Premium 64bit
 
 

Yes, thanks that did clear things up. Also I have noticed now since enabling this driver verifier games are unplayable on my pc. sure they run and evrything but the FPS fluctuates between 10-100fps and thus makes the game unplayable and I get FPS 'lagg', I assume this is normal because of the verifier and not the GPU or its drivers messing up? My PC has become pretty useless apart from just general web browsing and I will probably leave it Idle for driververifier to run in the background, but amn't sure if that is the right way to test the drivers? It said to leave the verifier running while I carry out normal tasks, but since I cannot do that and am leaving the PC idle, I don't know if im getting full use out of this test, any advice?

NB. As I was typing this another BSOD happened. Same error code, no outstanding drivers etc, feel its not because of the driver verifier and just another ''normal'' BSOD that happened to take place now. Will keep you posted on any more BSOD, so far they haven't changed in frequency since enabling DV.
My System SpecsSystem Spec
25 Jun 2014   #25
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

The experience you see is to be expected. I hope you can do without gaming or tolerate it for 24 hours of use. Gaming, as I understand it, is when you usually get the BSODs, so try other activities that will put some stress on everything. This is one time we want you to BSOD as often as possible. But, in Gaming we always get the same codes, so lets make an effort to either find ehich driver it is, or rule out drivers.

I am not at my normal computer at the moment, so will need to wait a while until I get back to look at the dump file. When you get time, could you save me the trouble of reading this whole thread and make a list of everything you have done, tests we have done so I can see if we have overlooked anything. I really don't think so. Also, did you try another card on this board since we started this?

Please understand, I'm old and forget a lot and we are dealing with quite a few cases all at the same time, so sometimes it's difficult for us old foggies to keep things straight. So, please bear with me. But, these type of BSODs are some of the most difficult to deal with because we get no specific information from the dump files. That's why Boozad asked you to run Driver verifier. Maybe with a couple of BSODs, it will give us some info to go on. But, don't give up, we haven't.
My System SpecsSystem Spec
25 Jun 2014   #26
Broken Hyoid

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by essenbe View Post
Gaming, as I understand it, is when you usually get the BSODs,
It is actually the complete opposite of this. I have never gotten a BSOD while gaming. I have gotten them while idle/browsing internet/alt tabbed from games, but never ever when I am actually playing a game. I do not know if this is luck or related to the problem, but it is the truth.

Quote   Quote: Originally Posted by essenbe View Post
Please understand, I'm old and forget a lot and we are dealing with quite a few cases all at the same time, so sometimes it's difficult for us old foggies to keep things straight. So, please bear with me. But, these type of BSODs are some of the most difficult to deal with because we get no specific information from the dump files. That's why Boozad asked you to run Driver verifier. Maybe with a couple of BSODs, it will give us some info to go on. But, don't give up, we haven't.
lol no problem, here is a summary of what has happened so far, for you or anyone else viewing this thread:


SUMMARY:
-Random BSODs(no physical blue screen appears upon restart but upon PC restart I get the following:


-Tested RAM(with Memtest+) : 8 Passes, No errors
-Tested GPU(With Furmark): No errors, Stable GPU temperature
-Tested CPU(with Prime95): Ran for 1.5hours, no errors, stable CPU temperature
-Tested HDD(with Seagate): No errors found in short and long tests.
-Checked Voltage from BIOS:

VCORE Voltage: 1.2724V
3.3V : 3.304V
5V: 5.100V
12V: 12.105V

-Currently have DriverVerifier running to stress my drivers. So far I have had 3 BSODs today(seems more than usual if it continues I shall keep you updated).


I am thinking of doing a vanilla reinstall of windows. Perhaps it is just a faulty driver, and if it isn't atleast with a clean reinstall of windows if the BSODs continue we can completely rule out software/driver issues. I just don't know the right way of doing this, e.g., do I update windows after a vanilla reinstall? What drivers should I start with(I need GPU/sound/wireless dongle drivers for gaming), how to test the driver etc. Ofc this is just my opinion and if more hardware testing is what you recommend then I would be happy to carry them out. Thanks.


EDIT:
Since posting this I have BlueScreened again, making the BSODs for today upto 4. This IS abnormal and the BSODs seem more frequent than normal. I am just browsing these forums while the BSODs occur. Attached the minidump files for the 4 BSODs that occurred today. This has led me to believe that this is a driver issue, what are your thoughts on this?
My System SpecsSystem Spec
25 Jun 2014   #27
Boozad

W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
 
 

They're all 0x124s and I can't get a thing out of them. Driver Verifier seems to be doing something to cause that many BSODs but there's absolutely nothing showing except for this:

Code:
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80087f6038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
The same as all the others. I'm going to ask a couple more people take a look because if all hardware tests have passed and DV isn't showing up any rogue drivers then all I can think of is the motherboard.
My System SpecsSystem Spec
25 Jun 2014   #28
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

OK, I'll take a look in a minute, but the vanilla reinstall is where I was thinking of going next. Download all of your Motherboard drivers from the Asus site, they should be the most current, and your GPU driver from AMD and Microsoft security essentials.. Put them on a USB Flash drive. What I do, which will upset some people here. As soon as I get to the desktop, go to Windows update and in the left column select change settings, set it to download updates and let me decide what to install. But, install no updates, which you should not have internet access anyway. Transfer the drivers from the USB drive to the desktop. Install all of your drivers, but, install the chipset driver first and do all the restarts for each driver. Do not install any of the Asus utilities like AI tuner. Install the rest of the drivers, but make sure the Lan driver is installed last of the motherboard drivers. Then install Msft Security essentials, then the GPU driver. Select custom install and only install the Display driver and the PhysX driver.making sure the 'clean install' checkbox is checked even though it should not be necessary. Once all of that is installed, go to windows update, you will have about 100 updates to inwstall. Take your time. Select about 10 at a time, and install them. Be sure throughout this process to install no hardware drivers. After each 10, use the computer for a few minutes to make sure it is running OK, then install another 10, give it a little time between each so if something is not right, you will know which ones messed it up. Continue this until you check and there are no more updates to install. Then install nothing else. That should put you in a clean state. I forgot to mention, when you do the install, disconnect 1 wire from each hard drive except the one you are installing windows on. After all drivers and windows updates are installed, do an image of the install and save it on another drive somewhere or a DVD drive. That may save you from having to do this again. You can install the image and have a perfectly clean install.

Now, install nothing at all and do not connect any drives for a few days, if possible. You will have nothing that should cause a driver problem. Now, if you can hold out for a few days and get no BSODs, you will have a pretty god idea that a driver is at fault. If you have BSODs after this, you will know you have a hardware problem. that is exactly what I would do. With just the basic clean install, use it for doing normal stuff, which will not be a lot, but give it a good run for as long as possible. Once you feel good about it, if that happens, install 1 program at a time and use it for awhile until you feel good about it, then another. I know this is a PITA, but at least if you install a program and all of a sudden start having BSODs, you will know exactly what it is. That is exactly the way to do this to identify what is wrong. Before the install, set BIOS to optimized defaults, set the sata controller to what you want (AHCI is best and probably the default) set your ram timings, frequency and voltage to manufacturers specs), you can set the boot order to DVD/CD 1st boot device and hard drive to second device. That way if you need to use the installation disk or recovery disk, it will be no problem.

So, disconnect all but the drive you are installing windows to first, set bios to defaults next, while in bios put the installation DVD in the drive, set the boot order save and exit. You should boot straight into the installation disk. When you get to the screen of where do you want to install windows, you may want to select advanced options and select format first, when that is done, select that drive and install. You will have no 100MB partition, the boot files will be on the C drive if you do that, but it will hopefully clean off anything that may be on the drive that could mess you up.

If you have any doubts or questions be sure to ask before starting. I don't mind a bit. But, I would wait until you have run driver verifier for the full 24 hours first, and that is 24 hours of use.
My System SpecsSystem Spec
25 Jun 2014   #29
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

What manufacturer, nodel and size of PSU do you have? The values you gave me fro Bios are all quite good. But that is at idle, what it does under stress could be something very different.
My System SpecsSystem Spec
25 Jun 2014   #30
Broken Hyoid

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by essenbe View Post
Now, install nothing at all and do not connect any drives for a few days, if possible. You will have nothing that should cause a driver problem.
Does this include programmes such as games and such? Or just drivers? Or can I install one game then wait a few days and no BSOD then next game, like that?

Quote   Quote: Originally Posted by essenbe View Post
What manufacturer, nodel and size of PSU do you have? The values you gave me fro Bios are all quite good. But that is at idle, what it does under stress could be something very different.
The PSU is a Corsair CX500M Modular(500W 80+ Bronze Certified)



I will let the DriverVerifier run for 24hrs and let you all know, planning to do the Vanilla reinstall on Saturday/Sunday.
My System SpecsSystem Spec
Reply

 ntoskrnl.exe BSOD Randomly every few days




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD randomly twice in two days since fresh format
Hey guys, got myself some lovely BSOD issues after a fresh format yesterday. One happened yesterday upon closing a Chrome window and the next today whilst playing Bastion. Neither are particularly strenuous activities so I'm presuming a driver error. I've attached my dump files. Any...
BSOD Help and Support
ntoskrnl.exe+75b80 BSOD every few days
Hello, For a few weeks i have been having BSOD errors. I tried searching for help on google but i didn't find anything useful. When using blue screen viewer it says it's mostly caused by ntoskrnl.exe but I am not sure if it's correct, this mostly happens when playing games. I also...
BSOD Help and Support
Two different BSOd's in two days, happens randomly
Hello everyone, I recently installed a new motherboard and I think that may be the cause of my problems. I tried reading the dump files myself, but I'm no expert. What I picked out (from the two most recent BSOD's) is a USB 3.0 Accelerator (ASUS software) driver failure BSOD and a CPU hardware...
BSOD Help and Support
BSOD twice in 5 days (ntoskrnl.exe/ntkrnlmp.exe and ntfs.sys)
I got a BSOD twice in the last 5 days. According to WhoCrashed, the first one came from ntfs.sys and the next one from ntoskrnl.exe/ntkrnlmp.exe. Apparently most likely a driver/memory error. The OS is Win7 x64 Ultimate Professional retail. The PC is slightly less than 2 years old and so is the...
BSOD Help and Support
BSOD - Randomly over the last few days. Driver_irql_not_less_or_equal
Hello, recently I have received 2 BSOD. Yesterday when i was playing Dota 2(with Itunes in background), and today when i was just browsing the internet and listening to Youtube. I can't seem to find the issue, so hopefully someone can help. I am reasonably sure that this is coming from a driver...
BSOD Help and Support
BSOD randomly every couple of days
Hello, any help on my problem is much appreciated. I have experienced the BSOD seemingly randomly every so often on my new computer build. It has a clean install of Windows 7 Home Premum 64 bit and I haven't installed very much software on the computer because of the problems. I've...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:38.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App