BSOD on a brand new system, collecting error messages

[Dritzo]

Hello people,

There are allot of topics involving BSOD and the errors I've been having but I also read multiple times that not all solutions aply to the same system. So I decided to post here.

I've bought a new system about a month ago and honestly I've been having problems with it since the beginning. I was told that a digital version for windows 10 was installed on the SSD disc.
But on my first-time setup it kept booting in bios.
I was kind of excited about me new pc so I downloaded a windows 10 iso on my old pc and decided to reinstall windows 10 on my new rig.

After manually transferring some drivers to get my internet working i got the system going. Updated all my drivers, and decided to test a game. This is when I got my first error and BSOD.
Most of the internet suggestions involved something around my HDD or SSD or drivers.

So first I checked all my drivers made sure they were up to date and then tried to run the system with the HDD detached. (I haven't tried the SSD yet because I don't really wand to install windows 10 again)

Here are some of the errors I've been having (in likelihood of occurring +,++,+++):

- irql_not_less_or_equal +++
- kmode exception not handled ++
- system service exception +
- page fault in nonpaged area +++
- request msp lock +
- kernel auto boost invalid lock_release +
- memory management +

Kind of bad when I write it down like that.

The other day A friend tried to help out and we checked if none of the hardware was broken. We ran a demo of 3d-Mark and did a mem test. The only thing we could find was that my first slot for RAM is probably broken. Wich explains why my RAM was in the 2nd slot.

Lastly I've sent a email to the supplier but communications have been sloppy so I decided to post something here. It's kinda frustrating to spend so much money on a nice machine and not be able to play on it.

This is my system at the moment:

- Intel Core i7 6700K 4-Core (8 threads) 4.0Ghz (turbo: 4.2Ghz) socket 1151 6MB Skylake 91 watt
- ASUS H170 PRO GAMING (H170,S1151,ATX,DDR4,Intel) motherboard
- Inno3D Nvidia Geforce GTX980 Ti OC met 6GB GDDR5 PCI-E 2xDVI HDMI 3xDP
- 8GB (2x4GB) PC4-17066 2133Mhz DDR4 CL15 RAM Crucial
- 500GB SATA3 7200rpm 32mb HDD
- 240GB V300 Kinston SATA3 SSD
- LiteOn SATA black iHAS124 24x / DL 8x / RAM DVD multi burner
- PCI Express TP-link TL wn881ND (300MBit) Wifi Card
- Coolermaster B700 700watt80+

 

[Colif]

Most of those look like driver errors to me. kernel auto boost invalid lock seems to be tied into wifi or Bluetooth (I assume the motherboard has Bluetooth since its the next generation of my motherboard). Perhaps use a program like Driver Booster as a guide to see what it thinks is old - i wouldn't dl anything with it as it can suggest wrong drivers but its normally good for a guide. I would go look for drivers myself once it showed any.

can you download and run whocrashed: http://www.resplendence.com/whocrashed
it will look at errors and give us a summary
might show us driver names but most times it just shows windows sys files that are being blamed

Copy/paste results in here

 

[Dritzo]

Ok here it is:

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 7/31/2016 1:36:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073116-3984-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x1A5E)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80043211A5E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 7/31/2016 1:36:40 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x1A5E)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80043211A5E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 7/31/2016 3:30:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073116-4359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0xA (0xFFFFF8025DCC72ED, 0x2, 0x1, 0xFFFFF802A58472E6)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 7/28/2016 11:42:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073016-2765-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF8012C51A912)
Bugcheck code: 0x50 (0xFFFFE000DB8161B8, 0x2, 0xFFFFF8012C51A912, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 7/27/2016 3:01:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072816-4156-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0xAABF6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8009F9BABF6, 0xFFFFD00020B68340, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 7/15/2016 10:02:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071716-3765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80266691514, 0xFFFFD0002298C7C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 7/5/2016 1:00:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071516-3562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0xBE (0xFFFFFAC29F9F3CF0, 0x8000000001380121, 0xFFFFD0002476D5C0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 7/5/2016 11:24:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070516-3656-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x11A5D0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800B25365D0, 0xFFFFD0002241B1D8, 0xFFFFD0002241A9F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 7/5/2016 10:50:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070516-3765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8009A025B61, 0xFFFFD00020BE47A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 7/5/2016 9:57:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070516-3656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD4594)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80156B65594, 0xFFFFD00052E3F868, 0xFFFFD00052E3F080)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

hidclass.sys = mouse/keyboard drivers. If you have a gaming mouse or keyboard, see if you have new drivers for them

two DX errors = http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

if ram slots are broken and PC is only 1 month old, I would be getting that fixed while its still under warranty, instead of putting up with a broken part forever. You could run http://www.memtest86.com/ to make sure

July 5th looked like a fun day

 

[johnbl]

0xC0000005 is a error code that indicates a bad memory address given to a driver.

you would remove any overclocking, and run memtest to confirm your BIOS memory timings are correct and your RAM works as expected.

 

[Dritzo]

July 5th was my day off, haha

I checked my drivers for mouse and keyboard, both aren't fancy and drivers were up to date.
Deleted my drivers for Nvidea then used the software to clean up and now im installing the new
(manual) downloaded driver. Next I will check the memtest, first have to find my USB.

So far, Thx

 

[Dritzo]

