Windows crashing...

[Costa Rica's Army]

Hey everyone!

I have been suffering a problem with my PC and I think what and where the problem is. First off, I intalled Windows 8.1 a few months ago. In 29/04/2014 the PC crashed and saved the dump files. This is what I got from the file:

Dump File : 042914-6140-01.dmp
Crash Time : 29/04/2014 11:42:09 a.m.
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041793
Parameter 2 : fffff680`000a4ff8
Parameter 3 : 00000000`00000200
Parameter 4 : 00000000`000001ff
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+153fa0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.17041 (winblue_gdr.140305-1710)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042914-6140-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 298.528
Dump File Time : 29/04/2014 11:43:08 a.m.

The consequences was that my Windows page file went from 4.2GBs to 16GBs. Then today it crashed too with this:

Dump File : 051114-6250-01.dmp
Crash Time : 11/05/2014 02:47:29 p.m.
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041201
Parameter 2 : fffff680`00021020
Parameter 3 : 82100002`018de867
Parameter 4 : ffffe000`30d476a0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+153fa0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.17041 (winblue_gdr.140305-1710)
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\051114-6250-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 298.584
Dump File Time : 11/05/2014 02:48:20 p.m.

I have noticed that it usually crash when I have the PC powered on for a long periods of time, usually 1 or 2 days without turn in it off.

Here is the thing: Before, I had an old SSD of 64GBs, same PC, never had any kind of problems. Now I have a Samsung Evo of 250GBs, GTX 780 to SLI and another 8GB of RAM. I discard that the new GTX 780 SLI could be the problem since I have max out them both at 99% of use without any problem.

My aim goes to the Samsung EVO and RAM. With the EVO, there is a cool funtion named RAPID, it just cache memory into the RAM. I have already cache so many memory that it fulls my RAM not in use but in cache. Since my first crash, my page file went from 4.2GBs to 16GBs. My thoughts are that it could be a problem related with RAPID mode, ¿could it be that it fulls both of my RAM and then page file to make the PC crash? I heared that it could also be a bad RAM stick, I don't know about this but since the cache have already full my RAM without any problems does not that discard a bad RAM stick?

This are my thoughts. I let all to you.

Thanks!

EDIT: Funny thing is that both of the crashes happened after I fell asleep with Google chrome opened, and then just opened a new tap or scroll down the page and the BSOD comes...

[Joker]

Run a memory diagnostic test. The error seems RAM related. Is Windows set to manage the pagefile? It should say "8189 MB". A stick could be going bad or an application like Chrome might have a memory leak. It could help to reboot your PC every now and then and/or get 16GB if the RAM is getting full.

[Carlsberg]

disable rapid on the ssd. set page file manually to 200 min and 4096 max.

[Costa Rica's Army]

ReXx の投稿を引用：

Run a memory diagnostic test. The error seems RAM related. Is Windows set to manage the pagefile? It should say "8189 MB". A stick could be going bad or an application like Chrome might have a memory leak. It could help to reboot your PC every now and then and/or get 16GB if the RAM is getting full.

How do I do it?

I have 16GBs of RAM, my bad in there xD. Before the crash the page file was 4.2GBs and now is 16GBs. Windows manage the pagefile, I never dare to touch it.

[Silicon Vampire]

I *think* there may be an issue in the latest W8 update from microsoft as I have gotten three BSODs with similar errors and under very similar circumstances.These are the first I have seen in over two months of using W8.

[Costa Rica's Army]

How much time should it take to run the tool?

I just did it with the Windows tool and there was no problems at all acording to Windows. But I don't know if is that fast for 16GBs...

[Costa Rica's Army]

Silicon Vampire の投稿を引用：

I *think* there may be an issue in the latest W8 update from microsoft as I have gotten three BSODs with similar errors and under very similar circumstances.These are the first I have seen in over two months of using W8.

Could be too. I don't know if to blame RAPID or W8.1. RAPID mode works perfect but I don't know if is causing this problem too. Also my BSODs are very distant from dates...

[Azza ☠]

Rock up to Start (or whatever you use in Win 8) > Run > Type 'Event Viewer' (without the quotes) and select from the list.

Event Viewer (Local) > Custom Views > Administrative Events

Look for red errors around the time of those crashes. Check to see if it's application related or a conflicted for this log.

Note: Issue is 0x0000001A - A severe memory management error occurred.

First ensure the PC isn't overheating, move away from walls which might cause hot pockets (hot air which doesn't freely escape) and clean out the fans, ensure they are spinning, etc. Heat builds up over time, feel around the fans to see how hot they become after long periods.

Disable any overclocking.

Bad memory causes crashes, run memory diagnosics next - Windows might ask to perform this task on the next reboot, OK, then reboot and wait a while. You may have a defective memory stick. If you believe it to be the memory, remove all except one and test each if required (replace the defective).

If a SSD drive/cache is going bad, sometimes it will cause crashes then automatically try a reboot repair on the SSD cache. Disable Rapid, SSD Cache, etc, on your drives. See if that helps.

If you have updated chipset drivers, ensure they haven't been corrupted or badly installed. Check if you are using the latest hardware drivers and it is valid, especially the chipset and video drivers.

[Silicon Vampire]

Azza ☠ の投稿を引用：

Rock up to Start (or whatever you use in Win 8) > Run > Type 'Event Viewer' (without the quotes) and select from the list.

Event Viewer (Local) > Custom Views > Administrative Events

Look for red errors around the time of those crashes. Check to see if it's application related or a conflicted for this log.

Note: Issue is 0x0000001A - A severe memory management error occurred.

First ensure the PC isn't overheating, move away from walls which might cause hot pockets (hot air which doesn't freely escape) and clean out the fans, ensure they are spinning, etc. Heat builds up over time, feel around the fans to see how hot they become after long periods.

Disable any overclocking.

Bad memory causes crashes, run memory diagnosics next. You may have a defective memory stick.

If a SSD drive/cache is going bad, sometimes it will cause crashes then automatically try a reboot repair on the SSD cache. Disable Rapid, SSD Cache, etc, on your drives. See if that helps.

If you have updated chipset drivers, ensure they haven't been corrupted or badly installed. Check if you are using the latest hardware drivers and it is valid, especially the chipset and video drivers.

All fairly good advice but I assure you, there is not a thing misconfigured in my box...

[Costa Rica's Army]

Azza ☠ の投稿を引用：

Rock up to Start (or whatever you use in Win 8) > Run > Type 'Event Viewer' (without the quotes) and select from the list.

Event Viewer (Local) > Custom Views > Administrative Events

Look for red errors around the time of those crashes. Check to see if it's application related or a conflicted for this log.

Note: Issue is 0x0000001A - A severe memory management error occurred.

First ensure the PC isn't overheating, move away from walls which might cause hot pockets (hot air which doesn't freely escape) and clean out the fans, ensure they are spinning, etc. Heat builds up over time, feel around the fans to see how hot they become after long periods.

Disable any overclocking.

Bad memory causes crashes, run memory diagnosics next - Windows might ask to perform this task on the next reboot, OK, then reboot and wait a while. You may have a defective memory stick. If you believe it to be the memory, remove all except one and test each if required (replace the defective).

If a SSD drive/cache is going bad, sometimes it will cause crashes then automatically try a reboot repair on the SSD cache. Disable Rapid, SSD Cache, etc, on your drives. See if that helps.

If you have updated chipset drivers, ensure they haven't been corrupted or badly installed. Check if you are using the latest hardware drivers and it is valid, especially the chipset and video drivers.

The PC don't have any overeat issue. It's not OC. According to the Windows test everything is alright. Everything is updated.

I will Disable RAPID mode to see how it goes. The only problem that I see is that these BSODs are very distant. I will format my PC soon, not for this reason BTW.

About Windows events (Windows is in spanish, will try to write it in english):

At 2:48:16 P.M I got a Critic one: The system without turning it off first restarted cleanly. This error can occur if the system stopped responding, crashed or the power supply is interrupted unexpectedly. Type: Kernel-Power ID:41

At 2:48:21 P.M Type: EventLog ID: 6008. The previous system shutdown at 2:46:50 PM on 11/05/2014 was unexpected.

At 2:48:22 P.M Type: BugCheck ID: 1001. The computer restarts after a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041201, 0xfffff68000021020, 0x82100002018de867, 0xffffe00030d476a0). : C: \ Windows \ MEMORY.DMP dump was saved in. Report ID: 051114-6250-01.

And there are other three more. Two are from ISCTAgent ID: 1000.

ISCT - CAgentService::AgentServiceInit iSCT 3.0 BIOS implementation was not detected - fall back to support 2.x functionality

And

ISCT - CAgentService::AgentServiceInit NetDetect is now disabled since this is not a mobile platform

The other one is from Wininit ID: 11.

I'm looking at those ISCTAgent, they are from Intel Smart Connect Tech.

[Azza ☠]

Intel Smart Connect Technology is for when your computer enters sleep mode with it enabled it wakes up your computer every x amount of minutes to do updates such as scheduled updates.

Uninstall it if you don't use or disable sleep all together since on Desktop.

Consider going under your Control Panel > Power Options and switch to always on (if you don't wish it to sleep). You want 'High Performance' plan > Change plan settings > Never / Never. Also under the advance, set PCI Express > Link State Power Management to Off.

And/Or under your BIOS, also consider disabling any hard Sleep Mode which might be conflicting with your Windows Sleep. Flash updating the BIOS to the latest could also help.

The issue is most likely a conflict between your motherboard sleep and the Windows sleep? After leaving your PC alone for a while, it will enter sleep mode (hense why you don't get it that much and was sleeping on the keyboard when it last happened). This sleep mode state isn't an issue, but rather some BIOS settings also have sleep which can conflict the awake alert. In this case, ISCT (Intel Smart Connect Technology) was attempting to wake up your system possibly to update it, but failed causing the memory corruption/dump during the waking up process and then forcing the reboot.

Hope that helps.

[Costa Rica's Army]

Azza ☠ の投稿を引用：

Intel Smart Connect Technology is for when your computer enters sleep mode with it enabled it wakes up your computer every x amount of minutes to do updates such as scheduled updates.

Uninstall it if you don't use or disable sleep all together since on Desktop.

Consider going under your Control Panel > Power Options and switch to always on (if you don't wish it to sleep). You want 'High Performance' plan > Change plan settings > Never / Never. Also under the advance, set PCI Express > Link State Power Management to Off.

And/Or under your BIOS, also consider disabling any hard Sleep Mode which might be conflicting with your Windows Sleep. Flash updating the BIOS to the latest could also help.

The issue is most likely a conflict between your motherboard sleep and the Windows sleep? After leaving your PC alone for a while, it will enter sleep mode (hense why you don't get it that much and was sleeping on the keyboard when it last happened). This sleep mode state isn't an issue, but rather some BIOS settings also have sleep which can conflict the awake alert. In this case, ISCT (Intel Smart Connect Technology) was attempting to wake up your system possibly to update it, but failed causing the memory corruption/dump during the waking up process and then forcing the reboot.

Hope that helps.

Thanks for the replay:

I already disable the sleep mode in Windows, even the hibernation mode. PC is already set to maximun performance and all the tweaks.

This may sound stupid but, could it bee google Chrome? Both of my crashes were after using chrome and leaving it in idle for the whole morning.

[Azza ☠]

Not a stupid question - There was an actual issue in one of the old versions of Google Chrome hanging after resume from sleep/hibernate. However, in sure that would be fixed in the latest version (that was like 2 years ago or something). Firefox browser again had a similar issue in early version. Ensure your updated to the latest version and check your Chrome Extensions / Plugins if concerned. There's a wake on lan trigger, normally done via motherboard level. Certain tasks like download managers should keep the system from sleep, but a few don't and Windows messes up when attempting to background download large files while also dropping into a sleep state. I think they had a program called 'Insomnia' to prevent that... but it's a lot easiler disabling the sleep/hibernate and just manually turning off the monitor instead.

If your disabled Hibernation mode completely and don't want it anymore:

Open a Elevated Command Prompt. Start > Run > type 'cmd.exe' and right click -> Run As Admin. Then type 'powercfg -h off' and press Enter. This will get rid of the 'C:\hiberfil.sys' which frees up a good 16GB drive space (if your using 16GB RAM). If it didn't remove it, you can delete that file manually. Enabling Hibernation or going back and running 'powercfg -h on' which recreate it anytime you want it back.

[Costa Rica's Army]

Azza ☠ の投稿を引用：

Not a stupid question - There was an actual issue in one of the old versions of Google Chrome hanging after resume from sleep/hibernate. However, in sure that would be fixed in the latest version (that was like 2 years ago or something). Firefox browser again had a similar issue in early version. Ensure your updated to the latest version and check your Chrome Extensions / Plugins if concerned.

Will do.

I also have an issue with chrome with the SLI. It's not just me, it applies almost to everyone with SLI since is a common thread in the forums of the browser. Hope they will fix it soon.

Thanks you.

[Costa Rica's Army]

Quick question:

It's suppose that if I have 16GB of RAM, Windows should made a page file of 16GB true?

[Azza ☠]

Windows page file is a stupid memory dump overflow... back in the days when you had limited memory it would flow over onto hard drive when it required some more (this runs slower but stops any sudden out of memory issues from occuring). These days it should almost never be touched. However, when system managed it will simply match your memory size but if you have 16GB will probably never be used unless you have a major memory leak or something when majorly wrong.

Rule of thumb -

< 4GB - Keep system managed is highly recommended.

Match memory size or at least have it half (8GB memory = 4GB page)

After 8 GB of installed RAM, a page file larger than 4 GB becomes pointless. You might wish to leave it or reduce manually into a locked size.

For 16GB memory or greater (specially if on SSD where room is important) you can set as custom size for approx 1GB. Most people (including Microsoft) don't recommend you disable it. Microsoft will tell you leave it system managed as they do such an awesome job managing it (wasting space). But you only really need a 512MB - 1024MB page file for compatibility with some programs. It's best to have min and max sizes the same value in order to stop the file from being modified (SSD less writes = longer life span).