Jump to content

General Crash problems post-Mod-Organizer


Recommended Posts

After NMM began derping out hard (not installing large mods, generally being useless) I installed Mod Organizer 2 and redownloaded all my mods through it.

I have the latest versions of NVSE, NVAC, etc...but FNV is still crashing rather randomly, stuttering hard, et cetera.

 

Load order:

 

# This file was automatically generated by Mod Organizer.
FalloutNV.esm
DeadMoney.esm
HonestHearts.esm
OldWorldBlues.esm
LonesomeRoad.esm
GunRunnersArsenal.esm
ClassicPack.esm
MercenaryPack.esm
TribalPack.esm
CaravanPack.esm
YUP - Base Game + All DLC.esm
SomeguySeries.esm
Interior Lighting Overhaul - Core.esm
IWR.esm
ELECTRO-CITY - CompletedWorkorders.esm
FCOMaster.esm
rePopulated Wasteland.esm
FINAL Seachlight Airport NCR.esm
SaxxonsQuestPack.esm
Project Nevada - Core.esm
Project Nevada - Equipment.esm
Project Nevada - Rebalance.esp
DWCNV.esm
ELECTRO-CITY - Highways and Byways.esm
World Of Secrets.esm
Project Nevada - Cyberware.esp
More Perks.esm
KhanInitiation.esp
JokerineStripMall.esm
ZionTrail.esm
JIP Selective-Fire.esm
WMVM.esm
SCAV.esm
Interior Lighting Overhaul - L38PS.esm
Project Nevada - Extra Options.esm
YUP - NPC Fixes (Base Game + All DLC).esp
Big Bears.esp
Uncut Wasteland.esp
Project Nevada - Rebalance Complete.esp
WeaponModsExpanded.esp
WMX-DLCMerged.esp
TweaksandChanges.esp
The Mod Configuration Menu.esp
ISFX.esp
Project Nevada - All DLC.esp
EVE FNV - ALL DLC.esp
Wasteland Veteran Trait.esp
WMX-ArenovalisTextures.esp
FCO - NPC Changes.esp
MJVEOutpost.esp
FCO - The Last Few Edits + DLC.esp
outsidebets.esp
TLD_Travelers.esp
The True Revival of Luxury - An Ultra-Luxe Overhaul.esp
TheSinkRemodel.esp
TfaT2.esp
CNR_Beta.esp
ILO - Searchlight Airport.esp
Unofficial Patch Plus.esp
WMX-EVE-AllDLCMerged.esp
TheLozza's_Gasmasks_V2.esp
NorthRoad.esp
NewVegasUncut 123457 Merged.esp
JGrahamCompanion.esp
BetterSpringBattle.esp
ZionTrail-NV.esp
IWR - Rebuilt.esp
ArmorClothes.esp
CCO - Ulysses Companion.esp
Guns.esp
MM Headhunter.esp
T60.esp
ADAM Complete.esp
lexx-hh-letter-english.esp
Book of Steel.esp
Better Burned Man.esp
pipboy2500_edisleado.esp
dD - Enhanced Blood Main NV.esp
IMPACT.esp
CASM with MCM.esp
BetterBurnedMan - JGrahamCompanion Patch.esp
ADAM - MERGE.esp
THOR.esp
JIP Companions Command & Control.esp
JIP Improved Recipe Menu.esp
JIP Realistic Weapon Overheating.esp
NewVegasBounties.esp
NewVegasBountiesII.esp
TheInheritance.esp
Russell.esp
Fortune Canyon.esp
Mojave Arsenal.esp
WMX-POPMerged.esp
PaintYourWeapon.esp
The Town of Vice - A Gomorrah Overhaul.esp
MainStoryAlterations.esp
Ragdolls.esp
RoxieFollower.esp
A Guide To Revenge.esp
Project Nevada - WMX.esp
Project Nevada - EVE All DLC.esp
Wastelandthings.esp
CasinoHeists.esp
FNV NPCs Travel.esp
KingOfTheRing.esp
MojaveExtended100.esp
Near Death.esp
Sierra Madre Safehouse - ILO.esp
TheCollector.esp
CourierRangerArmorV2.esp
CheckpointGary.esp
Paint Your Weapon - Honest Hearts Edition.esp
Real Recoil.esp
The Law Won.esp
Unofficial Patch Plus - Project Nevada Patch.esp
FCO - Russell.esp
FCO - Saxons Quest Collection.esp
ILO - YUP Patch.esp
Project Nevada - Cyberware Additions.esp
Old World Duster.esp
Gas Masks of the World - PN Patch.esp
Interior Lighting Overhaul - Ultimate Edition.esp
ILO - New Vegas Bounties II.esp
ILO - New Vegas Bounties.esp
merged patch.esp

 

 

 

I'm at my wit's end here. Any help you can give would be great.

 

EDIT:

 

Here's the NVAC report:

 

03162941 _ NewVegasAntiCrash FalloutNV.exe
03162941 _ 03A50000 07050000 nvac.dll
03162941 _ 0D800000 05010040 nvse_1_4.dll
03162941 _ 772F0000 0A0042EE ntdll.dll
03163147 ; script 'Expression Error: SYNTAX' (34015EFA).
03163153 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163155 ; script 'Expression Error: SYNTAX' (34015EFA).
03163158 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163200 ; script 'Expression Error: SYNTAX' (34015EFA).
03163203 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163205 ; script 'Expression Error: SYNTAX' (34015EFA).
03163208 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163210 ; script 'Expression Error: SYNTAX' (34015EFA).
03163213 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163216 ; script 'Expression Error: SYNTAX' (34015EFA).
03163218 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163221 ; script 'Expression Error: SYNTAX' (34015EFA).
03163240 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163243 ; script 'Expression Error: SYNTAX' (34015EFA).
03163251 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163253 ; script 'Expression Error: SYNTAX' (34015EFA).
03163256 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163304 ; script 'Expression Error: SYNTAX' (34015EFA).
03163307 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163309 ; script 'Expression Error: SYNTAX' (34015EFA).
03163312 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163317 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163319 ; script 'Expression Error: SYNTAX' (34015EFA).
03163324 ; script 'Expression Error: SYNTAX' (34015EFA).
03163327 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163332 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163340 ; script 'Expression Error: SYNTAX' (34015EFA).
03163342 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163348 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163350 ; script 'Expression Error: SYNTAX' (34015EFA).
03163353 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163358 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163409 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163412 ; script 'Expression Error: SYNTAX' (34015EFA).
03163414 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163417 ; script 'Expression Error: SYNTAX' (34015EFA).
03163419 ; script 'Expression Error: SYNTAX' (3D075B4A).
03163421 ; script 'Expression Error: SYNTAX' (34015EFA).
03163439 U 76E4D722 E06D7363 KERNELBASE.dll
03163439 ^ 00ECD240 00000010 FalloutNV.exe
Edited by Ragnarok101
Link to comment
Share on other sites

Don't recognize that "ntdll.dll" file, but it seems to be the source of the SYNTAX error messages. It's not part of the basic game nor any of the common NVSE plugins I'm using (which includes NX).

Check your Windows "Event Viewer" for errors under the "Application" and "System" filters. Suspect you are getting an Application Error: "Exception code: 0xc0000005". In which case, please see 'Issue: Application load Windows error(s)' entry under the 'Solutions to Starting the game problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

Also see the 'Solutions to Performance problems' section regarding your stutters, etc.
All of the following may not apply to your specific situation, but are worth repeating anyway.

* Be aware that one error may mask a number of other errors, which will not appear until those masking them have been resolved. Building a stable game consists of resolving each problem individually until none remain, and then realizing that every change you make thereafter (including updates to mods already installed) run the risk of introducing new problems. Be prepared to revert to a previous save if you do so.

* Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

* Are you running Win10? Did you get the "Fall Creator's Update" of 2017 (FCU aka "RedStone 3")? Do you have "New Vegas Stutter Remover" (NVSR) installed? If all three are "true", then please see the 'Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)' and 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' entries in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

* If you are suddenly having a "slowdown" or lag; or a lack of sound; or problems getting NVSE to load, or really anything new unexpectedly, please see the 'Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. This may be due to a Windows Update for the "Meltdown and Spectre Vulnerabilities".

* Are you using the 4GB Patcher? If not, please see the 'Maximizing use of memory' section of the wiki "FNV General Mod Use Advice" article.

* The game has "memory leaks". Getting 2-3 hours before a CTD is pretty good. You might want to try using the tool "Memclean", which periodically (you can set the interval; default is every 15 minutes) tells the OS to perform it's built-in "clean up" of memory. It has a "mini-monitor" that displays memory usage. Doesn't seem to hurt and might help.

* If you are using the full 4GB of memory, most likely your CTD problem (now or in the future) is the default "heap size" is too small. It's so common you might as well deal with it now. Please see the 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu') entry in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

* Move any "inactive" plugins out of the game "Data" folder. They count against the "plugin cap" because they get loaded by the game engine if found, and can cause "Missing Master" problems. Please see the wiki "Missing Masters" article if you get that error message.

* Don't install every optional file for a mod. Read the install instructions carefully. Optional files need to be selected on a "case by case" basis. For example: with any mod you usually only need one ESP (and possibly one ESM) "base" file depending upon whether you have all the DLCs active or not. Only if you don't have them all active do you need to install any specific DLC versions if there is an "Ultimate Edition/All/Merged DLC" version.

* "Compatibility patches" to make one mod work with another need to be placed after (as in "physically lower, higher numbered") in the "load order" than all of the plugins they are designed to make compatible. ESMs should always be placed at the top (lowest numbered) positions in the "load order", followed by the related ESPs though they can be separated from their ESMs by other plugins. "LOOT" does a good job of determining those basic orders. Getting the "load order" incorrect will cause "Missing Master" errors as well.

FYI: The "pre-order packs" (Caravan, Classic, Mercenary, and Tribal; available now in the "Courier's Stash" addon), are not considered "DLCs" by most mods and "compatibility patches". So their absence should not deter you from using "All DLC Merged" plugins. When in doubt, follow the process in the wiki "Missing Masters" article to confirm they are not "master files" for that plugin.

* Don't install compatibility patches for mods you do not have installed/active (e.g. get rid of any "TTW" patches if you aren't running TTW).

* Do not use an "Auto-purge" mod for game play. (That was old advice from before we knew better.) They are designed for debugging by mod creator's only, according to the author of the JIP extensions to NVSE. See the 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu', "Cause-2", "Solution-3" entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide for the game settings that do the same job.

* Please see the paragraph about "auto-saves" under the 'Essentials for Getting Started' section of the wiki "FNV General Mod Use Advice" article. If you have been using the built-in "auto-save" feature and you get the endless "roulette wheel" when loading a save game, then your current save game file is corrupted and you will have to either go back to a save before the corruption occurred (hard to tell) or start over.

* If you have more than one mod that makes any change to the same record or set of records in the vanilla game, then you really need to use a "Merge Patch File" with that collection of mods. Please see the 'Third Rule: The Rule of One' and 'Merge Patch File' sections of the wiki "FNV General Mod Use Advice" article.
-Dubious-
Link to comment
Share on other sites

Okay, here's the Application viewer:

Log Name: Application
Source: Application Error
Date: 6/3/2018 4:17:44 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-0SS3TQE
Description:
Faulting application name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50ed
Faulting module name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50ed
Exception code: 0xc0000409
Fault offset: 0x00ae1c3c
Faulting process id: 0x1e78
Faulting application start time: 0x01d3fb775172adfd
Faulting application path: C:\games\steam\steamapps\common\Fallout New Vegas\FalloutNV.exe
Faulting module path: C:\games\steam\steamapps\common\Fallout New Vegas\FalloutNV.exe
Report Id: 2a995b6a-878a-4001-940a-ba3860110d23
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-06-03T20:17:44.353485600Z" />
<EventRecordID>3540</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-0SS3TQE</Computer>
<Security />
</System>
<EventData>
<Data>FalloutNV.exe</Data>
<Data>1.4.0.525</Data>
<Data>4e0d50ed</Data>
<Data>FalloutNV.exe</Data>
<Data>1.4.0.525</Data>
<Data>4e0d50ed</Data>
<Data>c0000409</Data>
<Data>00ae1c3c</Data>
<Data>1e78</Data>
<Data>01d3fb775172adfd</Data>
<Data>C:\games\steam\steamapps\common\Fallout New Vegas\FalloutNV.exe</Data>
<Data>C:\games\steam\steamapps\common\Fallout New Vegas\FalloutNV.exe</Data>
<Data>2a995b6a-878a-4001-940a-ba3860110d23</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
However, it's not an application error. I've gotten a couple of 'this runtime has requested to be terminated in an unusual way' sort of warnings, though.
I've got 4GB, have modified NVSR as instructed, have a merged patch, and have the game in C:/Games/Steam... rather than in the x86 folder.
Searching for ntdll.dll on Google reveals it's part of the Windows installation, not sure why it would be affecting my game...
Link to comment
Share on other sites

Double-checking, it appears to be triggered by a cell change: it always happens when approaching the Goodsprings Cemetery. Without the NVSR fix, it crashes, and produces the error logs in nvac and the event viewer. With it, it freezes, and I have to restart my computer to get rid of it.

 

Gonna try disabling cell change saves or something of the nature if that's a thing in CASM.

