BSOD 0x0000001E, 1D, 3B on Computer Shutdown

There doesn't seem to be any dump files within the folder, please manually check this directory:

Code:

C:\Windows\Minidump

What do memory dump type do you have configured?

x BlueRobot said:

There doesn't seem to be any dump files within the folder, please manually check this directory:

Code:

C:\Windows\Minidump

What do memory dump type do you have configured?

Try now, I don't know what happened.

To the Top

themaltaproject said:

To the Top

bumped again

Please do not thread bump - https://www.sevenforums.com/general-d...ease-read.html

It also shows impatience and rudeness.

=======================================

Here's my analysis of the latest dump file:

Code:

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchDdiNotifyDpcWorker+36 )

Code:

0: kd> !stack
Call Stack : 14 frames
## Stack-Pointer    Return-Address   Call-Site       
00 fffff80000b9b708 fffff800032855be nt!KeBugCheck+0 
01 fffff80000b9b710 fffff800032b875d nt!KiKernelCalloutExceptionHandler+e 
02 fffff80000b9b740 fffff800032b7535 nt!RtlpExecuteHandlerForException+d 
03 fffff80000b9b770 fffff800032c84c1 nt!RtlDispatchException+415 
04 fffff80000b9be50 fffff8000328d242 nt!KiDispatchException+135 
05 fffff80000b9c4f0 fffff8000328bb4a nt!KiExceptionDispatch+c2 
06 fffff80000b9c6d0 fffff80003285bd6 nt!KiGeneralProtectionFault+10a 
07 fffff80000b9c860 fffff8800fd40caa nt!ExpInterlockedFlushSList+26
08 fffff80000b9c870 fffff8800fd40c58 dxgmms1!VidSchDdiNotifyDpcWorker+36 
09 fffff80000b9c8c0 fffff8800fc471cf dxgmms1!VidSchDdiNotifyDpc+94 
0a fffff80000b9c910 fffff8800f0d4120 dxgkrnl!DxgNotifyDpcCB+77 
0b fffff80000b9c940 fffffa8008a8f000 nvlddmkm+c7120 (leaf)

The problem within the stack seems to be quite simple, a exception occurred with the InterlockedFlushSList routine, leading to a General Protection Fault. I'm guessing the exception was due to some alignment error with the MEMORY_ALLOCATION_ALIGNMENT boundary which is 16 on x64 systems.

Since the linked list, was most likely built with a SLIST_ENTRY data structure (represents a entry in a singly linked list), then memory alignment is meant to be extra important, since a x64 system is meant to take advantage of guaranteed to be zero bits.

Good article explains how the exception happened - If you're going to write your own allocator, you need to respect the MEMORY_ALLOCATION_ALIGNMENT - The Old New Thing - Site Home - MSDN Blogs

Code:

fffff80000b9c628 -- (.exr 0xfffff80000b9c628)
ExceptionAddress: fffff80003285bd6 (nt!ExpInterlockedFlushSList+0x0000000000000026)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

Code:

0: kd> .frame 7
07 fffff800`00b9c860 fffff880`0fd40caa nt!ExpInterlockedFlushSList+0x26

This routine is used to flush or delete all the entries within a singly linked list.

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f00d000 fffff880`0fc44000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Oct 23 07:21:50 2013 (52676AFE)
    CheckSum:         00C0CF0F
    ImageSize:        00C37000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please ensure you have updated to the latest WHQL driver, which is available from here - Latest NVIDIA ForceWare Video Drivers Windows 7

Version: 331.65
Release Date for Desktops and Notebooks : October 28th 2013
In Device Manager: 9.18.13.3165

Remove:

Code:

Start Menu\Programs\DAEMON Tools Lite

Arc said:

Download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Daemon Tools uses a driver called sptd.sys, which is known to cause BSODs with Windows 7. It is recommend you remove this program, and use Windows own in-built features or ImgBurn.

Sorry for the forum bumping, it is a common thing across all forums, and I gave it a curtsey period of 24hrs before bumping. I wont do it again.

The thing is, I was getting the BSOD's about 2 wweks ago and reinstalled all of my nvidia drivers off of koolkats advice. They returned shortly after. I will delete Daemon tools and let you know how it goes.

Will look forward for an update, and the driver updates are released very regularly, and you may need to run Driver Verifier.