Been BSODing five to ten times a month for over a year.

kemical

Windows Forum Admin
Staff member
Premium Supporter
#2
Hi,
unfortunately no dump files were included in your zip folder.

This might be down to either incorrect settings, no pagefile (you need one for dump file creation) and/or issues with the hardrive.

To ensure dump file creation please check your settings like thus:
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.

You will need to bsod again before a dump file is created but when you do, check for a minidump folder in the windows section of the HDD.

I can see from your dxdiag that your last bsod is a bugcheck d1 usually caused by driver using incorrect settings.

If you updated anything recently try rolling back or removing altogether. So without seeing a dump file we cannot say much more so the sooner you can post a dump file the sooner we can debug.
 


#3
I already had it set to these settings.
set.PNG


I checked C:\Windows\Minidump but didn't find anything in it. Though event viewer does say my computer crashed.

eventv.PNG
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
#4
I wonder if it's a bugcheck 124? This particular bugcheck will at times produce no dump file.

This bugcheck is usually caused by overheating so check your temps as well as removing any dust build up you may have clogging the system.

Other possible causes for no dump file creation is having no pagefile or the HDD has an issue.

If you've never messed with the pagefile don't worry about it otherwise return it to the rec' amount.

Open an admin command prompt and type chkdsk /r. Press enter and you'll probably need to reboot to initiate the chkdsk scan.

You could also try checking the drive with Seatools
 


#5
A month ago I opened my PC and blew out all the dust inside with an air blower.

I downloaded CoreTemp and Enabled Overheat Protection and logging on startup.
overheat.PNG


I don't remember changing anything about pagefile, but the recommended value is still not what is currently allocated. Should I change that?
pagefile.PNG


I ran the chkdsk scan.

What should I do now?
 


Last edited:

kemical

Windows Forum Admin
Staff member
Premium Supporter
#6
Hi,
thank you for the update.

Please list your full system specification including make and model of PSU.

I also had a look through your dxdiag again and noticed that one crash at least was caused by an app called Python.exe? Might be worth removing just to test?

Please run Seatools using the link i posted above.

Test your memory using the onboard memory diagnostic:
  • Click Start, type mdsched.exe in the Search box, and then press Enter.
  • Choose whether to restart the computer and run the tool immediately or schedule the tool to run at the next restart.
  • Windows Memory Diagnostics runs automatically after the computer restarts and performs a standard memory test automatically. If you want to perform fewer or more tests, press F1, use the Up and Down arrow keys to set the Test Mix as Basic, Standard, or Extended, and then press F10 to apply the desired settings and resume testing.
  • When testing is completed, the computer restarts automatically. You’ll see the test results when you log on.
Does the bsod occur when doing anything in particular such as gaming?
 


#7
Here are my specs:

Motherboard: MSI MS-7918
CPU: Intel i5-4690K (using stock fans, but didn't overclock)
RAM: G.SKILL 16GB (4 x 4GB) Ripjaws X Series DDR3 1600MHz
PSU: OCZ ZX Series 850W Fully-Modular 80PLUS Gold
SSD: Samsung 850 EVO 500GB
Video Card: Nvidia GeForce GTX 1060 3GB
Sound Card: ASUS Sound Card Essence STX II

The python app is a discord bot. This one: Red - Discord Bot documentation | Red-DiscordBot documentation and tutorials
I have it running all the time for my discord server.

Is the Seatools for HDDs only? Can I run it if I only have an SSD?

I ran mdsched, it told me there were no issues.

I haven't noticed any pattern to the BSODs. There might be one but I'm not sure of it. A few crashes that I remember were when I was watching videos.

Thanks a lot.
 


Last edited:

kemical

Windows Forum Admin
Staff member
Premium Supporter
#8
Many thanks for the info.

Is the Seatools for HDDs only? Can I run it if I only have an SSD?
The short answer is yes. See a screenshot of it running on my system:
seagate.jpg
 


#9
I ran the S.M.A.R.T check test and the Short Drive Self Test. No errors.
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
#10
Ok, try this as your pagefile may be fragmented.

Turn the pagefile off totally and reboot.

Once your back in Windows set the amount to whats recommended and place the figure in both boxes.

See if a dump file is created on bsod.
 


#11
I turned off the pagefile, BSOD'd, then turned it on again after rebooting, and a dump file was created.
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
#12
I'm just off out but will debug as soon as i'm back in a couple of hours.
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
#13
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, ffff8124234002f5, fffff8864ba7cd80, 0}

Probably caused by : win32kbase.sys ( win32kbase!HMMarkObjectDestroy+15 )

Followup:     MachineOwner
Hi,
basically the above means that data held in the memory couldn't be read because either the data or the memory is bad.

Code:
PROCESS_NAME:  AsusAudioCente
The above is what was running at the time of bsod and is dated 2014. Please update if possible:
Download Center | Official Support | ASUS Global

I notice your core system drivers are ageing and you have later versions on your motherboard support page.

Please update:
Chipset drivers (this also includes the management driver found under 'other's')
Support For Z97 GAMING 3 | Motherboard - The world leader in motherboard design | MSI Global

Post any new dump files
Intel rapid storage driver
Network
Audio

STXII.sys Tue Feb 18 04:24:18 2014: ASUS Essence STX II Audio driver, please update.
Essence STX II Driver & Tools | Sound Cards | ASUS United Kingdom
 


#14
Updated all these drivers.

How do I force the computer to crash now? I set the pagefile to zero again, but it's not crashing.
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
#15
I set the pagefile to zero again, but it's not crashing.
I think it was because the pagefile had become fragmented which you cannot duplicate.

I would set it back to the recommended amount placed in both boxes.

How do I force the computer to crash now?
Just use the machine as per normal.

Unless you know for certain what the actual trigger is/was it's best left alone.

At least you know that dump files will now be created so if you do bsod again just post up the file. Your thread will never be closed so it doesn't matter if it happens 6 minutes or 6 months from now you'll still be able to post the issue up.
 


#16
So like this?
vm.PNG



Thanks a lot man. Appreciate it greatly.
 


#18
Got a BSOD today. Tried to open an aup file for audacity and computer crashed.

Here's the dump.
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
#19
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff808d2a2d2b7, fffff3881afbd618, fffff3881afbce60}

Probably caused by : L6PODHD5SE64.sys ( L6PODHD5SE64+2d2b7 )

Followup:     MachineOwner
Hi,
according to the above dump file the following driver is the probable cause:

L6PODHD5SE64.sys Fri Aug 21 18:13:56 2015: Line6 POD HD500x Guitar Floor Multi-Effects Pedal please update if possible:
Line 6

Post any new dump files.
 


#20
There isn't a more recent driver version than the one I have. :(

Thanks anyway.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top