SOLVED Can not find Minidump folder in Win7 64-bit Ult

[Healt]

I just had another Crash:
Nível Crítico 20/02/2014 10:33:32 Kernel-Power 41 (63)
Nível Crítico 20/02/2014 09:57:24 Kernel-Power 41 (63)

 

[Healt]

I noticed a pattern in the type of crashes, sometimes when you have 2 crashs followed, the time difference between them is 31 to 36 minutes

Nível Crítico    20/02/2014 10:33:32    Kernel-Power    41    (63)
Nível Crítico    20/02/2014 09:57:24    Kernel-Power    41    (63)
Nível Crítico    19/02/2014 13:14:01    Kernel-Power    41    (63)
Nível Crítico    18/02/2014 13:24:20    Kernel-Power    41    (63)
Nível Crítico    17/02/2014 17:13:10    Kernel-Power    41    (63)
Nível Crítico    15/02/2014 16:46:12    Kernel-Power    41    (63)
Nível Crítico    15/02/2014 12:27:55    Kernel-Power    41    (63)
Nível Crítico    14/02/2014 15:49:34    Kernel-Power    41    (63)
Nível Crítico    14/02/2014 15:18:18    Kernel-Power    41    (63)
Nível Crítico    14/02/2014 13:45:29    Kernel-Power    41    (63)
Nível Crítico    13/02/2014 07:41:10    Kernel-Power    41    (63)
Nível Crítico    12/02/2014 17:23:37    Kernel-Power    41    (63)
Nível Crítico    12/02/2014 15:36:53    Kernel-Power    41    (63)
Nível Crítico    12/02/2014 13:57:17    Kernel-Power    41    (63)
Nível Crítico    12/02/2014 13:24:46    Kernel-Power    41    (63)
Nível Crítico    11/02/2014 17:40:02    Kernel-Power    41    (63)
Nível Crítico    04/02/2014 11:36:44    Kernel-Power    41    (63)
Nível Crítico    04/02/2014 10:55:21    Kernel-Power    41    (63)
Nível Crítico    03/02/2014 16:22:01    Kernel-Power    41    (63)
Nível Crítico    03/02/2014 12:32:21    Kernel-Power    41    (63)
Nível Crítico    03/02/2014 11:59:41    Kernel-Power    41    (63)
Nível Crítico    31/01/2014 23:30:18    Kernel-Power    41    (63)
Nível Crítico    30/01/2014 19:22:19    Kernel-Power    41    (63)
Nível Crítico    27/01/2014 08:39:53    Kernel-Power    41    (63)
Nível Crítico    25/01/2014 08:13:36    Kernel-Power    41    (63)
Nível Crítico    23/01/2014 14:20:38    Kernel-Power    41    (63)
Nível Crítico    22/01/2014 16:58:23    Kernel-Power    41    (63)
Nível Crítico    22/01/2014 16:55:01    Kernel-Power    41    (63)
Nível Crítico    21/01/2014 11:02:55    Kernel-Power    41    (63)
Nível Crítico    21/01/2014 02:25:16    Kernel-Power    41    (63)
Nível Crítico    19/01/2014 16:33:09    Kernel-Power    41    (63)
Nível Crítico    17/01/2014 18:03:11    Kernel-Power    41    (63)
Nível Crítico    17/01/2014 00:31:52    Kernel-Power    41    (63)
Nível Crítico    16/01/2014 01:24:13    Kernel-Power    41    (63)
Nível Crítico    15/01/2014 15:39:41    Kernel-Power    41    (63)
Nível Crítico    12/01/2014 09:21:15    Kernel-Power    41    (63)
Nível Crítico    03/01/2014 14:10:11    Kernel-Power    41    (63)
Nível Crítico    31/12/2013 20:51:26    Kernel-Power    41    (63)
Nível Crítico    08/12/2013 16:10:13    Kernel-Power    41    (63)
Nível Crítico    27/11/2013 08:59:16    Kernel-Power    41    (63)
Nível Crítico    29/10/2013 16:35:28    Kernel-Power    41    (63)
Nível Crítico    22/08/2013 19:00:09    Kernel-Power    41    (63)
Nível Crítico    13/08/2013 12:03:55    Kernel-Power    41    (63)
Nível Crítico    01/08/2013 18:14:35    Kernel-Power    41    (63)
Nível Crítico    17/07/2013 08:49:27    Kernel-Power    41    (63)
Nível Crítico    05/07/2013 11:38:26    Kernel-Power    41    (63)
Nível Crítico    02/07/2013 16:05:35    Kernel-Power    41    (63)
Nível Crítico    02/07/2013 13:17:58    Kernel-Power    41    (63)
Nível Crítico    02/07/2013 13:11:11    Kernel-Power    41    (63)
Nível Crítico    02/07/2013 13:06:43    Kernel-Power    41    (63)
Nível Crítico    02/07/2013 13:02:21    Kernel-Power    41    (63)
Nível Crítico    02/07/2013 12:19:37    Kernel-Power    41    (63)
Nível Crítico    02/07/2013 11:56:09    Kernel-Power    41    (63)
Nível Crítico    01/07/2013 20:53:39    Kernel-Power    41    (63)
Nível Crítico    01/07/2013 17:22:59    Kernel-Power    41    (63)
Nível Crítico    01/07/2013 16:23:49    Kernel-Power    41    (63)

 

