[309, like 288 Crashes on Load]

Nothing there except my reply to another user last month. Nothing at all official.

 

The diction was a bit odd, no? He addressed some unknown observer, referring to me in the third person. Is that the usual voice here?

[309, like 288 Crashes on Load]

I will PM this user

 

Was I supposed to get a PM? Here?

[309, like 288 Crashes on Load]

This time, with 309, I got consistent crashes in debug mode **with only Peripherals selected**. My peripherals are pretty vanilla, except for the Sansa Clip+ hanging off USB today, which doesn't affect the crash. See profile at

 

http://speccy.pirifo...6xCgEhSjD51eFFr

 

(Made with 113) The only thing at all out of the ordinary is an ABS brand Cherry-switch USB kb.

 

Back to 113, which continues to work - on Win7-32, unlike all the XP crashes here.

 

I have a .dmp, but it's too big to upload

[Text Size Adjust]

There you have it - your more doddering users need the option of a larger font size, larger spinners and larger temp-graph boxes. I'd say just let the interface respond to ctrl-mousewheel or ctrl-+/-, but that wouldn't enlarge the widgets.

 

19x10 monitors do have their downside.

[1.14.288 Crashes on Load]

All previous versions have worked well. 1.14 hangs with spinner, and Windows 7-32's appcrash msg pops up after 8-10 seconds. I can't get anything useful out of 1.14 /debug, but here's the event log text of one crash. Yell if you need msinfo, etc.

 

-Frank

 

==========

Log Name: Application

Source: Application Error

Date: 12/13/2011 3:48:54 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: FRH-P55

Description:

Faulting application name: Speccy.exe, version: 1.14.0.288, time stamp: 0x4eca52cc

Faulting module name: Speccy.exe, version: 1.14.0.288, time stamp: 0x4eca52cc

Exception code: 0xc0000005

Fault offset: 0x000626f3

Faulting process id: 0x1628

Faulting application start time: 0x01ccb9d89b1b5f7e

Faulting application path: C:\Program Files\Speccy\Speccy.exe

Faulting module path: C:\Program Files\Speccy\Speccy.exe

Report Id: de79cda4-25cb-11e1-875e-002511ccb0bf

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2011-12-13T20:48:54.000000000Z" />

<EventRecordID>9095</EventRecordID>

<Channel>Application</Channel>

<Computer>FRH-P55</Computer>

<Security />

</System>

<EventData>

<Data>Speccy.exe</Data>

<Data>1.14.0.288</Data>

<Data>4eca52cc</Data>

<Data>Speccy.exe</Data>

<Data>1.14.0.288</Data>

<Data>4eca52cc</Data>

<Data>c0000005</Data>

<Data>000626f3</Data>

<Data>1628</Data>

<Data>01ccb9d89b1b5f7e</Data>

<Data>C:\Program Files\Speccy\Speccy.exe</Data>

<Data>C:\Program Files\Speccy\Speccy.exe</Data>

<Data>de79cda4-25cb-11e1-875e-002511ccb0bf</Data>

</EventData>

</Event>