Recently, I started having my custom built system (which was working just fine) turn off at night.  My SSD was funky and Corsair mentioned some problems and suggested I update the SSD's firmware.  I'm not sure if that caused the problem and I suck and reading the minidump to find these problems.

I've uploaded 2 minidump files to dropbox if someone would be kind enough to look at them and let me know where the problem might be.

https://dl.dropboxusercontent.com/u/24043987/Dump.7z

Thanks

Beerguy

Both DMP files are empty (zero bytes) probably a shortcut.  Try it again.

We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.   WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.
Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask

Sorry, I thought they were rather small.  I can't connect to my system now so it obviously shut down again but I'll get these resent after work.

Thanks for the help!!!!!

BG

Now worries and my pleasure.

All the dump files in c:\windows\minidump are small.

Here's the zip to all the ones in the folder from 12/21 until the 25th.

https://dl.dropboxusercontent.com/u/24043987/dmp.7z

WhoCrashed posted a memory dump at 4:37 am when it appears the computer crashed.

it's here: https://dl.dropboxusercontent.com/u/24043987/MEMORY.7z

Let me know if you need any other info.

Thanks again for the help.

BG

Nope same problem  What size are they on your computer?

Various sizes but I think the problem is 7zip.  I think this should work now.

Wow, can't believe I"m having these problems with compressing files.....the simplest of things.

Here's the original bunch

https://dl.dropboxusercontent.com/u/24043987/Dump.7z

and it happened again while I was out tonite....

https://dl.dropboxusercontent.com/u/24043987/122713-10718-01.dmp

These are not zero byte files so I hope they have everything you need.

Mega thanks!

BG

Well there is good news and bad  news.  We got 3 dmps but they were all inconclusive.  It may very well be because the SSD is causing ACPI.sys to crash but from these DMPS I cant tell.

*

One way to be more certain is to run driver verifier

*

If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

Driver verifier (for complete directions see our wiki here) Co-Authored by  JMH3143 .

Bugcheck code 0000009F
Bugcheck code 0000009F
Bugcheck code 0000009F
``
BugCheck 9F, {3, ffffe00000638e10, fffff8019cb9a840, ffffe000013bb010}
BugCheck 9F, {3, ffffe00000624e10, fffff8014a79a840, ffffe000028fae10}
BugCheck 9F, {3, ffffe000006369f0, ffffd00020933840, ffffe00000c82640}
``
BugCheck 9F, {3, ffffe00000638e10, fffff8019cb9a840, ffffe000013bb010}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
``
BugCheck 9F, {3, ffffe00000624e10, fffff8014a79a840, ffffe000028fae10}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
``
BugCheck 9F, {3, ffffe000006369f0, ffffd00020933840, ffffe00000c82640}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
``
SYSTEM UP-TIME
System Uptime: 0 days 1:49:59.728
System Uptime: 0 days 12:43:00.050
System Uptime: 0 days 10:35:51.840
``
Debug session time: Thu Dec 26 23:37:17.380 2013 (UTC - 5:00)
Loading Dump File [C:\Users\Ken\SysnativeBSODApps\122713-11171-01.dmp]
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
System Uptime: 0 days 12:43:00.050
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 9F, {3, ffffe00000624e10, fffff8014a79a840, ffffe000028fae10}
Bugcheck code 0000009F
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe00000624e10, Physical Device Object of the stack
Arg3: fffff8014a79a840, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: ffffe000028fae10, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x9F_3_ACPI_ANALYSIS_INCONCLUSIVE
MaxSpeed:     3500
CurrentSpeed: 3518
BiosVersion = 3505
BiosReleaseDate = 03/13/2013
SystemManufacturer = System manufacturer
SystemProductName = System Product Name

Thanks, I'll try the driver verifier and see how it goes.

FYI, I don't overclock.  I built this system recently and it ran great but after  a few weeks, I had problems with rebooting and seeing the SSD and Corsair forums mentioned this problem and they issued new firmware. Then this happened. 
I'll post back what I find out.

I really appreciate you time and help.

BG

You are slightly over clocked

MaxSpeed:     3500
CurrentSpeed: 3518

I've not done anything to overclock this CPU but maybe ASUS Suite has.

I ran verifier and after a number of tries, it would not restart. After I got into safe mode and disabled verifier and got it back to normal boot.

I hope I have all the files you need.

https://dl.dropboxusercontent.com/u/24043987/dump.zip

Again, many thanks.

BG

Finally.  The verified DMPS clearly point to your video driver.  Since yours is current I would revert back to an older driver (at least a generation).

Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff802`87a6f000 PsLoadedModuleList = 0xfffff802`87d33990
Debug session time: Sat Dec 28 11:18:21.327 2013 (UTC - 5:00)
System Uptime: 0 days 0:01:07.054
Loading Kernel Symbols

BugCheck C4, {f6, bcc, ffffe000047c9900, fffff80001ee3879}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9a879 )


DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000bcc, Handle value being referenced.
Arg3: ffffe000047c9900, Address of the current process.
Arg4: fffff80001ee3879, Address inside the driver that is performing the incorrect reference.

• Edited by ZigZag3143xMVP, Moderator 18 hours 4 minutes ago

