BSOD at Win 7 start up

Skirmantas

Honorable
Feb 27, 2013
16
0
10,510
Hey community,

I've built a new pc one week ago, and it managed to deal with maybe 20 BSOD while booting up. Just don't know what to say. PC parts are really good, I consulted with a pc technicians here and in my local pc shot before assembling it.

My short PC summary:

CPU: Intel Xeon E3-1231 v3 @ 3,4Ghz
RAM: Cant remember correctly the model, but it's Kingston BeastX (maybe), running @ 1600Mhz, 16GB (2x8GB)
Mobo: Asus H97 PRO4
GPU: MSi GTX 970 4GB Gaming edition, running at 1114 Mhz
PSU: Corsair RM550
SSD: Samsung 850 Pro
HDD: Seagate Barracuda 7200.14 3TB

First of all, all drivers are up to date. Each component is updated on the system! Including GPU, which runs latest 347.52 driver. The system runs really well, I don't get BSOD while working or playing, runs smoothly. No performance drop, no lag, no temp rises, but the problem is booting up. Sometimes you hit turn on button and PC rapidly boots up in 4-5 sec, but something when there should appear welcome window, the screen is blank black, maybe pc thinks for a sec or two and BSOD appears, saying:

----------------------------------------------------------------------------

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: nvlddmkm.sys



If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000116 (0xfffffa8011e33010, 0xfffff88005c22978, 0x0000000000000000,
0x0000000000000002)

*** nvlddmkm.sys - Address 0xfffff88006553134 base at 0xfffff88005ae4000 DateStamp
0x54d3b001

----------------------------------------------------------------------------

To make sure, I've read that Samsung SSD is not really well performing with RAPID mode on. At least not reliable, so it's turned off. I just don't know what to do. I thought at first, maybe it's really broken GPU, but if it would be problem, it didn't show anything at first place, or I would be getting glitches and etc, but I dont. It runs really well. Amazing GPU.

Please, if you dealt with something similar, and found a solution, can you help me out?

I appreaciate any comment. Thanks.

Skirmantas
 
Update:

--------------------------------------------------

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: dxgkrnl.sys



If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000116 (0xfffffa80115a64e0, 0xfffff88005bac978, 0x0000000000000000,
0x0000000000000002)

*** dxgkrnl.sys - Address 0xfffff880064dd134 base at 0xfffff88006480000 DateStamp
0x539e411c

------------------------------------------------------------

This is a message that shows bluescreen viewer software after loading today's minidump file. The thing is - the information doesnt match that one I actually got during BSOD, which was saying the message I posted above, related to nvlddmkm.sys.
 

TRENDING THREADS