Need help understanding dump file and crash reason

[visible]

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Users\Garfield\Desktop\080715-9282-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e92730
Debug session time: Fri Aug 7 10:20:55.260 2015 (UTC + 3:00)
System Uptime: 0 days 0:05:37.087
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880009b3180, 4}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------
This occurs when i try to render something in Cinema 4D, ran cinebench for 24 hours stable no crashes.. ran Cinnebench on GPU for 8 hours no crash (didnt have more time) so im puzzled, whats going on here..

Thank you in advance!

 

[Laith]

Hiya and welcome to SevenForums!rb:
Next time please follow the Blue Screen of Death (BSOD) Posting Instructions
But this time you analyzed it so it's okay.

It's an 0x101 which is related to overclocking. Have you overclocked?

 

[visible]

yes, from 4,3 standart to 4,6 GHz, but as I said, the cinebench ran 24 hrs stable at 100% load...
4790k @4,6 GHz / on MAXIMUS VII Ranger, highest temperature i reached was 57C

 

[Laith]

Reset the overclocking. That should fix the BSOD.

 

[visible]

so basically I cant use any OC while in C4D, weird...

 

[Laith]

Well, have you resetted the OC?

 

[visible]

yep.. strange... doesent happen to AE... C4D is unable to handle OC?

 

[visible]

Literally Ran cinebench stress @ 100% for 24 hours no glitch, Cinema 4D BSODs in 5 seconds...
Adobe After Effecs uneffected

 

[Laith]

Must be, maybe C4D dosen't like OCing. Have you resetted the OC yet?

 

[visible]

yes I did, its quite easy with Asus ROG motherboards, you don't even need to restart the pc... still..

 

[Laith]

Well, look up in google about C4D and overclocking, maybe you can find a patch and overclock. That's amazing too with the ASUS ROG motherboards.