Thanks very much. I wondered about that driver though an almost identical machine using the same video card and driver is working fine.

I'll revert back to the last driver and try that for a few days and if that doesn't work, I'll go back further.

I very much appreciate all the help here!

BG

No two machines are identical.  Every machine is a unique combination of hardware, and software.  If this is a laptop you may also want to keep an eye on the temps by downloading cpu-s & gpu-z (both free)

Have a good ho

BG

Finally.  The verified DMPS clearly point to your video driver.  Since yours is current I would revert back to an older driver (at least a generation).

Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff802`87a6f000 PsLoadedModuleList = 0xfffff802`87d33990
Debug session time: Sat Dec 28 11:18:21.327 2013 (UTC - 5:00)
System Uptime: 0 days 0:01:07.054
Loading Kernel Symbols

BugCheck C4, {f6, bcc, ffffe000047c9900, fffff80001ee3879}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9a879 )


DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000bcc, Handle value being referenced.
Arg3: ffffe000047c9900, Address of the current process.
Arg4: fffff80001ee3879, Address inside the driver that is performing the incorrect reference.

• Edited by ZigZag3143xMVP, Moderator Saturday, December 28, 2013 5:39 PM

BG

Finally.  The verified DMPS clearly point to your video driver.  Since yours is current I would revert back to an older driver (at least a generation).

Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff802`87a6f000 PsLoadedModuleList = 0xfffff802`87d33990
Debug session time: Sat Dec 28 11:18:21.327 2013 (UTC - 5:00)
System Uptime: 0 days 0:01:07.054
Loading Kernel Symbols

BugCheck C4, {f6, bcc, ffffe000047c9900, fffff80001ee3879}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9a879 )


DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000bcc, Handle value being referenced.
Arg3: ffffe000047c9900, Address of the current process.
Arg4: fffff80001ee3879, Address inside the driver that is performing the incorrect reference.

• Edited by ZigZag3143xMVP, Moderator Saturday, December 28, 2013 5:39 PM
• Marked as answer by ZigZag3143xMVP, Moderator 6 hours 50 minutes ago

Didn't take long for this to happen again with an earlier driver.  I'll go to the next earliest driver and give that a try.

This sucks that Nvidia, a company I've been happy with, can put out drivers almost every 6 weeks and have nothing but problems. Their forums are full of complaints.

BG

AFAIK it is only with this driver and only with a select group of machines.  If reverting back doesn't help it may be something with the card itself.

You might want to run a GPU stress test

Try this free video stress test:  http://www.ozone3d.net/benchmarks/fur/
FurMark Setup:

- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first)
- Click "Quit" to exit

I went back a few drivers and have tried almost all the Furmark tests.  Passing with flying colors. Temps never got above 73 C and most stayed below 70.  Idle temps are 36 C.

BG

You are probably approaching a point where it might be easier to simply re-install the OS.

Well I do have an image of the system right after I built it and installed the OS and other software and another image a week later but maybe starting over will be what is needed in the end.

So far, going back 2 gens with the nvidia driver hasn't helped.

I did look at the BIOS and enabled XMP which is how my other system is set up (same memory, yada, yada, yada) so maybe that will help a bit.  I'm over my head when it comes to the software side of things.

• Edited by Beerguy 17 hours 4 minutes ago

BG

We know what it is but don't know why it is.  Your call and I am here to help in which ever way you go.  If we could attach a debugger directly and watch it as it happens we would have a definitive answer but that would take weeks of instruction and I suspect the image might work

Well I do have an image of the system right after I built it and installed the OS and other software and another image a week later but maybe starting over will be what is needed in the end.

So far, going back 2 gens with the nvidia driver hasn't helped.

I did look at the BIOS and enabled XMP which is how my other system is set up (same memory, yada, yada, yada) so maybe that will help a bit.  I'm over my head when it comes to the software side of things.

• Edited by Beerguy Sunday, December 29, 2013 6:41 PM

Well I do have an image of the system right after I built it and installed the OS and other software and another image a week later but maybe starting over will be what is needed in the end.

So far, going back 2 gens with the nvidia driver hasn't helped.

I did look at the BIOS and enabled XMP which is how my other system is set up (same memory, yada, yada, yada) so maybe that will help a bit.  I'm over my head when it comes to the software side of things.

• Edited by Beerguy Sunday, December 29, 2013 6:41 PM

Bummer, I went back to a clean image and not more than 12 hours later, the crash.  I think it's sleep related as the system only has done this in while in sleep mode.  I'm going to try Away  mode to see what happens over the next 2 days.  Then, I guess it's a fresh install though I wonder if the same thing would happen again.

I think we can close this one out. Thanks for all the help.

In the end I reinstalled 8.1 from scratch and things seem to be working well.  As a guess, I think my installing Acronis Disk Manager (an older version) caused some or all of the problems I was having.  It was after I installed it on another system and had similar problems, removed it and found things were good that I realized it may have also caused the problem I posted here.

Anyway, I learned much and again, thanks.

• Marked as answer by ZigZag3143xMVP, Moderator 6 hours 52 minutes ago

Glad you got it working and thanks for letting us know.