SO I decided to run a game to see if there were any changes and it did crash after 10 min. or so. This time the game froze and the pc restarted, but i only got a black screen. It was like the monitor was not receiving a signal.

I'm working with a LG 21:9 Ultra wide curved monitor

 

[Colif]

doubt monitor is involved in problem, is it working yet? Are you seeing the bios flash screen at all? Any sign its trying to load windows?

if it loads bios and then blank you may need to dl the Win 10 media creation tool on another PC and make a win 10 installer on USB or DVD - its a handy boot disc if nothing else

if it shows a the bios, perhaps log into safe mode and run DDU again and remove the drivers again. You can get to safe mode by booting from installer, on the second screen after choosing languages, choose repair this pc, not install
choose troubleshoot/advanced/start up options
should be 3 choices for safe mode, choose one of them.

its odd a 9080 TI would be giving you this behaviour, its not even a new card (the new series has teething problems), does your motherboard have integrated graphics? can you attach screen to it and see if it works?

Did you run memtest on the memory sticks? not booting can also be ram.

 

[Dritzo]

Hello,

I'v been trying to run the memtest since last night. The first time it made 2 passes and detected an error but I don't have any logs since it crashed, again without blue screen just a black screen. The second time I left it running and when I returned the same thing happened. a black screen.

It doesn't show bios or anything it just shows a black screen like the monitor is off whilst the computer sounds like it starting up. Usually the only
way to stop it is to leave the machine without the power cable for a few minutes after this it usually starts windows normally.

Just now started to run the 3th attempt on memtest. I'll wright down the results....

 

[Colif]

Any error is one too many on memtest. You want no errors, so if a stick gives you any, try another until no errors. Bad ram can stop PC starting as its vital.

try other slots with the ram that shows as bad since you suspect the slots as well.

 

[Dritzo]

SO I should move my ram to say slot 3?

edit: don't know if I have a integrated graphic card. I do have one HDMI on my GPU and second near my motherboard does this mean a intergrated graphics card?

 

[Colif]

Yes, just to make sure its the ram and not the slots. Your friend may have tested ram in slot one and had a bad stick, not slot. I don't know, I wasn't there

Did you make system or buy it from someone? Its one month old, if its pre made I would get them to fix as everything in PC should be under warranty. They would be able to work out what is wrong as they have spare parts.

At this point, the problem is either your ram or the motherboard. If I had a broken slot I would be getting that fixed.

 

[Colif]

edit: don't know if I have a integrated graphic card. I do have one HDMI on my GPU and second near my motherboard does this mean a intergrated graphics card?

Yeah, you do: specs

but i don't think problem is graphics right now.

 

[Dritzo]

Here's the error from the memtest:

Error Confidence Value : 127
Lowest Error Adress: 00080038004 - 2048.2MB
Highest Error Adress: 000bcd0effc - 3021.0MB
Bits in Error Mask: ff000000
Bits in Error - Total: 8 Min: 2 Max:8 Avg:7
Max Contiguous Errors: 1

 

[Colif]

try the next stick, that ones bad

this explains the tests it runs: http://superuser.com/questions/326078/how-do-i-interpret-the-statistics-of-a-memtest-run

 

[Dritzo]

Ok I'll be back tonight to try it out have to get to work first!

 

[Ironsounds]

Hello... Any time you move/change or Test your RAM, you should do a MB/BIOs CMOS Reset between Tests.

Take your time here and be slow and careful to your MB... look in your MB manual/Pdf for pictures and location of the SW/pins. B )

1) un-plug PS from wall.
2) remove MB battery
3) place jumper pins/switch on MB to clear the capacitors... for ~1 min
4) remove Jumper/switch
5) re-install battery

Look in your manual for the correct RAM slots you want to use/test for "Dual channel" OR "single channel" operation with this MB.

6) re-move and re-seat your RAM stick(s) into the MB slots.
7) plug monitor into the MB video output OR Video card for a BOOT display, And set your monitor for that cable input.
8) plug in PS to wall
9) Boot computer.

Another very easy fast thing to do before testing RAM sticks, is to give all them small Gold contacts, a quick cleaning, with a wetted Q-Tip of Rubbing alcohol... and wipe it clean/dry with the other side... And also get a magnifying Glass, and get your eyes close to the MB Ram slots, for closer inspection of a bad slot... You might see a Dirty or Bent contact there. B /

 

[Dritzo]

Ok I'm back! I ran a second run on memtest just to make the 4 passes that's everybody talking about, and got a second error value. But It's hard to find what causes this in the article you sent me. To many numbers and it looks like hes using a different version then me.

Ive also tried to move my ram to other slots but it just gives a black screen whilst booting, one of the slots just gave a beeping sound when I installed it. SO I don't know if that works.

Last I send an email to the supplier and im still waiting for response. Whatever the problem I think they should fix it

 

[Colif]

As i said, any error value above 0 is too high. The supplier can work out the fault as I would guess they have spares and ram sticks they know works. Currently you can't tell if its ram or slots.

 

[Dritzo]

Well I'll just wait on a reply from the supplier. thanks for all the help guy(s). I know that selecting the "pick as solution" thing is a big deal on the forum but I don't really know if it applies here

But thx anyway!

 

[Colif]

Well I'll just wait on a reply from the supplier. thanks for all the help guy(s). I know that selecting the "pick as solution" thing is a big deal on the forum but I don't really know if it applies here

But thx anyway!

Wait and see if we guessed right, I guess