Crashes with "Priv_Instruction"??

[sys12189 21]

I was playing a session the other day and went into a zoning-w2w-apartments spree. I forgot time passing and didn't save for about 1.5 hours. As I was hovering over one of the custom Hotels with the query tool it crashed. I assumed it was the normal 'ACCESS_VIOLATION' but it wasn't. It wasn't anything I ever saw before (I had access violation and another one with INT_DIVIDE_BY_ZERO caused by a bad plugin).

This is the first 20 or so lines of the exception report:

 

Exception time: 09/08/2015, at 00:51:04.
Exception code: 0xC0000096 (-1073741674) PRIV_INSTRUCTION.
Current thread ID: 10552 (0x00002938).
Version information:
Application/module path: C:\Program Files (x86)\Maxis\SimCity 4 Deluxe\Apps\SimCity 4.exe
Application/module version name: SimCity 4
Application/module version: 1.1.638.0
System version: Windows NT 6.1
System memory: 3980 Megabytes total, 2008 Megabytes free.

Exception module:  .
Exception address: 0x12ddce50. Section:Offset: 0x00:0x00000000.

Registers
   EAX: 0012ddc3
   EBX: 00000000
   ECX: 12ddca04
   EDX: 12ddca04
   ESI: 1567c014
   EDI: 12ddca04
   CS:EIP: 0023:12ddce50
   SS:ESP: 002b:0018f80c  EBP:0000006e
   DS:002b  ES:002b  FS:0053  GS:002b
   Flags: 00010286

 

Compare that with the 'normal' crashes I get from time to time (usually only after not saving for 2~3 hours straight. Nowadays I usually have an alarm so I save every 30 minutes or so)

Exception time: 08/27/2015, at 16:36:58.
Exception code: 0xC0000005 (-1073741819) ACCESS_VIOLATION.
Current thread ID: 6076 (0x000017bc).
Version information:
Application/module path: C:\Program Files (x86)\Maxis\SimCity 4 Deluxe\Apps\SimCity 4.exe
Application/module version name: SimCity 4
Application/module version: 1.1.638.0
System version: Windows NT 6.1
System memory: 3980 Megabytes total, 1752 Megabytes free.

Exception module:  C:\Program Files (x86)\Maxis\SimCity 4 Deluxe\Apps\SimCity 4.exe.
Exception address: 0x0065ed40. Section:Offset: 0x01:0x00257d40.

Registers
   EAX: 0018f6f8
   EBX: 0018f6fc
   ECX: 00000000
   EDX: 000000c1
   ESI: 00000000
   EDI: 43888d9c
   CS:EIP: 0023:0065ed40
   SS:ESP: 002b:0018f6c0  EBP:0018f6f7
   DS:002b  ES:002b  FS:0053  GS:002b
   Flags: 00210246

The new error came up after I installed a bunch of new plugins. Perhaps they could be the problem...? On the other hand my game still runs for long hours with good stability with a 900MB plugin(not very large!) unlike many others who say they CTD within the hour, even just with NAM....

 

see how there is nothing next to the 'exception module' and that EBX is 00000000 (unlike the bottom one with ECX, ESI at all-zero)

  Edited September 8, 2015 by sys12189  

[rsc204 21,862]

Honestly the exception report doesn't really provide any help with tracking down the problem since the codes it produces are something only those with familiarity of the code could probably decipher.

If you know which lot you queried that caused this to happen, see if the same thing happens again when querying it. If it consistently causes the CTD, you've a faulty modded lot. If it doesn't CTD anymore, then more than likely this was a hiccup, the cause of which is likely to remain unknown.

[sys12189 21]

I know the query lot when it crashed (Name was Sokos Hotel Viru or something) so I queried it again. It used to work fine, and no reason for it to crash now. I made the situation as close as possible (being growable buildings....) and the query works flawlessly. Not that one (and I'm pretty sure a faulty query usually brings up ACCESS_VIOLATION...)

[rsc204 21,862]

Occasionally, despite what I find to be quite a reliable game which I push as a modder more than most, such hiccups do occasionally materialise out of nowhere. If it's not replicable then I wouldn't spend a great deal of time worrying about it.

[A Nonny Moose 8,262]

Executing a privileged instruction in slave mode is usually some kind of operating system hiccup and usually occurs immediately after a dispatch when the processor is switching from O/S mode to slave state.  You are lucky your whole machine didn't go down.  After a thing like that, just for insurance, I would do a cold boot, then try to reproduce the error.  It might have been a random (power) transient, but it does no harm to check.