Any solutions for these problems after building my new computer?

AustnW

Honorable
Jun 25, 2013
128
0
10,690
So I just recently built my first computer. It's been almost a month since completing it. It's been great so far except for a few "minor" problems. It would mean a lot if you guys could help me solve them as they interrupt the overall enjoyability of the computer. For reference I have Windows 8 and have not experienced any problems with it on my, now, old computer.

1. The first one is I've encountered two BSOD's recently while using the computer.

The first error came up about a week ago. It was a DRIVER_CORRUPTED_EXPOOL error. I installed a new mouse the day before, so I checked the drivers and found out I was using an out-of-date driver. So I updated it to the newest one. That error has not popped up since.

The second error just happened today (which actually made me post this thread). The error this time was a SYSTEM_SERVICE_EXCEPTION error. I looked it up and saw it might be caused by the system's RAM or a bad memory slot. I performed the built in "Diagnose your computer’s memory problem" test in Windows. It didn't find anything so I'm not quite sure what to do now.

2. The second problem I've been having continuously lately is that the computer has been freezing up for 10-15 seconds periodically. This usually happens when I am using Google Chrome (but like I said I have not had any problems like this while using Chrome on my older computer). I usually have Skype and BitDefender running in the background as well. Most of the times when this freezing has occurred I've also had World of Tanks opened up on my second monitor as well, but it also happens when it's not opened. The freezing sometimes occurs a little after boot-up as well. I'm not quite sure what it might be caused by. I've ruled out the new HDD because I used it for about 1-2 months on my older computer before putting it into my new one and it worked perfectly. So I'm thinking that it might either be the GPU or RAM. I'm not sure what action to take though.

3. The third problem happens in the morning at boot-up. I boot-up the PC for the first time each morning and it stays at a black screen forever until I reboot. It usually boots up normally after rebooting it, but sometimes needs to be rebooted a second time. The computer may or may not get to the motherboard logo before hanging at the black screen. Most of the time it doesn't show the logo though. I posted a question about it on here before and have gotten a response to turn off the Windows Boot Manager in the BIOS. Well I tried going in there to turn it off, but when I disable it and put the HDD as the primary boot device, it doesn't boot at all. So I am open to any other suggestions. Also, this ONLY happens in the morning, if I reboot the computer during the day after usage, it reboots fine. It seems to only happen after being off for a good amount of time.

Any help on these problems would be hugely appreciated as I would like to fix them so I can fully enjoy my newly built computer. Thank you!

EDIT: Forgot to mention that all of this was after a clean re-install of Windows, which also makes me believe it is a hardware related issue.
 
Solution
hmmm sound i had a simlar thing going on before with my laptop somtimes windows 8 can have probelms with hardware try a clean renistal and if that doesent work try windows 7

AustnW

Honorable
Jun 25, 2013
128
0
10,690


Oh, I also forgot to mention this was after a clean re-install of Windows. That's what's strange =/.

And I don't think I still have a copy of Windows 7 laying around. I'm not really willing to go back anyways. This seems more like a hardware related issue rather than an OS issue as like I said in the OP, Windows 8 worked perfectly fine for me on my old computer.
 

fkr

Splendid
http://www.nirsoft.net/utils/blue_screen_view.html

use this to review your own bsod reports.

this will tell you what your last running executables were and in order. this can really help with diagnostics.


if you are worried about a corrupted windows install you can sfc
http://technet.microsoft.com/en-us/library/bb491008.aspx

test your ram
http://www.memtest86.com/

run this for several passes. it will take along time so running it overnight is a good idea

edit

http://pcsupport.about.com/od/toolsofthetrade/tp/tophddiag.htm

use the one that is appropriate for your manufacturer
 

AustnW

Honorable
Jun 25, 2013
128
0
10,690


Thanks for the links! I'll try out those diagnostics later.
 

AustnW

Honorable
Jun 25, 2013
128
0
10,690


So I ran the test this morning and got this result:

5lld.png


It said I got 1 error, but I wasn't quite sure how to see what it was. Is there any way to view the error? And is 1 error enough to make one of my RAM sticks bad?
 

fkr

Splendid
I have never seen one error and your screen looks a little different than when I last remember having to run it so I reached out to a true memory expert (from what I have been told he knows everything there is to know about ram).

my computer ran 90% of the time and I had one stick that all it had were errors so I doubt that one error would kill things but check your hard drive and other things till the expert arrives

