Various BSODs, please help?

[Interloper]

Hi. I've posted over at Microsoft Answers before but those guys were useless (kept referring me to Dell, who have been equally useless.) This looks like a nice place to get some answers. Hope you can help

- x86 (32-bit) or x64 ? x86. Had x64 installed but switched because I thought the 64 bit edition might have been my problem.
- the original installed OS on the system? no
- an OEM or full retail version? OEM
- What is the age of system (hardware)? Two years? I think. Bought second-hand.
- What is the age of OS installation? Only a week or so. Prior to that, I think the retailer I bought it from had only recently installed the 64 bit.

 

[Dave76]

Welcome to Seven Forums.

Uninstall Daemon Tools. It's driver, SPTD, is known to cause problems in Windows 7.
Once it's removed, run the SPTD removal tool. DuplexSecure

Have you updated drivers from the Dell site?

Update your driver for your Conexant SoftK56 Modem.

Did you add the extra RAM card or did it have that when you got it?
Might need to look at that later.

Try this MS Hot Fix: "0x0000007F" Stop error after you install Windows 7 Service Pack 1 in Windows 7

STOP 0xF7

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
BugCheck F7, {b4c77eb6, 9b0b970f, 64f468f0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiDispatchException+17c )
Followup: MachineOwner
---------

Can you give some details on the crashes?
When they started? Was it after any new hardware or software?

 

[Interloper]

Cheers Dave. I don't think I have updated any drivers from the Dell site - I've certainly browsed through there before, but they don't offer any drivers for Windows 7. I did install a chipset driver, I'm not sure if that was a Vista driver from the Dell site, or if I located a reference driver from Intel.

"Update your driver for your Conexant SoftK56 Modem."

Done.

"Did you add the extra RAM card or did it have that when you got it?"

The RAM came in the machine when I purchased it. As I said it was second-hand - the retailer claimed to run exhaustive tests on the system prior to putting it back on the market. Trying to get some tech support out of them as well.

I'm installing the hotfix now.

*Cancel that, seems it was already installed.

 

[Interloper]

You know what? I think it might have been Service Pack 1, which I had to uninstall for the purpose of installing that hotfix. I haven't experience a crash in a couple of days now. I'll try to remember to check back in a couple of days.

If it is Service Pack 1, obviously it's something I should pass on to Microsoft, right? Does anyone know the best method of doing so?

 

[Dave76]

Hope you system remains stable.

Have you previously installed all MS updates?

Let us know how your system is running.

 

[Interloper]

Yes, when I received the PC one of those first things I did was install all of the available updates. Since removing SP1 the system has been completely stable.

 

[Interloper]

I take that back. I just had a bluescreen. Okay, so, I know the basics of WinDbg and I'd been running it myself but it stopped working for me. I just tried it with the minidump from the recent crash and it was fine.

This one points to the process PSANHost.exe which is Panda Cloud Antivirus. Appears to be a buffer overrun, something to do with a driver. I don't know enough about what the data means to read it.

 

[Interloper]

And one more just now. 0x100000(etc.)8E KERNEL_MODE_EXCEPTION_NOT_HANDLED points to win32k.sys
The general consensus from Google suggests video card drivers, but I have the latest =/ I used to have the beta drivers installed but I went back to the stable as a troubleshooting measure.

 

[Dave76]

Did you un-install the old drivers first?

How To Correctly Remove Nvidia Video Card Drivers.
In order for new video card drivers to work correctly, you must first make sure that all old drivers for the video card are removed, as the old ones can conflict with the new ones, giving various errors when trying to run games ect.

Firstly, remove old drivers by navigating to device manager, and select display adapters, double click on your graphics card, select the driver tab, and select uninstall for your video card driver.

Download and install Guru3D Driver Sweeper

Once installed, reboot your computer and start in safe mode, run driver cleaner and select Nvidia from the drop down list to be cleaned. This will remove all remaining parts of the old driver. It should be run in safe mode as this has the best results.

Once cleaned, restart the computer. Install the new drive

 

[Interloper]

Yes, and I used a driver sweeper.

 

[Interloper]

Hi. I just wanted to bump this thread. I've been using Linux Mint for a while and came back to Windows for the gaming. The BSODs are back, though I'm using Windows 7 x64 this time - which I figure suggests that its a hardware issue, perhaps incompatibility. Does anyone have any solutions? Here's some fresh system info.

 

[Dave76]

First let's find out about the RAM.

Download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs for both RAM cards.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Mixed RAM can be difficult to get setup and run together, OEM computers don't let you adjust the RAM settings so there aren't a lot of options if the RAM isn't running stable.
Run memtest86+ with both cards installed, this will take several hours, run for a minimum of 8 passes. Best to run overnight.
Each pass runs different tests, they are all important.
If you get any errors you can stop the test, and report back here.
RAM - Test with Memtest86+

The last minidump.
Usual causes: Device driver
Cause:
A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.
This bug check is usually caused by drivers that have used improper addresses.

This can also be caused by hardware, as is indicated in the Bugcheck below.

Firefox is blamed and has a known memory leaks in older versions. Update firefox to the latest version.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000929, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88006849bf6, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d13100
 0000000000000929 

CURRENT_IRQL:  2

FAULTING_IP: 
USBPORT!USBPORT_BusContextEvent+36
fffff880`06849bf6 00488d          add     byte ptr [rax-73h],cl

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

[B]PROCESS_NAME:  firefox.exe[/B]

TRAP_FRAME:  fffff88003122ad0 -- (.trap 0xfffff88003122ad0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000099c rbx=0000000000000000 rcx=fffffa8004d9f5e0
rdx=fffffa80043dc9d8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006849bf6 rsp=fffff88003122c60 rbp=fffffa80042a0ad0
 r8=fffffa80042a0b1c  r9=000000000000099c r10=fffffa8004ce81a0
r11=fffffa80043dc938 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
USBPORT!USBPORT_BusContextEvent+0x36:
fffff880`06849bf6 00488d          add     byte ptr [rax-73h],cl ds:9500:00000000`00000929=??
Resetting default scope

MISALIGNED_IP: 
USBPORT!USBPORT_BusContextEvent+36
fffff880`06849bf6 00488d          add     byte ptr [rax-73h],cl

LAST_CONTROL_TRANSFER:  from fffff80002ae32a9 to fffff80002ae3d00

STACK_TEXT:  
fffff880`03122988 fffff800`02ae32a9 : 00000000`0000000a 00000000`00000929 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03122990 fffff800`02ae1f20 : 00000000`00000000 fffffa80`0408b800 fffffa80`036681a0 fffffa80`042a0000 : nt!KiBugCheckDispatch+0x69
fffff880`03122ad0 fffff880`06849bf6 : fffffa80`0426db80 fffff880`06842f5d 00000000`00000001 fffffa80`0425ab80 : nt!KiPageFault+0x260
fffff880`03122c60 fffffa80`042a0130 : fffffa80`04ce8a18 fffff880`0684b210 fffffa80`037dca00 fffffa80`04ce8050 : USBPORT!USBPORT_BusContextEvent+0x36
fffff880`03122c90 fffffa80`04ce8a18 : fffff880`0684b210 fffffa80`037dca00 fffffa80`04ce8050 fffffa80`042a0000 : 0xfffffa80`042a0130
fffff880`03122c98 fffff880`0684b210 : fffffa80`037dca00 fffffa80`04ce8050 fffffa80`042a0000 fffff880`06869208 : 0xfffffa80`04ce8a18
fffff880`03122ca0 fffff880`06894bac : fffffa80`042a2718 fffffa80`06dc2750 fffffa80`04ce96a0 fffffa80`042bc6f0 : USBPORT!USBPORTSVC_CompleteIsoTransfer+0xe4
fffff880`03122cf0 fffff880`0689ce08 : fffffa80`037dcc48 fffffa80`037dcc48 00000000`00000001 fffffa80`03669500 : usbehci!EHCI_InternalPollHsIsoEndpoint+0x628
fffff880`03122da0 fffff880`0683de8b : 00000000`00000002 fffffa80`04ce81a0 00000000`00000000 00000000`00000070 : usbehci!EHCI_PollEndpoint+0xb8
fffff880`03122de0 fffff880`068429d1 : 00000000`00000070 00000000`00000004 fffffa80`037dca00 fffffa80`04ce8050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`03122e10 fffff880`0684e077 : fffffa80`04ce81a0 00000000`00000070 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`03122e70 fffff880`0683ef89 : fffffa80`04ce8050 00000000`00000000 fffffa80`04ce8a02 fffffa80`04ce8a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`03122ed0 fffff800`02aef10c : fffff880`009e9180 fffffa80`04ce8a18 fffffa80`04ce8a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`03122f00 fffff800`02ae6765 : 00000000`00000000 fffffa80`07308b60 00000000`00000000 fffff880`0683edb0 : nt!KiRetireDpcList+0x1bc
fffff880`03122fb0 fffff800`02ae657c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`0cfdb460 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_InternalPollHsIsoEndpoint+628
fffff880`06894bac 4533ed          xor     r13d,r13d

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  usbehci!EHCI_InternalPollHsIsoEndpoint+628

