Squawks

[seekermeister]

It seems ironic that W7 x64 only has 3GBs of memory available, out of 4GBs installed. I know that this is normal for x32 versions of older Windows, but I would have thought that it would be like XP x64, and have almost all of the memory available. Perhaps this will change when W7 becomes final, but I'm not going to hold my breath.

I'm been having a series of problems running any kind of game (except those that are part of the OS), and it seems that the root cause is the same in each case...at least the data in the Event Viewer is the same in every instance:

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 5/29/2009 8:31:55 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Newhope
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff96000112a4f, 0xfffff880093b4050, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052909-27328-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-05-30T01:31:55.000000000Z" />
<EventRecordID>3432</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>Newhope</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x0000003b (0x00000000c0000005, 0xfffff96000112a4f, 0xfffff880093b4050, 0x0000000000000000)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">052909-27328-01</Data>
</EventData>
</Event>

Does anyone have any idea of how to change or fix either problem?

 

[YupYup]

Sorry still trying to figure out the title.

 

[Snufffed]

You might check the following links:

[URL="http://support.microsoft.com/kb/941410"]The computer crashes, and you receive a "Stop 0x0000003b" error message after you enable large image-based page files in Windows Server 2003[/URL][URL="http://support.microsoft.com/kb/941410"]
[/URL]

or

[URL="http://en.community.dell.com/forums/t/19276326.aspx"]Blue screen error - DELL COMMUNITY[/URL][URL="http://en.community.dell.com/forums/t/19276326.aspx"] 
May 25, 2009 ... 2008. and blue screen error message is below. STOP: 0x0000003B (0x00000000C0000005, 0Xfffff80002597897, 0Xfffffa60163442E0, ...
en.community.dell.com/forums/t/19276326.aspx - 188k
[/URL]

 

[seekermeister]

Sorry, old habit. Definition = Gigs, problems, defects, etc. I was going to list more, but then decided to focus on the main problems.

 

[seekermeister]

You might check the following links:

[URL="http://support.microsoft.com/kb/941410"]The computer crashes, and you receive a "Stop 0x0000003b" error message after you enable large image-based page files in Windows Server 2003[/URL][URL="http://support.microsoft.com/kb/941410"]
[/URL]

or

[URL="http://en.community.dell.com/forums/t/19276326.aspx"]Blue screen error - DELL COMMUNITY[/URL][URL="http://en.community.dell.com/forums/t/19276326.aspx"] 
May 25, 2009 ... 2008. and blue screen error message is below. STOP: 0x0000003B (0x00000000C0000005, 0Xfffff80002597897, 0Xfffffa60163442E0, ...
en.community.dell.com/forums/t/19276326.aspx - 188k
[/URL]

Thanks, the first link is interesting, but it only seems to apply to Windows Server 2003. The second link offers nothing.