Bsod even while re-installing windows

Toggle sidebar Toggle sidebar
R

Raphaeloper

Prominent
May 13, 2017
7
0
510
So... First things first, here's the link to the dumps: https://drive.google.com/file/d/0B3fb6j6UhGJkY0dmWjh3SmRpVnM/view?usp=sharing
And here's the analysis WhoCrashed gave me:
On Sun 21-May-17 08:54:12 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052117-5171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xD1 (0xED66, 0xFF, 0x2A, 0xED66)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sun 21-May-17 08:54:12 PM 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: 0xD1 (0xED66, 0xFF, 0x2A, 0xED66)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sun 21-May-17 08:50:45 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052117-4578-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xD1 (0x5C19, 0xFF, 0xE9, 0x5C19)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sun 21-May-17 08:27:56 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052117-4734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xD1 (0x2D66, 0xFF, 0x41, 0x2D66)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sun 21-May-17 07:39:37 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052117-4718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xD1 (0x4D66, 0xFF, 0x8A, 0x4D66)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.

Now with the problem itself: I've got a pretty decent pc (will post specs if needed), and since like 3 months after i bought it, i had these BSoDs: kmode_exception_not_handled, DRIVER_IRQL_NOT_LESS_OR_EQUAL, IRQL_NOT_LESS_OR_EQUAL I went to the store with a request to fix it, they told me they haven't found anything, but the Blue Screens came back... and so the cycle repeated for something like 5 times. And then, for awhile, it ran with no problems. But recently(1.5 years after purchase), it returned. I tried updating drivers, ran memtest (nothing found), ran verifier(found faulty drivers, uninstalled, but the problem persisted), re-installed windows, but it was crashing while i was installing it. I'm pretty sure that it's no physical damage.
Please, if anyone can help, i'll be really thankful. I'm really hopeless
 
Sort by date Sort by votes
IRQ not less than or equal, whether it mentions driver or not, is normally a driver error. I can't read the dumps but hopefully someone who can will show us more.

when are dumps from? before or after install? They are all driver errors (they say that) and they blame the usual victim, Windows.
ntoskrnl = new technology operating system kernel. Brains of windows 10, looks after memory management and driver requests
ntkrnlmp.exe is also part of the kernel, I just don't know meaning of last 3 initials.

So is windows on PC or you kept getting bsod? Normally i would blame memory for bsod during install but you say you tested that. Did you remove all non essential hardware while installing? so extra USB devices, or 2nd GPU (if that is case)?

its possible its the USB drive you are using

what are specs of PC?
 
Upvote 0 Downvote

Specs:
http://imgur.com/a/vm9sc
Dumps are from, sadly, after the installation, but as you pointed out, i didn't remove any non essential hardware, my bad. Will try again if the problem will come back and i'll have to re-install windows again. Does that include keyboard and mouse?

 
Upvote 0 Downvote
keyboard/mouse are essential as its hard to do anything without them.

i hope someone comes along who can read dumps. If no one does, you can read the posting instructions on the next link and ask on there as they have more people who can read them - https://www.tenforums.com/bsod-crashes-debugging/
 
Upvote 0 Downvote


You not only one who wished they understood it :)
I am self taught so some of this is a mystery to me as well. I wonder if there is a tutorial anywhere, I can only do so much by reading them. Johnbl seems to be able to pull a list of drivers out of these dumps

I am curious, do you do this on the files?
Use !analyze -v to get detailed debugging information.
Click to expand...

@Op I would post on tenforums and see how they go. They know how to read these dumps, and recently they all seem to blame memory corruption.
 
Upvote 0 Downvote

Should I just copy-paste the post?
 
Upvote 0 Downvote
You not only one who wished they understood it :)
I am self taught so some of this is a mystery to me as well. I wonder if there is a tutorial anywhere, I can only do so much by reading them. Johnbl seems to be able to pull a list of drivers out of these dumps

I am curious, do you do this on the files?
Click to expand...
Colif, yes I usually right click on the !analyze -v option and open it in a new window. Sometimes have to hit the start button, sometimes it takes 3 or 4 minutes to run and gather the info. I've only recently started looking around for more info in the debugger, I will continue to try to learn with it too. Actually I just learned a lot more, maybe not really helpful but its a start. Fast forward up to 3:25 and you'll get a basic look of how it works. https://www.youtube.com/watch?v=s5Vwnmi_TEY

Raphaeloper, sorry I couldn't help. Do as Colif said and try the tenforums (or maybe someone else will show up and help).
 
Upvote 0 Downvote
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom