my comp BSOD when rendering with 3ds max

hotoma2 · 03 Mar 2012

hi, when rendering in 3d max i get BSOD. ive changed hard drive because it destroyed my other one. and now its happening to this one. i uninstalled my antivirus (eset) and it still happens. the only programs i had open was VLC player

im using Windows 7 64x the original OS of the system
system hardware is about 3 months old, i havent tried a different version

writhziden · 03 Mar 2012

Antivirus Software? Either recommend

Microsoft Security Essentials - Free Antivirus for Windows

or the

Good and Free system security combination.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\hotoma2\Windows_NT6_BSOD_jcgriff2\030312-22183-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e57000 PsLoadedModuleList = 0xfffff800`03094e50
Debug session time: Sat Mar  3 08:16:47.047 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:10.779
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800839a8f8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800839a8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031b66f0 fffff800`03111a89 : fffffa80`0839a8d0 fffffa80`06a32680 fffffa80`00000005 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031b6c10 fffff800`02ff3547 : fffffa80`0839a8d0 fffff800`0306c5f8 fffffa80`06a32680 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031b6c40 fffff800`02f5bb95 : fffff800`030ce360 fffffa80`079bd828 fffffa80`079bd820 fffffa80`06a32680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031b6c80 fffff800`02ed6161 : fffff880`010dee00 fffff800`02f5bb70 fffffa80`06a32680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031b6cb0 fffff800`0316c166 : 00000000`00000000 fffffa80`06a32680 00000000`00000080 fffffa80`06a1e040 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02ea7486 : fffff880`02f64180 fffffa80`06a32680 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`02ecb590 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

Followup: MachineOwner
---------

Start with Stop 0x124 - what it means and what to try and use the following to supplement the steps in that link.

If you are overclocking any hardware, please stop.
Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
Update to Service Pack 1 (SP1)

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site
Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH

hotoma2 · 04 Mar 2012

i tried running prime95 test, and the comp blue screened

writhziden · 04 Mar 2012

Did you happen to note the temperature at the time of the blue screen?

Also, did the blue screen crash finish compiling the .dmp report? There may be useful information in the crash report for us to look at.

hotoma2 · 05 Mar 2012

no i didnt , heres the dump file . i checked the temperature after the BSOD . componants was running at normal temp

writhziden · 05 Mar 2012

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\hotoma2\Windows_NT6_BSOD_jcgriff2\030412-23743-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e54000 PsLoadedModuleList = 0xfffff800`03091e50
Debug session time: Sun Mar  4 10:39:43.582 2012 (UTC - 7:00)
System Uptime: 0 days 0:03:45.315
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008336028, b26b4000, 175}

Probably caused by : hardware

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008336028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b26b4000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  prime95.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02f6ca88 fffff800`02e1d903 : 00000000`00000124 00000000`00000000 fffffa80`08336028 00000000`b26b4000 : nt!KeBugCheckEx
fffff880`02f6ca90 fffff800`02fda513 : 00000000`00000001 fffffa80`0841f4b0 00000000`00000000 fffffa80`0841f500 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6cad0 fffff800`02e1d5c8 : 00000000`00000728 fffffa80`0841f4b0 fffff880`02f6ce30 00000000`39daa500 : nt!WheaReportHwError+0x263
fffff880`02f6cb30 fffff800`02e1cf1a : fffffa80`0841f4b0 fffff880`02f6ce30 fffffa80`0841f4b0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6cc80 fffff800`02e10e8f : 00000000`4f119780 00000000`00000001 fffff880`02f6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6ccc0 fffff800`02ec47ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02f6ccf0 fffff800`02ec4613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6ce30 00000000`005dfe23 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`02462100 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5dfe23


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

Followup: MachineOwner
---------

In addition to any steps above that have not yet been carried out, proceed with the steps in Stop 0x124 - what it means and what to try