Daily BSOD crashes.

BMTS

New Member
I've been getting BSOD crashes increasingly for the past couple of months, it started out as a couple times a month, and now its multiple times a day. Mostly UNEXPECTED_STORE_EXCEPTION and CRITICAL_PROCESS_DIED.
I don't know if this is relevant, but i replaced my hard drive a couple months back after i ran crystaldiskinfo and found it to be damaged, i've checked and my current hard drive is healthy. Any help would be much appreciated.
 

Attachments

kemical

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

Use !analyze -v to get detailed debugging information.

BugCheck 154, {ffffc88a9b77b000, ffffb40bfc776390, 2, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware_disk

Followup:     MachineOwner
Code:
FAILURE_BUCKET_ID:  0x154_c0000006_c00000c0_IMAGE_hardware_disk
Hi,

when you changed drives did you perform a clean install or use a back up?

File scans
Find command prompt in the start menu, right click on it and choose 'run as admin'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

Run the Store troubleshooter for apps:
Run troubleshooter

Also I couldn't see any chipset or SATA drivers in the driver stack although that doesn't necessarily mean they aren't there.

Your motherboard support page has recent updates available. Please install chipset and SATA drivers (Intel Rapid Storage Technology Driver)

B150M PRO GAMING Driver & Tools | Motherboards | ASUS United Kingdom

Your bios also has an update pending although if your not happy about flashing it yourself leave it for another day.

Post any new dump files.
 

BMTS

New Member
Hey Kemical, thanks for your help.

So, I ran the file scans and got nothing unusual (everything came back healthy/successful).
Ran the store troubleshooter and got an error the first time telling me to reset crashing apps (but didn't tell me which apps were crashing) ran it a couple more times and got no errors.
I've installed the chipset/SATA drivers.
I would prefer not to update my bios unless it is absolutely necessary so i have put that off.
That's all for now, I will update you with any new crash dumps.
Oh, and i preformed a clean install when i replaced my hard drive.
 

BMTS

New Member
So i haven't gotten any crash dumps, but my pc has started to freeze and crash with no blue screen (just immediately turn off). I ran crystal disk info and it appears my new drive has also been damaged. I am assuming that the BSODs were caused by my HDD failing. Is there anyway i could figure out what may be causing my hard drives to fail. Thanks for your help again.
1534200201113.png
 

BMTS

New Member
Ok, so i ran seatools and got no issues, then i decided to run crystaldiskinfo again just cause that was weird and crystaldiskinfo says my hard drive is healthy again. This is very confusing as from my limited knowledge hard drives don't usually bounce back from being damaged. I have not had the opportunity to test the drive in a different machine.
 

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
Sounds more like a failing controller on your board. Or just an odd driver conflict.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Ok, so i ran seatools and got no issues, then i decided to run crystaldiskinfo again just cause that was weird and crystaldiskinfo says my hard drive is healthy again. This is very confusing as from my limited knowledge hard drives don't usually bounce back from being damaged. I have not had the opportunity to test the drive in a different machine.
Which is why I mentioned about two drives failing one after another, this is rare and may indicate something else is actually going on.

It might even be the case the Crystaldisk is giving you false information. As a tool for checking hard drives it's hardly conclusive and your better off checking the drive in question using either chkdsk or Seatools.

Lastly when you changed the drive did you fit a new cable too? Might be worth attaching a new one if you have a spare lying around. Oh, and I'd try plugging into a different SATA port and see if that helps.
 

BMTS

New Member
Also when i checked resource monitor on startup, i noticed this and i'm not sure if its normal or not. it went away after a couple mins
1534378025862.png
 
Last edited:

kemical

Windows Forum Admin
Staff member
Premium Supporter
I checked on 'software reporter tool.exe' and it apparently belongs to Chrome:
How to disable Google Chrome Software Reporter Tool

It does look like from the dump file below that your pagefile is corrupt.

I read the link you sent and I think you'd be better served changing it back to the recommended amount.

First though, to clear the corrupted pagefile, turn the pagefile off and reboot.

Type the recommended Pagefile figure into both boxes so Windows has access to the full pagefile straight away.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3f, f57c, ed104183, 1c028621}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

*** Memory manager detected 1 instance(s) of corrupted pagefilepage(s) while performing in-page operations.
 

BMTS

New Member
I did the pagefile thing, didn't help so i clean installed windows and it also didn't help. I've gotten 3 new BSODs and my pc has also started randomly turning off with no warning. I'm kinda running out things to try here, any help would be greatly appreciated.
 

Attachments

kemical

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {6001, ffffffffc000000e, 24b50000, ffffd70f62616ed0}

Probably caused by : memory_corruption ( nt!MmStoreProbeAndLockPages+10d2b7 )

Followup:     MachineOwner
Hi,
can you run a couple of scans please. Open an admin command prompt and type:
chkdsk /r
Press enter and you may need to reboot to initiate the scan.

The above command will search for and if possible repair any broken sectors.

Please run a memtest86 scan. I know from experience that harddrive errors can actually be the memory that's at fault and vice versa.

The following guide will help you set up and run memtest86 either via USB or disk:
How to Test PC RAM with MemTest86

Lastly don't forget about the bios update. I know your not happy about flashing the board but I'd still keep it as a last option.
 

BMTS

New Member
Ok, so i ran both chkdsk and memtest, chkdsk took like 3+ hours, and was stuck at 10% for a while, but it didn't give me any errors, and memtest i ran overnight and got 0 errors over 11 passes. I did however get another BSOD after i used my pc for a little while (after chkdsk scan, but before memtest)
 

Attachments

BMTS

New Member
Here are my chkdsk results also:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
187392 file records processed.
File verification completed.
6661 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
6376 reparse records processed.
256876 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
6376 reparse records processed.

Stage 3: Examining security descriptors ...
Cleaning up 535 unused index entries from index $SII of file 0x9.
Cleaning up 535 unused index entries from index $SDH of file 0x9.
Cleaning up 535 unused security descriptors.
Security descriptor verification completed.
34743 data files processed.
CHKDSK is verifying Usn Journal...
36645560 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
187376 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
214565843 free clusters processed.
Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

976131071 KB total disk space.
117435952 KB in 141732 files.
109684 KB in 34744 indexes.
0 KB in bad sectors.
322059 KB in use by the system.
65536 KB occupied by the log file.
858263376 KB available on disk.

4096 bytes in each allocation unit.
244032767 total allocation units on disk.
214565844 allocation units available on disk.

Internal Info:
00 dc 02 00 67 b1 02 00 e6 a1 05 00 00 00 00 00 ....g...........
54 00 00 00 94 18 00 00 00 00 00 00 00 00 00 00 T...............

Windows has finished checking your disk.
Please wait while your computer restarts.
 

kemical

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

Use !analyze -v to get detailed debugging information.

BugCheck 154, {ffff9c043896a000, ffffcf8030e85550, 2, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware_disk

Followup:     MachineOwner
The dump file is pointing to the disk as the cause of the issue even though it's tested ok.

Can you check the Device manager and see if any yellow marks are around.

Is it possible for you to get a local PC store to help you with the bios flash as there are a number of compatibility updates?

If the bios flash still doesn't stop the bsod then you could be looking at a hardware issue.

Something else you could try to see if it is actually a driver causing the problem. Run whats called the driver verifier.

First you'll need to create a recovery usb/disk as the verifier can on occasion cause a boot loop. If it does this then you use the recovery drive to boot from, enter safe mode and turn the verifier off.
https://support.microsoft.com/en-gb/help/4026852/windows-create-a-recovery-drive

Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista
 

BMTS

New Member
Ok, so I've updated my BIOS. I did however get another blue screen before i updated it. I'll run the driver verifier and get back to you. Thanks again for your help.
 

Attachments

kemical

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

Use !analyze -v to get detailed debugging information.

BugCheck 154, {ffff8f8c68388000, ffffe784ff31dfb0, 2, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware_disk

Followup:     MachineOwner
Hi,
same bugcheck as before.

If you find the machine doesn't bsod after the bios flash then I wouldn't bother with the verifier but see how you go.
 

BMTS

New Member
Alright so after updating my bios, and turning on driver verifier my pc just suddenly turns off, and says "power surge detected" on the next reboot any time i do something. I think i am just going to turn the surge protector off, as my sockets themselves are also surge protected.
 
Top