Quite random BSOD new build

Toggle sidebar Toggle sidebar
M

maurovid

Reputable
Sep 20, 2014
12
0
4,510
So I built my first rig about 2 months ago (all new components except for hdds and optical -wich I don't use anyway-) and since then three times I've had a BSOD in quite random moments. Here's a pic I could take from the last one.

WP_20150203_002.jpg
[/url] free photo upload[/img]

After the BSOD, the PC will restart and work just fine.

I guess I have to check for driver updates but I think I had that OK.

Also my specs are:

MOBO: Gigabyte Z97x-Gaming 3
CPU: Intel i7 4970 + Cooler Master Hyper 212 EVO
RAM: Kingston HyperX Beast 2 x8gb
GPU: Sapphire Amd Radeon r7 250
PSU: XFX XTR 850w

Any way I can know more less accurately what the problem is?
Thanks!
 
Solution
J
windows loads drivers in a different order on each boot. So, yes the same problem can cause different drivers to fail in different ways. A "bad" spot in memory will corrupt different drivers on each boot. A bad driver will corrupt the data of the driver next to it and that can be different on each boot.

you should still be able to boot when running verifier, you might bugcheck on boot but you want to get a bugcheck so it will write a memory dump. You would then do a safe mode boot and turn off verifier.exe with the /reset switch.
(verifier.exe /reset) then you would have the memory dump to analzye.

if you have a memory .dmp I would put it on a server and post a link. it is just faster to look at it and see what windows thinks...
Sort by date Sort by votes
M

maurovid

Reputable
Sep 20, 2014
12
0
4,510
I'm still having this problem.

ran chkdsk - nothing
ran memtest86 - nothing

Kept getting BSODS (it may take 2-3 weeks for it to crash, so it's hard to tell if I've solved the problem)

Two days ago I removed the RAM sticks and cleaned both them and the sockets (everything was brand new when I installed it like 4 months ago, but still), ran memtest again. First for 7hs, then for 10hs - no errors.

Here's a screen of BlueScreenViewer


I'm quite lost here, don't know how to identify the problem.



 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
the error sub code was : 0x41790
A page table page has been corrupted.

something overwrote a table in the OS or you have problems with your pagefile.sys

I would update any storage drivers, remove any overclocking. delete your pagefile.sys (turn off virtual memory, reboot, make sure the hidden pagefile.sys gets deleted or rename it to pagefile.old ,turn on virtual memory and reboot.

you could also start cmd.exe as an admin then run
verifier.exe /standard /all
then reboot and see if verifier finds a bad driver and forces a bugcheck.
use verifier.exe /reset to turn off driver verification.

otherwise I would put the saved memory dump .dmp file on a server and post a link
 
Upvote 0 Downvote
M

maurovid

Reputable
Sep 20, 2014
12
0
4,510
I will do all this, thanks. However what concerns me is that since I've built my rig, I kept getting different blue screens. Is it likely that all different errors are caused by the same issue?

PS: I have already ran driver verifier and then became unable to boot (got stuck at the black screen before windows logo) unless I did it in Safe Mode. How do I know if driver verifier finds a bad driver and where do I find the bugcheck?
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
windows loads drivers in a different order on each boot. So, yes the same problem can cause different drivers to fail in different ways. A "bad" spot in memory will corrupt different drivers on each boot. A bad driver will corrupt the data of the driver next to it and that can be different on each boot.

you should still be able to boot when running verifier, you might bugcheck on boot but you want to get a bugcheck so it will write a memory dump. You would then do a safe mode boot and turn off verifier.exe with the /reset switch.
(verifier.exe /reset) then you would have the memory dump to analzye.

if you have a memory .dmp I would put it on a server and post a link. it is just faster to look at it and see what windows thinks the problem is.



 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom