BSOD Windows 7 64bit Brand New Custom Built Computer

Toggle sidebar Toggle sidebar
Forever1337

Forever1337

Reputable
Apr 9, 2015
32
0
4,540
Ok so I just built this system and have checked and rechecked that everything is together right (keep in mind this is not my first rodeo at all when it comes to building computers I run a repair shop). I have run ram tests overnight on the one stick of ram 12 hours and it tested good. Hard drive is a western digital 1TB it has tested fine as well. Intel processor diagnostic tool says processor is fine. All my drivers are up to date per ASUS website. I have wiped the hard drive and reinstalled windows again, what I did notice is that windows did not blue screen for two days and the only thing I had not done was windows updates. I had installed all my programs, drivers and printers with no problems then I do windows updates and back to the same BSOD error.
PLEASE HELP!

BSOD error 0x0000001A (0x0000000000041790, 0xfffffa8000b3fb20, 0x000000000000ffff, 0x0000000000000000)

System specs:
i3-4150
ASUS B85M-G R2.0 Motherboard
1 8GB Patriot DDR3 1600 PSD38G16002H
WD green 1TB HDD
450W Antec VP450F Power supply
LG DVD Burner
Windows 7 SP1 x64 install disk
 
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
your system has a map that it keeps that tells it what is currently in memory and what is swapped to your pagefile.
Something corrupted the map and the system detected it and shut down.

you might consider: start cmd.exe as an admin, run the command
verifier.exe /standard /all

Reboot and see if the verifier detects any driver that is corrupting your memory. If it does then it will force a bugcheck and name the driver in the minidump.

use
verifier.exe /reset
to clear the verifier flags after you are done testing or your machine will run slowly until you do.

it is often useful in these cases to change your memory dump type to kernel as it will include internal error logs and extra debugging info that can explain why the system called the bugcheck.
it will also change the memory dump file name and location to c:\windows\memory.dmp and the memory dump file will be much larger.
 
Upvote 0 Downvote
Forever1337

Forever1337

Reputable
Apr 9, 2015
32
0
4,540


Please let me know how to change the memory dump type to kernel and what to do with it? I did what you said up above aside from changing to kernel just don't know what to do now. I have no idea on how to do anything with a .dmp file. Also had a new BSOD happen just after upgrading to the newest Intel graphics driver off intel's website.

0x000000c1 (0xfffff98020d96Fco, 0xfffff98020d969ba, 0x0000000000878040, 0x0000000000000032)

I am beginning to wonder if it isn't intel graphics driver causing the problems because windows update did do that as well...
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
I think you have verifier on and it detected a corruption and should name the driver.
the corruption it detected was:
A driver freed an address, but nearby bytes within the same page have a single bit error.

it could be a bug in the new driver or a hardware problem (assuming you are not overclocking anything)
-------------
how to change memory dump type:
https://www.sophos.com/en-us/support/knowledgebase/111474.aspx

if you change it to kernel memory dump then the file will be in:
c:\windows\memory.dmp
Note: reboot after you make the change.
mini memory dumps will be stored at:
c:\windows\minidump directory with .dmp file extension.

you can put your memory dmp file on a server like microsoft onedrive and post a link.



 
Upvote 0 Downvote
Forever1337

Forever1337

Reputable
Apr 9, 2015
32
0
4,540
Just wanted to give a update. It would appear that the updated Intel Drivers that Windows Update installed was the problem, and the updated drivers off Intel's website actually made things worse. I reverted back to the drivers that came with the motherboard and all seems to be good now.
 
Upvote 0 Downvote
Forever1337

Forever1337

Reputable
Apr 9, 2015
32
0
4,540
OK so here is another update. I have since had the computer blue screen again and decided that we would go to windows 8.1 because the hardware is designed for windows 8.1. It still blue screens in windows 8.1 once with memory_management as the error and once as NTFS_File_System as the error. Most updates have been donem I am stuck on one update that wont install. I am at my wits end. I have run prime 95 to stress memory and the processor with no blue screen and have run memtest86 along with windows memory test and nothing finds errors or causes crashing. I have tested the hdd and no errors were found. I really don't know what to do anymore.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom