New
#21
USB stick is fine, that's what I use. No config settings are needed, just let her rip.
Aye aye captain, just going to try cold booting without the extra module and will get to it.
Update:
Cold booted with the extra module: BSOD
Cold booted without the extra module: BSOD
Running memtest with the extra module (the laptop was still cold) and got an immediate 130 errors (see attached screenshot).
Should I wait for this to finish 7 passes before trying without the extra module?
You can stop memtest86+ if you get any errors.
This test will keep going until you stop it, if it stops on it's own it means the test failed.
Remove the card you added, and run the test again, with the three original cards, for a minimum of 7 full passes.
If you get any errors you can stop the test.
RAM - Test with Memtest86+
These laptops with i7 CPUs and discrete graphics cards are known to overheat.
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.
Turning off SpeedStep will only increase the CPU temps.
Turn on Intel SpeedStep.
Turn off Turbo Boost.
Can you post the CPUZ snips of the CPU, Mainboard, Memory, and SPD tabs.
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
Post the SPD tab for the RAM that came with the laptop and the RAM card you added.
You were looking at the SPD tabs, they read the manufacturers recommended settings and are not the actual RAM settings.
The Memory tab will tell you what the RAM is running at.
Your last three crashes:
A PFN, the Page Frame Number list, is usually caused by memory corruption. This is likely from a RAM problem but in some circumstances can be caused by drivers.Code:STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b ) PROCESS_NAME: Wow-64.exe IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiDeleteAddressesInWorkingSet+11b ------------------------------------------------------------------------------------------------------------------------- STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 ) PROCESS_NAME: chrome.exe IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x1E_c0000005_R_nt!MiReplenishPageSlist+c0 ------------------------------------------------------------------------------------------------------------------------- STOP 0x0000001A: MEMORY_MANAGEMENT Usual causes: Device driver, memory, kernel A page table page has been corrupted. On a 64 bit OS, parameter 2 contains the address of the PFN for the corrupted page table page. PROCESS_NAME: fdm.exe FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35054
Let's test the RAM first as it is the most likely cause.
From your System Event Logs:
There are a lot of these.
These are indicating the CPU is overheating.Code:Event[34547]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2012-10-26T16:56:35.760 Event ID: 89 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Supes-PC Description: ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated. _PSV = 0K _TC1 = 0 _TC2 = 0 _TSP = 0ms _AC0 = 360K _AC1 = 328K _AC2 = 273K _AC3 = 273K _AC4 = 273K _AC5 = 0K _AC6 = 0K _AC7 = 0K _AC8 = 0K _AC9 = 0K _CRT = 379K _HOT = 0K _PSL - see event data. Event[8875]: Log Name: Application Source: Microsoft-Windows-WMI Date: 2012-11-02T18:09:33.000 Event ID: 10 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Supes-PC Description: Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
As mentioned above, enable SpeedStep and disable/turn off Turbo Boost in your BIOS.
Last edited by Dave76; 04 Nov 2012 at 09:26.
Hi Dave
Thanks for the reply, I've included the requested images as well as the most recent dump, the strange thing about the dump is that all previous cold boot crashes did not produce a dump file, the previous dump files were from crashes that happened after the laptop had been running for sometime.
What I have done so far:
- As previously mentioned, Memtest produced errors when all 4 modules were installed and the laptop was cold booted.
- Memtest also produced errors when I removed the extra module and the laptop was cold booted.
- Memtest also produced errors when I removed another of the modules (only 8GB in the laptop) and the laptop was cold booted.
- I reinstalled all modules and then ran a Memtest after the laptop had been running for about 10 minutes and no immediate errors were produced (in the previous tests errors were generated almost immediately after Memtest started) I left it running for about 10 minutes with no errors.
I've also re-enabled SpeedStep and will continue a Memtest on a warm system.
EDIT: There's no TurboBoost option in the BIOS, I've seen some custom unlocked BIOSs for this laptop but am very weary of flashing one of those at the moment.
EDIT 2: Added a snip of RealTemp after doing a Sensor Test with Prime 95
Last edited by iSupes; 04 Nov 2012 at 09:52.
I do not recommend using modified BIOS, if you have the latest updated BIOS from MSI, stay with that one.
With the laptop warm, run memtest86+ with all four RAM cards installed, as always if you get any errors you can stop the test.
Run for a full 7 passes, this will take several hours, best to run overnight.
You are having Cold Boot issues which can usually be fixed by adjusting CPU and RAM settings, since your OEM laptop doesn't have any of these settings available, you may have to send it to MSI for repairs.
Your last crash:
Still appears to be caused by the RAM.Code:STOP 0x00000024: NTFS_FILE_SYSTEM Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAILURE_BUCKET_ID: X64_0x24_nt!ExReinitializeResourceLite+145
The RAM may have corrupted files on your SSD/HDD.
Your Intel RST drivers are working with no errors so leave them installed.
EDIT:Code:Event[8885]: Log Name: Application Source: IAStorDataMgrSvc Date: 2012-11-02T18:11:35.000 Event ID: 0 Task: N/A Level: Information Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: Supes-PC Description: Service started successfully.
The CPU is definitely running hot, 100°C is max CPU temp.
Make sure there are no vents blocked, never put the laptop on a cloth/material surface, be sure it gets good ventilation. You may need to get a laptop cooler, be sure the fan lines up with the intake vent on the bottom of your laptop.
Check with your manual or MSI if there is a way to turn off the CPU Turbo mode.
Thanks again Dave
Will setup a Memtest to run overnight tonight and report back tomorrow morning.
Quick update before I setup an overnight Memtest:
I think the problem was one of the original RAM modules, I did cold boots while removing one module at a time and eventually I didn't receive any BSODs. Then I replaced one at a time and did cold boots till I did receive a BSOD, removed that module, replaced the others and haven't received a BSOD yet. I then replaced that module and did receive a BSOD (did this twice, just to make sure).
Will be setting up that Memtest with the 3 'working' modules to be run overnight. If all goes well will mark this as solved in the morning :) (I'm being cautiously optimistic this time)
Good trouble shooting, that was the next step I was going to suggest.
Run the memtest86+ with the three good RAM cards, overnight as you mentioned.
You're going to need some information to give MSI when you return the RAM, they will probably want the three original cards, run memtest86+ with the bad card only. You can stop the tests if you get any errors.
First on cold boot, then again on warm boot.
Let us know how the testing is going.