Edited by Ragnarok101
Link to comment
Share on other sites

Alright, went to the Goodsprings Saloon instead of the graveyard. Got inside, game crashed a couple seconds later.

 

03194841 _ NewVegasAntiCrash FalloutNV.exe
03194841 _ 067C0000 07050000 nvac.dll
03194841 _ 0D900000 05010040 nvse_1_4.dll
03194841 _ 772F0000 0A0042EE ntdll.dll
03195017 ; script 'Expression Error: SYNTAX' (3D075B4A).
03195020 ; script 'Expression Error: SYNTAX' (34015EFA).
03195049 ; script 'Expression Error: SYNTAX' (3D075B4A).
03195051 ; script 'Expression Error: SYNTAX' (34015EFA).
03195054 ; script 'Expression Error: SYNTAX' (3D075B4A).
03195056 ; script 'Expression Error: SYNTAX' (34015EFA).
03195107 M 61662064 C0000096
03195107 r 005C0760 00000000 FalloutNV.exe
03195107 h 005C0760 8B08894D FalloutNV.exe
03195107 h 005C0765 8B500489 FalloutNV.exe
03195107 h 005C076B 8B400889 FalloutNV.exe
03195107 m 2773257E 00000000
03195107 r 004839E7 00000002 FalloutNV.exe
Could Windows just really hate FNV now?
Link to comment
Share on other sites

Here's what I could find out about that exception code: http://answers.microsoft.com/en-us/w...9b31bf5?auth=1. In this case the faulting application is FNV.

Seems to be a registry issue for sure. Have you tried or considered a repair install? Here's a tutorial on how to do that if you haven't : Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums.

-Dubious-
Link to comment
Share on other sites

Tried again after reinstalling exe, got THIS error:

 

03200935 _ NewVegasAntiCrash FalloutNV.exe
03200935 _ 039B0000 07050000 nvac.dll
03200935 _ 0D800000 05010040 nvse_1_4.dll
03200935 _ 77740000 0A0042EE ntdll.dll
03201101 U 7639D722 E06D7363 KERNELBASE.dll
03201101 ^ 00ECD240 00000010 FalloutNV.exe
Going to use system file checker and try to fix the dlls, will report back if successful or not.
Link to comment
Share on other sites

The description page of NVAC tells you how to decypher it's log file.

03200935 _ 77740000 0A0042EE ntdll.dll = "_" entries are informative, relaying that NVAC was loaded and the base address of various DLLs. "77740000" is a memory address. Note this is beyond that of "KERNELBASE.dll", but close to it.

 

03201101 U 7639D722 E06D7363 KERNELBASE.dll = "u" entries are Unhandled exceptions reported from the Unhandled Exception Filter; these are crashes. "7639D722" is a memory address. "E06D7363" is an informative value; in this example, the version number of "KERNELBASE.dll".

 

03201101 ^ 00ECD240 00000010 FalloutNV.exe = "^" entries are informative, relaying possible return address to main code from external library code. "00ECD240" is a memory address. "00000010" is an informative value, not sure what of.

 

So your core problem is with "KERNELBASE.dll". There should be a Windows "Event Viewer" "System" entry related to this file.

 

-Dubious-

Link to comment
Share on other sites

The description page of NVAC tells you how to decypher it's log file.

03200935 _ 77740000 0A0042EE ntdll.dll = "_" entries are informative, relaying that NVAC was loaded and the base address of various DLLs. "77740000" is a memory address. Note this is beyond that of "KERNELBASE.dll", but close to it.

 

03201101 U 7639D722 E06D7363 KERNELBASE.dll = "u" entries are Unhandled exceptions reported from the Unhandled Exception Filter; these are crashes. "7639D722" is a memory address. "E06D7363" is an informative value; in this example, the version number of "KERNELBASE.dll".

 

03201101 ^ 00ECD240 00000010 FalloutNV.exe = "^" entries are informative, relaying possible return address to main code from external library code. "00ECD240" is a memory address. "00000010" is an informative value, not sure what of.

 

So your core problem is with "KERNELBASE.dll". There should be a Windows "Event Viewer" "System" entry related to this file.

 

-Dubious-

 

I can't seem to find the darn thing. There's no events related to it that I can be certain about.

 

Here's a few that might be near the correct time, they're the only errors and warnings I could find.

 

 

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 6/3/2018 8:08:32 PM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: DESKTOP-0SS3TQE
Description:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2018-06-04T00:08:32.733178700Z" />
<EventRecordID>6175</EventRecordID>
<Correlation />
<Execution ProcessID="900" ThreadID="1264" />
<Channel>System</Channel>
<Computer>DESKTOP-0SS3TQE</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Launch</Data>
<Data Name="param4">Windows.SecurityCenter.WscDataProtection</Data>
<Data Name="param5">Unavailable</Data>
<Data Name="param6">NT AUTHORITY</Data>
<Data Name="param7">SYSTEM</Data>
<Data Name="param8">S-1-5-18</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 6/3/2018 8:08:32 PM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: DESKTOP-0SS3TQE
Description:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2018-06-04T00:08:32.732181300Z" />
<EventRecordID>6174</EventRecordID>
<Correlation />
<Execution ProcessID="900" ThreadID="1320" />
<Channel>System</Channel>
<Computer>DESKTOP-0SS3TQE</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Launch</Data>
<Data Name="param4">Windows.SecurityCenter.WscBrokerManager</Data>
<Data Name="param5">Unavailable</Data>
<Data Name="param6">NT AUTHORITY</Data>
<Data Name="param7">SYSTEM</Data>
<Data Name="param8">S-1-5-18</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 6/3/2018 8:07:42 PM
Event ID: 37
Task Category: (7)
Level: Warning
Keywords:
User: SYSTEM
Computer: DESKTOP-0SS3TQE
Description:
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Event Xml:
<System>
<Provider Name="Microsoft-Windows-Kernel-Processor-Power" Guid="{0F67E49F-FE51-4E9F-B490-6F2948CC6027}" />
<EventID>37</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>7</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2018-06-04T00:07:42.793462000Z" />
<EventRecordID>6173</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="220" />
<Channel>System</Channel>
<Computer>DESKTOP-0SS3TQE</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Group">0</Data>
<Data Name="Number">1</Data>
<Data Name="CapDurationInSeconds">71</Data>
<Data Name="PpcChanges">1</Data>
<Data Name="TpcChanges">0</Data>
<Data Name="PccChanges">0</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 6/3/2018 8:07:42 PM
Event ID: 37
Task Category: (7)
Level: Warning
Keywords:
User: SYSTEM
Computer: DESKTOP-0SS3TQE
Description:
The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Event Xml:
<System>
<Provider Name="Microsoft-Windows-Kernel-Processor-Power" Guid="{0F67E49F-FE51-4E9F-B490-6F2948CC6027}" />
<EventID>37</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>7</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2018-06-04T00:07:42.793416900Z" />
<EventRecordID>6172</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="500" />
<Channel>System</Channel>
<Computer>DESKTOP-0SS3TQE</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Group">0</Data>
<Data Name="Number">2</Data>
<Data Name="CapDurationInSeconds">71</Data>
<Data Name="PpcChanges">1</Data>
<Data Name="TpcChanges">0</Data>
<Data Name="PccChanges">0</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 6/3/2018 8:07:42 PM
Event ID: 37
Task Category: (7)
Level: Warning
Keywords:
User: SYSTEM
Computer: DESKTOP-0SS3TQE
Description:
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Event Xml:
<System>
<Provider Name="Microsoft-Windows-Kernel-Processor-Power" Guid="{0F67E49F-FE51-4E9F-B490-6F2948CC6027}" />
<EventID>37</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>7</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2018-06-04T00:07:42.793361900Z" />
<EventRecordID>6171</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="224" />
<Channel>System</Channel>
<Computer>DESKTOP-0SS3TQE</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Group">0</Data>
<Data Name="Number">0</Data>
<Data Name="CapDurationInSeconds">71</Data>
<Data Name="PpcChanges">1</Data>
<Data Name="TpcChanges">0</Data>
<Data Name="PccChanges">0</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 6/3/2018 8:07:42 PM
Event ID: 37
Task Category: (7)
Level: Warning
Keywords:
User: SYSTEM
Computer: DESKTOP-0SS3TQE
Description:
The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Event Xml:
<System>
<Provider Name="Microsoft-Windows-Kernel-Processor-Power" Guid="{0F67E49F-FE51-4E9F-B490-6F2948CC6027}" />
<EventID>37</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>7</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2018-06-04T00:07:42.793343500Z" />
<EventRecordID>6170</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="204" />
<Channel>System</Channel>
<Computer>DESKTOP-0SS3TQE</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Group">0</Data>
<Data Name="Number">3</Data>
<Data Name="CapDurationInSeconds">71</Data>
<Data Name="PpcChanges">1</Data>
<Data Name="TpcChanges">0</Data>
<Data Name="PccChanges">0</Data>
</EventData>
</Event>
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...