[Shintaro]

Mate,
A couple of things:
1/ please surround the Kernel Power log list with the forum formatting tags CODE, you will see a picture with the <> on it. It will keep the thread a bit neater. For example:

Nível Crítico 01/07/2013 20:53:39 Kernel-Power 41 (63)
Nível Crítico 01/07/2013 17:22:59 Kernel-Power 41 (63)
Nível Crítico 01/07/2013 16:23:49 Kernel-Power 41 (63)

2/ Please put the crash dump files ( maybe the last 10) in a zip file and upload it to the forum.
3/ Please tell me what you were doing on the computer when it crashed. And what type of crash, computer froze or it went blank and rebooted, etc.

Mate just to let you know I will have a look at the crash files in about 5 hours as it's 1 am here. (Sydney is +10 hours GMT). Just letting you know so that you do not think I am ignoring you.

If you get any more crashes, please update the forum.

Regards.

 

[Shintaro]

Sorry, mate I see that you said there wasn't any crash dump files.
So you looked in :
C:\Windows
C:\Windows\Minidump
C:\Windows\LiveKernelReports\WATCHDOG

About safe Mode, it gives us an indication that it is something running in normal mode, typically a driver, that is causing a problem. However because it is safe mode, you cannot do the same things as you can do with Windows running normal.

 

[Shintaro]

Could you please turn on Driver verifier:

Driver verifier

The Driver Verifier tool that is included in every version of Windows since Windows 2000 it is used to detect and troubleshoot many driver issues that are known to cause system corruption, failures, or other unpredictable behavior.

***FIRST: Please backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Windows 7 Startup Repair feature.)

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select:
   ---- Special Pool
   ---- Force IRQL Checking
   ---- Pool Tracking
   ----Deadlock Detection
   ---- Security Checks (Windows 7 & 8)
   ---- Miscellaneous Checks
   ---- DDI compliance checking (Windows 8)
   
5. Click "Next"
6. Select "Select driver names from a list" and click "Next"
7. Then select all drivers NOT provided by Microsoft and click "Next"
8. Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

How Long should I wait for a crash?

- If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
​

How do I turn Driver Verifier off?!

- Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page.

- Or press the Windows Key + R, and type in "verifier /reset" (Without the quotes)

- Then locate and zip up the memory dump file and upload it with your next post. then locate and zip up the memory dump file and upload it with your next post.
​

I can't get in to Windows, what do I do?

- If Windows will not start and get to a login screen or desktop, because it crashes too soon, try it in Safe Mode.


- If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
​

_________________________

 

[Healt]

