BSOD 0x0000001e

Boozad · 10 Jul 2014

The chances are this is a device driver causing the BSODs, although I'm not sure why the minidumps aren't being produced. I'll ask some more BSOD bods to to stop by and see if they know the answer.

doobs · 10 Jul 2014

Sounds good. I really appreciate your help

essenbe · 10 Jul 2014

In your system properties, change the Kernel dump to small memory dump and make sure the aytomatically restart is not checked. Also, go to C:/Windows/Minidump and see if there is a folder in C:/Windows named Minidump. If not, create one. Make the advanced system properties look like this.

Attachment 325037

derekimo · 10 Jul 2014

doobs said:

Sure I guess, but they always say "Unable to produce a minidump file from the full dump file." from event viewer

This is a bit confusing because that is not what is needed.

What is needed is for it create a small memory dump (Minidump) instead of the kernel memory dump shown in your screenshots.

Can you merge the .reg file under option two, number 2 of this tutorial,

Dump Files - Configure Windows to Create on BSOD

To have it create small memory dumps on the next crash.

Your dump file from OneDrive was partially corrupt for me,

Code:

**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************

doobs · 10 Jul 2014

@essenbe- Okay, done. There is a folder in C:/Windows/Minidump but it is empty. Its icon is the default folder with a lock on it

@derekimo- Alright, I did option two, number two.

Thanks guys.

Also, if it helps, I've gotten about 4 times this error when I turned on my pc https://bd23.https.cdn.softlayer.net...-error-msg.png

essenbe · 10 Jul 2014

Why not download and run Toshiba's hard drive diagnostic test for DOS, you will get better results with the DOS version.
Software Utilities
Seagate's Seatools works very well also.
http://www.seagate.com/support/inter...ls-dos-master/

doobs · 10 Jul 2014

The DOS version says the version is not compatible with my version of Windows and the one above that on the page wont let me choose a hard drive and keeps telling me to select one. I attached the pictures below, and the seagate looks like a lot of work. I ran chkdsk and windows memory diagnostic a couple of months ago and got no problems...

Ill run another chkdsk now.

doobs · 10 Jul 2014

I just ran a chkdsk and it said Volume is clean and regularly booted, similar to this guy-

chkdsk -f on reboot bails: "Volume is clean" - Tech & Computer Forums

"The system reboots and goes into the chkdsk console, but doesn't scan the disk, just reports "Volume is clean", then continues booting Windows.
Event viewer does not show any entry for WinLogon following this."

essenbe · 10 Jul 2014

Did you try the Seatools for DOS link? The guy in the link you posted was running Raid and was most likely using a different operating system than you are. I would try the Seatools link I gave. Also, if you want to run Check Disk this will help Disk Check

doobs · 10 Jul 2014

Regarding the check disc, I did do that. Right clicked my hard drive, checked now, I had both the "Automatically fix file system errors" and "Scan for and attempt recovery of bad sectors".

For the seatools, I don't have discs to burn :/