BSOD 0x0000001e

[doobs]

Hey guys, my first post on these forums. Yesterday I got a BSOD 0x0000001e error. I checked Event Viewer and saw that- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000096, 0xfffff80002c90948, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

AND

Unable to produce a minidump file from the full dump file.

Before I've gotten a couple of 0x0000007F blue screens, but that was a couple of months ago. I hate getting bluescreens and I was wondering if you guys could help me. I posted what bluescreenview shows me in the png image and the zip file contains the logs. Thanks!

I was looking in Event Viewer and found one of the previous blue screens- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007a (0xfffff8a0038b2820, 0xffffffffc0000185, 0x000000010df418c0, 0xfffff88006d70000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

Unable to produce a minidump file from the full dump file.

I also included a picture of the BSOD 0x0000007F below.

System Specs:

CPU - FX 4130 Black Edition 3.8GHz
Motherboard - ASUS M5A97 r2.0
GPU - EVGA GTX 760
RAM - Crucial Ballistix Sport 8GB DDR3-1333
Storage - 1TB Toshiba DT01ACA100
Case - Zalman Z11 Mid tower case
PSU - Corsair CX500M

 

[Boozad]

There are no dump files in your logs to analyse unfortunately. Follow http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html to see if this catches future BSODs.
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[doobs]

I looked at those screenshots and my System Properties have all the things checked.. except on the Write debugging information there is no "Complete memory dump". I attached a picture of what mine looks like

 

[doobs]

I opened the MEMORY.DMP with windbg.. can I upload it so that you can see it?

 

[Boozad]

Try uploading the Memory dump to a site like OneDrive and post the link.

 

[doobs]

Here you go: https://onedrive.live.com/redir?resid=61BB3DBAE872B4DC!115&authkey=!AOkA9WhXDeu3TZ0&ithint=file,.DMP

Sorry it took so long, I have like a 1mb upload speed.

 

[Boozad]

I'll take a look shortly, I'm on my phone at the moment.

 

[doobs]

Sure, thanks

 

[Boozad]

There's nothing I can get out of the dump unfortunately except for the STOP being a 0x1E, which could point to one of quite a few things. If you get any more BSODs check for minidumps and upload them straight away and I'll be glad to look at them for you.

**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000096, fffff80002c90948, 0, 0}

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057

 

[doobs]

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

 

[Boozad]

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]

Sounds good. I really appreciate your help

 

[essenbe]

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.

View attachment 325037

 

[derekimo]

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,

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

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

Your dump file from OneDrive was partially corrupt for me,

**************************************************************************
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]

@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.ne...ntent/uploads/2005/10/disk-read-error-msg.png

 

[essenbe]

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/inte...-electronics/ld25-series/seatools-dos-master/

 

[doobs]

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]

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]

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 http://www.sevenforums.com/tutorials/433-disk-check.html

 

[doobs]

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 :/