My_Crash: (All my files of Watchdog and the file of EVGA precision X), yeah no .dmp files
When it crash my PC goes off instantly, no blue screen appears and my Nobreak makes a brief whistle, the last crash i was on this website and on ebay website maybe youtube also.
And Thanks for all help you are like my last hope on this. Good night

Let me ask
"If I can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier."
What i do if that happens ?

 

[Shintaro]

Mate, on all the forums I have been on helping people, I have never seen that happen.

Were you able to turn on verifier?

 

[Healt]

I'm scared to run this program, I have no backup of my working files and i cant do without an external HD, I ordered an external HD by ebay, should arrive here about 1 month.
Could we use this as a last resort?

 

[Healt]

Also i saw this into a forum of Microsoft what you think about that:

Troubleshooting
If there is no "minidump" folder, or if the folder is empty make sure "minidumps" are enabled.

To ensure minidumps are enabled:
Go to Start, in the Search Box type: sysdm.cpl, press Enter.
(In win 8 you can use the windows key "win" + "s")
Under the Advanced tab, click on the Startup and Recovery Settings button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the drop down box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

Source

Im asking because if you remenber we set it different right now is set to this:

 

[Shintaro]

We already did this via the command line. And small in no good. It needs to be Kernel. Besides it appears that the video crashes all go to C:\Windows\LiveKernelReports\WATCHDOG

Actually the last resort would be to update your BIOS because you are on F03 and on the Gigabyte site there is F08. But updating the BIOS can BRICK your motherboard. So it has to be the absolute last resort.

Microsoft Driver Verifier catches any bad behaving drivers and creates a crash dump file.

Without a crash dump file I am essentially guessing what might be causing the crash.

What you can try, if you feel capable, and you don't want to turn on Verifier is to:
- Download the latest Intel Video driver for your motherboard.
- Re-enable the Intel Video on the motherboard.
- Uninstall the EVGA 760 drivers
- Remove the EVGA 760 board from the computer
- Install the Intel Video Drivers and see if you get any problems.

 

[Healt]

ok i gonna trust on you and give an try on this Driver Verify. im alot scared but seems i dont have many options.
another question have you ever heard of this program Display Driver Uninstaller, i dint used because is also one of my last resort too but look that:

DDU Version: 12.2
Detected GPU : NVIDIA GeForce GTX 460 SE
Detected GPU : NVIDIA GeForce GTX 460 SE
Detected GPU : NVIDIA GeForce GTX 760
Detected GPU : Intel(R) HD Graphics 4600
Detected Driver(s) Version(s) : 9.18.10.3071
Detected Driver(s) Version(s) : 9.18.13.2018
Detected Driver(s) Version(s) : 9.18.13.2018
Detected Driver(s) Version(s) : 9.18.13.3221

 

[Healt]

Where can i turn Driver verifier on ?

nvm i found

 

[Shintaro]

I explained how to enable driver verifier and what to set in it, in one of the above posts.

I only trust uninstallers from the vendor. It is up to you if you want to use DDU.

Tell me what you are going to try next. Driver Verifier or remove the EVGA 760 board?

 

[Healt]

I dint check any driver called Microsoft Corporation, anyway could you check if everything is fine so i can click finish and reboot.

 

[Healt]

 

[Shintaro]

Looks ok, go with that.

 

[Healt]

ok i alread finish and reboot now im w8ting the next crash

 

[TrainableMan]

The error constantly mentions kernal power. What power supply do you have and have you ever tried a new one? If the computer is not getting enough power it could easily shut down and that could also explain why there would be no DMP.

 

[Shintaro]

Actually Trainableman you might have something there. I was getting the same error on my Laptop, but I was thinking that it was to do with switchable graphics. Because as soon as I set what could use "Power Saving" Intel Graphics and "High Performance" the on-board Radeon, the error went away.

As a test I will run a graphic screen saver(setti at home) whilst my laptop is on batteries.

 

[TrainableMan]

Well my thought was maybe a power supply that is inadequate, because it looks like Healt is running two high-end graphics cards: a GTX460 & a GTX760. So I want to know how powerful his power supply is; I'm thinking he probably needs a good 800W, maybe 1000W PSU.