FOLLOWUP_NAME:  MachineOwner

[B]IMAGE_NAME:  hardware[/B]

DEBUG_FLR_IMAGE_TIMESTAMP:  0

[B]MODULE_NAME: hardware[/B]

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Your Conexant SoftK56 Modem Driver is dated '08 and may be causing issues.
Check the Dell site again or this site:
http://www.conexant.com/support/
Update this driver.


The 29 July crash is STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

Cause:
Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.

A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.

This is telling me it can be caused by the Firefox memory leak and/or the RAM card mismatch.
Best to check both, as suggested above.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff88001253137

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002acc2a9 to fffff80002accd00

STACK_TEXT:  
fffff880`009efc68 fffff800`02acc2a9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009efc70 fffff800`02aca772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009efdb0 fffff880`01253137 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`0381ff68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsMapUserBuffer+0x27


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02aca772 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

The 27 July crash is STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory

Cause:
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

This is also confirming memory leak and/or RAM issues.

It is blaming windows drivers which usually indicates hardware.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88003a3d695, Address of the instruction which caused the bugcheck
Arg3: fffff8800bcc01b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VidSchSubmitCommand+369
fffff880`03a3d695 488908          mov     qword ptr [rax],rcx

CONTEXT:  fffff8800bcc01b0 -- (.cxr 0xfffff8800bcc01b0)
rax=0000000000000000 rbx=fffffa8005bd0678 rcx=fffffa8003b68b00
rdx=fffffe00081581f8 rsi=fffffa8007538280 rdi=0000000000000000
rip=fffff88003a3d695 rsp=fffff8800bcc0b90 rbp=fffff8800bcc0d80
 r8=0000000000000000  r9=0000000000000000 r10=0000004400000000
r11=fffffa8003b68b88 r12=fffffa8005bd0490 r13=fffffa8003b68ae0
r14=0000000000000001 r15=fffffa800639f410
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
dxgmms1!VidSchSubmitCommand+0x369:
fffff880`03a3d695 488908          mov     qword ptr [rax],rcx ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  DX2.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88003b5b764 to fffff88003a3d695

STACK_TEXT:  
fffff880`0bcc0b90 fffff880`03b5b764 : fffff8a0`00000000 00000000`00000200 fffff880`0bcc12c0 00000000`00000000 : dxgmms1!VidSchSubmitCommand+0x369
fffff880`0bcc0bf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DXGCONTEXT::Render+0xadc