btw do you have any bsod reports to look
 

AustnW

Honorable
Jun 25, 2013
128
0
10,690


Thanks!

And where would I see the reports at?
 

fkr

Splendid
If you use this program http://www.nirsoft.net/utils/blue_screen_view.html it should automatically direct itself to where your .dmp files are at, aka bsod reports.

I use this program to take prtscn http://prntscr.com/1m8gt5 there will be a link to install this very non obtrusive piece of software in this link. you can always copy paste if you like.

the prntscn i have above is just a picture of the blue screen view software


the best thing to do is to let it run again overnight or for as long as you can to see if the issue replicates and if it the same sector and such. If there is an error in memory an rma can never hurt.
 

AustnW

Honorable
Jun 25, 2013
128
0
10,690


Okay, here's the reports:

http://img23.imageshack.us/img23/4949/pqec.png

Another BSOD must have happened when one of my family members was on the computer. That's the second one.

So it seems their all caused by ntoskrnl.exe. I looked that up and it seems to have to do with the boot.ini file. Any suggestions?
 

fkr

Splendid
If you click on each report and expand the window to full size it will show me all of the files that crashed and in what order. that way I can see the system files that broke down right before that also.

ntosknl.exe It provides the kernel and executive layers of the Windows NT kernel space, and is responsible for various system services such as hardware virtualization, process and memory management, etc., thus making it a fundamental part of the system. It contains the cache manager, the executive, the kernel, the security reference monitor, the memory manager, and the scheduler, among other things

windows nt os kernal or windows nt operating system kernal and the kernal is the most fundamental layer


cpuz download on the right side http://www.cpuid.com/softwares/cpu-z.html
 

AustnW

Honorable
Jun 25, 2013
128
0
10,690


You mean all of this?:

http://img5.imageshack.us/img5/7869/9bnu.png

There's a lot more if you scroll down. It would take awhile to screenshot it all.



7aez.png

s5fg.png


Does that cover it?
 

Tradesman1

Legenda in Aeternum
Okay, think taht's enough - haven't read everything above, (too much going on) anyway, make sure you have the latest BIOS, then put the sticks in slots 1-3, boot into BIOS, enable XMP and select profile 1, then go to DRAM voltage and change to 1.55, then find CR (command Rate or command timing) it currently shows as 1T make sure it's in as 2T - then give it a try
 

AustnW

Honorable
Jun 25, 2013
128
0
10,690


Darn, I hope it wouldn't come to this. Unfortunately I have the Noctua NH-D14 as my CPU cooler, so switching RAM to different slots isn't the easiest thing in the world with the cooler, it has to be removed first. If you truly think it will fix it though, I will give your instructions a go tomorrow morning.

Thanks for your help btw.
 

fkr

Splendid
i only really needed to see the top few i just wanted to be sure. if more than one was highlighted on the bottom then they all crashed in sequence but only your top one was highlighted so nothing else went wrong. If you are curios the hal.dll is the hardware abstraction layer which kinda separates the CPU from other things to decrease issues and it also plays a role in i/o operations for the pcie lanes. the kd.dll is the kernel debug layer. .dll is just a dynamic link library which means it link to the library of instructions that are understood by your computer and it contains: code, data, and resources.

so blah blah blah and usually what this means is that the ram is having issues and what tradesman is saying to do is exactly what should be done. not to mention your ram has been running slower than it should have been. your ram has been running as 1333 when it is 1600MHz ram

the switching of the slots is just to rule out that you do not have a bad RAM slot on your motherboard I believe.
 

AustnW

Honorable
Jun 25, 2013
128
0
10,690


Yeah, that's the only item that was highlighted on all three BSOD's.

And I didn't know that my RAM was only running at 1333, how can you tell from those pics?
 

AustnW

Honorable
Jun 25, 2013
128
0
10,690


Oh, okay. I didn't know that you double it.

So you think it would solve anything if I would just increase it to 1600 and up the voltage to 1.55?
 

AustnW

Honorable
Jun 25, 2013
128
0
10,690


So I tried putting it on the XMP, but it still stays at 1333MHz even though it says it's on Profile1 and the mulitplier is at 16.
 

fkr

Splendid
that is what it says in the bios when picking the xmp profile one setting. You can always manually put in those setting in the bios also(the ones seen in cpuz spd tab). any chance for a bios screenshot. what is your motherboard also.