Return to Level1Techs.com

Windows BSOD or other issue? Read here first!


#1

So I have seen a couple of threads with Windows BSOD issues, now I want to help the people who post in it but don’t know where to start.

For starters, copy and paste this line into your explorer bar “%SystemRoot%\Minidump” or “C:\Windows\Minidump”.

Zip and upload the contents of the folder to something like DropBox or MediaFire and create a new thread.

In that new thread, a quick description of hardware, anti-virus, what version of Windows, and maybe a short description of how you encounter the BSOD is possible.

Then tag the following people and we will try to help you the best we can. You can tag us for non-BSOD issues as well.
@Novasty
@Commissar
@Heimdallr
@Peanut253

If anyone else would like to be add their name to the list, just PM me and give me a small example of how you can help and I will add your name to the list. You don’t have to know how to debug BSODs, I just want to compile a list of people who can help because I am disgusted at the availability of support for Windows when people need it.

Useful tools that may help.

Update: I’ve been seeing people here use BlueScreenView to try and debug these issues. All I have to say is don’t bother, BSV isn’t reliable enough to provide any real answers. If you truly want to debug mini-dumps, learn how to use WinDBG/Sysnative.

Update2: Event Viewer does not provide enough information regarding BSODs. Event Viewer provides a shit ton of information leading up to the BSOD. Only use the Event Viewer to assist in debugging the issue, IT DOES NOT PROVIDE ENOUGH INFORMATION TO GIVE A CONCRETE ANSWER. (Someone tried to solve a BSOD with event viewer and it pissed me off)


Laptop bsod driver power state failure
SSD Migration Issue New SSD keeps going BSOD. Old one works fine
pinned #2

#3

Just for the record I do have the necessary software to read the windows code and debug errors .. SO feel free to tag me any time.


#4

Contents of %SystemRoot%\Minidump\

Hey all who could possible assist me,

I've been having some recent BSOD issues and I'm not particularly comfortable with trouble shooting this by myself, so i figured i'd use the internet to my advantage.

This is from a post on r/techsupport I made

Reddit post

" BSOD Mini Dump analysis

My system specs are 3770k p8z77-v Deluxe 8gb Geil 1600 DDR3 Gtx 780ti 120gb hyperx 3k Random hdd 750 watt seasonic gold PSU

This has started to happened recently, I have not really installed any new software that i think would effect anything. No hardware changes or anything of that nature. The problems that i have been having don't seem to be related to any thing that i am doing on my computer, most of the time ill have come back to my computer after a few hours and the blue screen had happened at some point. I'd really appreciate any type of help.

Thank You,
Carter "

So again I'd really appreciate any help

@Novasty
@Dynamic_Gravity
@NJM1112
@Commissar
@R00tz31820

And i hope everything is formatted properly and in the right place


#5

@novasty can you toss this to a new thread please.
@carter9996 i need you to umpload the .dmp files. i use a more advanced program for analysis


#6

The dmp files should be in the first clickable link called

Contents of %SystemRoot%\Minidump\

It should be a 7z in Dropbox


#7

Hello, I wonder whether you could help me?

I have been having intermittent BSOD on windows 10 64bit on my new pc:

i7 6700k
H100i GTX
EVGA Z170 FTW
16gb Corsair lpx ddr4
GTX 980 ti FTW

I have saved the mini dump files and got them analysed

Could somebody more knowledgeable than me take a look and see if, hopefully, there is a solution?

On Thu 31/03/2016 12:38:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033116-4734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x1A (0x41793, 0xFFFFF68003587F18, 0x4, 0x3)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 31/03/2016 12:38:53 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41793, 0xFFFFF68003587F18, 0x4, 0x3)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 29/03/2016 14:03:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032916-5625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802C60C9F0F, 0xFFFFD00021D96C10, 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 Mon 28/03/2016 23:24:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032916-3500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000026BC8, 0x2000000000000000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 28/03/2016 23:09:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032916-2828-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xEF5E)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8010489EF5E, 0xFFFFD00122D39CF8, 0xFFFFD00122D39510)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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.


#8

okay, you need to post a new thread,. and follow the instructions. but start with a memtest. ANY errors means you got bad ram


#9

Been having some BSOD problems:

http://www.mediafire.com/download/uaxkncdicb8598m/Minidump%282%29.rar

Guessing it might be a problem with my RAM but not sure

@R00tz31820
@Novasty
@Dynamic_Gravity
@NJM1112
@Commissar


#10

new thread please