Jump to content

Hey,
At the end of 2016 I built a computer for the first time, that went well.
After a month (barely used) I suddenly could not play games on the computer anymore.
As soon as I was in a game for a while (4 ~ 5 minutes) the computer crashed.
I get a BSOD with the error code "unexpected_store_exception" (ntoskrnl.exe according to bluescreenview).

 

Specs:
Windows 10 x64
Intel Core i5 6400

Asrock h110m-hds

Gigabyte gtx1050

8GB ram from Crucial (Compatible with the manufacturer of the mobo)

 

(I've no idea why this is Dutch, the system language is English. But "Geslaagd" means "Succesful")

report.html

Link to comment
https://linustechtips.com/topic/897092-unexpected-store-exception/
Share on other sites

Link to post
Share on other sites

7 minutes ago, Sjoerrdd said:

Hey,
At the end of 2016 I built a computer for the first time, that went well.
After a month (barely used) I suddenly could not play games on the computer anymore.
As soon as I was in a game for a while (4 ~ 5 minutes) the computer crashed.
I get a BSOD with the error code "unexpected_store_exception" (ntoskrnl.exe according to bluescreenview).

 

Specs:
Windows 10 x64
Intel Core i5 6400

Asrock h110m-hds

Gigabyte gtx1050

8GB ram from Crucial (Compatible with the manufacturer of the mobo)

 

(I've no idea why this is Dutch, the system language is English. But "Geslaagd" means "Succesful")

report.html

Any hardware, driver, or major software changes? Usually one of the main culprits for bluescreens.

Spoiler

My main desktop, "Rufus":

Spoiler

PC Specs:

CPU: AMD Ryzen 5 1600

CPU Cooler: Cooler Master MasterLiquid Lite 120

RAM: 2x8gb Corsair Vengence DDR4 Red LED @ 3066mt/s

Motherboard: MSI B350 Gaming Pro Carbon

GPU: XFX RX 580 GTR XXX White 

Storage: Mushkin ECO3 256GB SATA3 SSD + Some hitachi thing

PSU: Seasonic Focus Plus Gold 650W

Case: Corsair Crystal 460X

OS: Windows 10 x64 Pro Version 1607

Retro machine:

Spoiler

PC Specs:

CPU: Intel Core 2 Quad Q9550

CPU Cooler: Stock heatsink

RAM: GSkill 4gb DDR2 1066mt/s

Motherboard: Asus P5n-e SLI

GPU: 8800 GTS 640mb, I swap between that and my 8800 GTS 512mb

Storage: Seagate 320gb right from 2006

PSU: Ultra 600W 

Case: Deepcool Tesseract SW

OS: Windows XP SP3 32-bit, Linux Mint 18.2 Cinnamon 64-bit, Manjaro Deepin x64 (sorta)

Mac Pro Early 2008: Dual Xeon X5482s w/ 32GB RAM & HD 5770 running macOS High Sierra

More PC's

 

Link to post
Share on other sites

18 minutes ago, Sjoerrdd said:

Hey,
At the end of 2016 I built a computer for the first time, that went well.
After a month (barely used) I suddenly could not play games on the computer anymore.
As soon as I was in a game for a while (4 ~ 5 minutes) the computer crashed.
I get a BSOD with the error code "unexpected_store_exception" (ntoskrnl.exe according to bluescreenview).

 

Specs:
Windows 10 x64
Intel Core i5 6400

Asrock h110m-hds

Gigabyte gtx1050

8GB ram from Crucial (Compatible with the manufacturer of the mobo)

 

(I've no idea why this is Dutch, the system language is English. But "Geslaagd" means "Succesful")

report.html

Some troubleshooting steps I recommend you follow next:

 

1. Disable any overclocks.

2. Do a CHKDSK scan: https://windowsinstructed.com/run-chkdsk-windows/

2. Open a command prompt with administrative privileges, type sfc /scannow and hit enter.

4. Reseat your ram.

5. Open device manager and see if anything has a yellow warning next to it, then try to update that driver.

6. Verify your drivers with driver verifier: http://www.thewindowsclub.com/windows-driver-verifier-device-manager

7. Hit start, type reliability history, and look for red and yellow warnings when this occurred. This can give you clues. Maybe a windows update or driver update failed. This will show as a yellow warning. Many bluescreen errors and other errors will show under the red warnings. Those that don't show up in your event viewer.

Link to post
Share on other sites

On 16-2-2018 at 5:20 PM, stateofpsychosis said:

Some troubleshooting steps I recommend you follow next:

 

1. Disable any overclocks.

2. Do a CHKDSK scan: https://windowsinstructed.com/run-chkdsk-windows/

2. Open a command prompt with administrative privileges, type sfc /scannow and hit enter.

4. Reseat your ram.

5. Open device manager and see if anything has a yellow warning next to it, then try to update that driver.

6. Verify your drivers with driver verifier: http://www.thewindowsclub.com/windows-driver-verifier-device-manager

7. Hit start, type reliability history, and look for red and yellow warnings when this occurred. This can give you clues. Maybe a windows update or driver update failed. This will show as a yellow warning. Many bluescreen errors and other errors will show under the red warnings. Those that don't show up in your event viewer.

1. Nothing is overclocked

2. Windows successfully scanned the drive. No errors were found.

3. "Windows Resource Protection could not perform the requested operation."

4. Done
5. There are no drivers with a yellow warning next to it

6. "No unsigned drivers have been found."

7. (see screenshot. When I click on "Check for a solution", i'm getting a message that there is no solution).5a88792ba61bb_ReliabilityMonitor.png.86fb3d46046c7c2a7ea22a475b870f45.png

Link to post
Share on other sites

On 2/17/2018 at 2:49 PM, Sjoerrdd said:

1. Nothing is overclocked

2. Windows successfully scanned the drive. No errors were found.

3. "Windows Resource Protection could not perform the requested operation."

4. Done
5. There are no drivers with a yellow warning next to it

6. "No unsigned drivers have been found."

7. (see screenshot. When I click on "Check for a solution", i'm getting a message that there is no solution).5a88792ba61bb_ReliabilityMonitor.png.86fb3d46046c7c2a7ea22a475b870f45.png

See those yellow markers in your reliability history?

Check what those say.

Usually those are failed windows updates.

If you find an update that failed, go into your windows update history, find that update, uninstall it, and install it again.

 

Oh, and it's really weird that sfc /scannow didn't work. That always works. Did you right click CMD and click "run as administrator" first?

 

Link to post
Share on other sites

  • 2 weeks later...
On 21-2-2018 at 2:06 PM, stateofpsychosis said:

See those yellow markers in your reliability history?

Check what those say.

Usually those are failed windows updates.

If you find an update that failed, go into your windows update history, find that update, uninstall it, and install it again.

 

Oh, and it's really weird that sfc /scannow didn't work. That always works. Did you right click CMD and click "run as administrator" first?

 

Indeed, it are failed updates.

It's indeed really weird that sfc /scannow doesn't work...

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×