FOLLOWUP_IP: 
dxgmms1!VidSchSubmitCommand+369
fffff880`03a3d695 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VidSchSubmitCommand+369

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff8800bcc01b0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VidSchSubmitCommand+369

BUCKET_ID:  X64_0x3B_dxgmms1!VidSchSubmitCommand+369

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

Event messages:

Try to ensure adequate disk space to store memory dumps, you will need these for evaluation.

Event[430]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2011-07-29T15:46:38.000
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: PrecisionM4300
  Description: 
The dump file at location: C:\Windows\[B][SIZE="3"]MEMORY.DMP was deleted because the disk volume had less than 25 GB free space[/SIZE][/B].

Have you deleted and completely removed Trend Micro?
Avast is throwing some errors, you might want to check that it is working correctly.
Make sure that both of these are not installed at the same time, it will cause conflicts and errors.
I would recommend Avast over Trend Micro, but that is just my opinion.


D/L and run Seagate SeaTools – Short Drive Self Test and Long Drive Self Test

Event[2476]:
  Log Name: System
  Source: Ntfs
  Date: 2011-07-27T18:08:49.821
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: PrecisionM4300
  Description: 
[B][COLOR="Red"]The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume 1[/COLOR][/B].

Is this a partition or external HDD?

Event[2479]:
  Log Name: System
  Source: Ntfs
  Date: 2011-07-27T18:08:49.373
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: PrecisionM4300
  Description: 
[B][COLOR="Red"]The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume G:[/COLOR][/B]

There are a lot of app crashes that may or may not be attributed to RAM issues, memory leak or HDD file corruption.


There is a lot of info and trouble shooting steps here, just start with updating Firefox.
Then the RAM information and memtest86+.
Run SeaTools.

Let us know the progress.

 

[Interloper]

Alright, my CPU-Z results are attached.

I haven't been checking the temperatures, but I ran Real Temp. I seem to idle around 50 degrees celsius. I ran a torture test in Prime95 and the system hit 98 degrees before the BIOS scaled the CPUs back to reduce the temperature.

I'll run memtest overnight. Firefox reports its already the latest version, and from what I can see on the website, that's correct. I couldn't find a newer driver for the modem - I also checked windows update through device manager.

I'm not actually running a Trend Micro antivirus, its RUBotted, specifically for detecting bot infections. Avast is probably enough, I'd agree, but its something I came across while attempting to clear my system of malware a couple of days ago. (I had to format and reinstall.)

The tests through SeaTools produced no errors - I'll have a look into those disk errors. I suspect they're related to a USB hub w/ IDE and SATA interfaces I use.

 

[Dave76]

Those temps are way too high, you need to take off the CPU cooler, clean both the CPU and heatsink with alcohol, then apply new thermal paste.
Artic Silver 5 is highly recommended.

Information on CPU coolers and thermal paste.
80 Thermal Pastes Tested

Did you uninstall firefox the last time you updated?
If not then uninstall it and re-install the newest version.

Trend Micro was on that system at one time and wasn't correctly removed. Go to the trend Micro website and get their un-installer and run it.

The RAM is PQI and Corsair, timings seem close but, RAM that is not from the same manufacturer and/or same lot number from the same manufacturer is often non-compatible.
Since OEM - Dell BIOS won't let you adjust the settings, chances are you will need to get new RAM.
The prices are very reasonable now, you should check into this. Find RAM that is listed as compatible with your laptop.

Let's see what memtest86+ says.
Even if it passes it doesn't mean it is not the problem.

Let us know the results.

 

[Interloper]

Alright, I went with the Arctic Silver - I've ordered some online so I'll take care of that in a few days.

I don't believe that I have updated Firefox. As I said earlier, its only a very recent install of Windows that's still reproducing this issue, and when I reinstalled Firefox on it, it was from the latest binary on their site.

I've uninstalled the Trend Micro software and ran their uninstaller from the site, as well.

I'll have a look into the RAM.

Thanks for the help, btw.

 

[Dave76]

You're welcome.

You should run memtest86+ will be beneficial to see the results.

Post the dump files if you get any more crashes.

Let us know what you decide to do.

 

[Interloper]

Alright, I ran memtest for 9 hours while I slept, it only came up to 3 passes, but there were no errors. I would agree in thinking that maybe heat is the issue here - either way, I'll wait to see how the thermal paste effects the heat dissipation and performance, before investing in replacement ram.

 

[Dave76]

Yes, agree, I would replace the thermal paste and test it for stability before buying RAM.

9 hours and 3 passes for 4GB RAM seems to be a bit long.
Was the test still running when you looked at it?

Let us know how the thermal paste applications is going.

 

[Interloper]

It was. I don't know how intensive memtest is on the CPU..? if it incubated too much heat perhaps the firmware scaled things back. I'll post again when I have, and have tested the thermal paste.

 

[Dave76]

Good point, give it another overnight run after you get the thermal paste applied.