BSOD is not creating logs

[Deleted member 1587028]

So basically I've had many issues over the last few years involving random BSODS with this computer, however for the past few months it has settled down. However today I started my pc and got 2 BSOD's in 20 mins. I want to start from the bottom and check everything, but the issue is when my computer BSOD's it doesn't seem to write any log to the minidump file. Last time it BSOD'd it also didnt write logs (about 6 months ago). In my control panel system settings I have ticked "write an event to the system log", automactically restart is unticked, and the debugging information is set to small memory dump (256 KB) and its directory is the correct minidump file. Any ideas, because once I can get logs I can then start to solve all of this!
Thanks for any help 😀

 

[Colif]

not all bsod create logs, most of the kernal level ones don't. Are the errors KMODE or Kernal events?

try running sfc /scannow in a command prompt with admin rights. It won't fix the logs but it might fix windows.

this might help: http://lifehacker.com/5459919/use-event-viewer-to-tell-when-your-pc-last-rebooted

 

[Deleted member 1587028]

It just blue screened again, with the DRIVER_IRQL_NOT_LESS_OR_EQUAL error, I am not sure if this is KMODE or Kernal?
I ran sfc /scannow and it did not find any integrity violations.
I have been using even viewer for a while now, and checking the last events before the crash doesn't really seem to turn anything up 🙁
Any more ideas and thanks for the help so far!

 

[Colif]

well, its a driver error given your description, much less painful than kernal ones. Try updating your drivers,

lets try seeing if you really have no logs. download and run thsi: http://www.resplendence.com/whocrashed
if you have any logs, it will find them and hopefully tell us what cause is.

 

[Deleted member 1587028]

Alright thats good news! Downloading now, it is worth noting I have had lots of separate issues with this computer having random blue screens before and they seemed to randomly appear / disapear. Are there any programs that automatically check all of my drivers (that are free and not full of viruses!)
Once again thanks 😀

 

[Deleted member 1587028]

I have downloaded and ran the program, and it also did not find any logs, (apart from the ones from 6+ months ago)

 

[Colif]

see if this can fix why you have no logs: http://www.resplendence.com/whocrashed_dumpnotwritten
its hard to fix this if we have no idea what cause is.

 

[Deleted member 1587028]

My paging file currently seems to be 7778 MB in size, but I have 8 GB of RAM, could that be the issue?

 

[Colif]

Probably, i just let windows look after it. Mine is too big but i have space to burn.

win 10 hardly uses it anymore, it prefers to compress things in ram than use page file. Its still necessary for other things though.

 

[Colif]

if you made it bigger, we just have to wait for next bsod and you can look at details now. Might even fix it.

 

[Deleted member 1587028]

I've cleared up some HDD space, will do their test soon to see if dumps are writing again

 

[Colif]

sorry about win 10 reference, forgot what forum I was on. Something was stopping you make it.

 

[Deleted member 1587028]

So I have followed all of that, increased my page size, and changed it to kernel memory dump, and now when its blue screening it shows the progress of writing to disk, and says data written to disk. However whocrashed doesn't find it, and I have searched the folder it is supposed to be in (as set up in the settings for dumps), and it isnt there. Any more ideas?

 

[Colif]

here are some default locations: https://social.technet.microsoft.com/Forums/windows/en-US/a5ebab26-61ef-42a4-a2bb-0fc60ad45385/bsod-error-log-location?forum=w7itprogeneral

if i had a driver updater I trusted, i would have suggested it. What you could do is run one but just use its suggestions as a guide to what web sites to visit and download the right drivers. I used one last week and while 1st install worked fine, the second froze my pc and wouldn't let me start pc. I ran system restore as the first driver had created a restore point before installing. My pc hasn't been the same since, now I have a random 71gb file on my storage file that defrag won't touch, think its an old system restore folder from my last install. enough about me, thats just the reasoning why I won't suggest using one

 

[Deleted member 1587028]

I have checked everywhere, and despite saying writing to disk, and something along the lines of write successful it does not appear anywhere within the file specified, and searching my PC turns up nothing. I have more than enough HDD space and a large enough paging file, what could it be?

 

[Deleted member 1587028]

Ok I am now getting small memory dumps when my computer BSOD's. Next time it does this due to an error I shall post them in here. Thanks for the help once again 😀

 

[Deleted member 1587028]

So in the short time I used it last night is just randomly shutdown, on restart it showed the top of the BIOS screen (the logo but nothing else), which it doesn't usually show, then restarted again. It did the same thing just now after 10 mins of use, then BSOD'd twice in the next 5 mins. Where should I attach the dumps?

 

[Colif]

run whocrashed and paste the results in here

nice to actually see them... maybe...

 

[Deleted member 1587028]

On Sat 16/04/2016 08:54:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041616-21309-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002ED41AC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 16/04/2016 08:47:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041616-27097-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xA7E88)
Bugcheck code: 0x50 (0xFFFFF881011C0A24, 0x8, 0xFFFFF881011C0A24, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[Colif]

oh goodie, finally get errors and they point at windows... ntoskrnl is NT operating System Kernal & NTFS is your file system... the usual suspects, not the actual cause though. They just pushed to do things by drivers that remain hidden still.

i wish i could tell you more...

I should have asked, what are specs of machine?

 

[Deleted member 1587028]

Yep the same thing was happening before 🙁

All at standard clocks

Fx-8350
2x4Gb of DDR3 RAM (some generic brand)
Gtx 660
990XA-UD3
1Tb Toshiba HDD
Corsair 650W

 

[Colif]

sometimes ntoskrnl errors are caused by Nvidia drivers, give this a go and see if it helps: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

 

[Deleted member 1587028]

Alright I did that, will let you know if I get more errors!

 

[Deleted member 1587028]

Ok so I upgraded to windows 10, and after a few days of usage I got a freeze, and now they are becoming more and more common, along with shutdowns and BSOD's. I have checked all the drivers I could think of and tried looking in event viewer, any ideas?

 

[Colif]

You were meant to be fixed... I will just close eyes and pretend its fixed

Can you upload the dump files to a cloud server and share a link here.

An option is run Driver Booster and see what drivers it can find on pc that need replacing. If you just upgraded to Win 10 without looking for new drivers, that is likely to be a reason.

one thing you might want to consider, do a fresh install of Win 10 as it reduces the amount of crap drivers on the System. It always helps after an upgrade.

What model Corsair PSU have you got?