BSOD on new W7 Pro x64 system with QBPro2011, Office Small Biz 2007,

I'm getting BSOD's on a new PowerSpec B331 running Windows 7 Pro - 64 bit, 4gb mem, 1TB hard drive. It is part of a Workgroup. This is the second PowerSpec B331 that gets the BSOD's. When the BSOD's started on the first PowerSpec after installing QB Pro 2011, Dell 2335dn, Trend Micro, and Office, I took it back to Micro Center and they gave me a replacement unit no questions asked. The replacement unit got the same BSOD errors.

The system has the following applications installed:

1. QuickBooks Pro 2011;
2. Dell 2335dn MFS application suite;
3. Office Small Business 2007;
4. Trend Micro Titanium Internet Security2014;
5. Adobe Reader X (10.18);
6. Adobe Flash Player 10 ActiveX;
7. Malwarebytes Pro Trial;
8. TeamViewer 8.

All of the applications except Trend Micro Titanium are running with no issues on an old slow XP Pro desktop that I'm replacing.

QuickBooks is single user but its company files can also be opened by a single desktop in a domain on the network.

It is connected via a KVM to monitor, keyboard, and mouse.

The event viewer shows that system resources get exhausted and services start dying. It usually required a hard power off / on to recover and allow login.

Today no one was using the desktop and it had multiple Bugchecks throughout the day.

I was suspecting an issue with the Dell 2335dn MFS application suite and on 27-Nov-2013 removed their latest Nov 2013 version and installed an older version of it. The system ran until 02-Dec-2013 with no issues and then started with resource exhaustion again and eventually getting BSODs.

I have run the SF Diagnostic Tool and have attached the zip file.

Code:

There have been Bugchecks on:
 
12/2/2013 10:33:45 PM:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 12/2/2013 10:33:45 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Accounting-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000048, 0x0000000000000002, 0x0000000000000001, 0xfffff8800615d63e). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120213-16239-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="2013-12-03T06:33:45.000000000Z" />
<EventRecordID>15292</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>Accounting-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x000000d1 (0x0000000000000048, 0x0000000000000002, 0x0000000000000001, 0xfffff8800615d63e)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">120213-16239-01</Data>
</EventData>
</Event>
12/3/2013 4:31:46 PM:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 12/3/2013 4:31:46 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ACCOUNTING-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000044, 0xfffff80002eb67fc, 0xfffff88002ba4250, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120313-14773-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="2013-12-04T00:31:46.000000000Z" />
<EventRecordID>15660</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>ACCOUNTING-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x0000003b (0x00000000c0000044, 0xfffff80002eb67fc, 0xfffff88002ba4250, 0x0000000000000000)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">120313-14773-01</Data>
</EventData>
</Event>
12/4/2013 10:05:24 AM:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 12/4/2013 10:05:24 AM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ACCOUNTING-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000048, 0x0000000000000002, 0x0000000000000001, 0xfffff88005f4b63e). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120413-13821-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="2013-12-04T18:05:24.000000000Z" />
<EventRecordID>15804</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>ACCOUNTING-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x000000d1 (0x0000000000000048, 0x0000000000000002, 0x0000000000000001, 0xfffff88005f4b63e)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">120413-13821-01</Data>
</EventData>
</Event>
12/4/2013 8:34:22 PM:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 12/4/2013 8:34:22 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ACCOUNTING-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000048, 0x0000000000000002, 0x0000000000000001, 0xfffff8800685f63e). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120413-14258-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="2013-12-05T04:34:22.000000000Z" />
<EventRecordID>16097</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>ACCOUNTING-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x000000d1 (0x0000000000000048, 0x0000000000000002, 0x0000000000000001, 0xfffff8800685f63e)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">120413-14258-01</Data>
</EventData>
</Event>

Hi jrd53047,

Apparently your issue is with ASMedia USB3 drivers.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {48, 2, 1, fffff8800685f63e}

*** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
Probably caused by : asmthub3.sys ( asmthub3+963e )

Followup: MachineOwner
---------

Update the USB3 controllers from Station-Drivers - Asmedia drivers & firmwares.

Let us know the results.

OK, take your time. If there is any BSOD in between, let us know as per the posting instructions.

Before the teamviewer operation, there was another BSOD after I checked last time, on 07/12. What is strange there that the Asmedia USB3 driver filed again, despite of the driver update.

Code:

BugCheck C2, {7, 109b, 40f0010, fffffa800831b780}

*** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
*** WARNING: Unable to verify timestamp for asmtxhci.sys
*** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
GetPointerFromAddress: unable to read from fffff80003113100
GetUlongFromAddress: unable to read from fffff800031131c0
Probably caused by : asmthub3.sys ( asmthub3+3288 )
--------------------------------------------------------------------------------------
    Image name: asmthub3.sys
    Timestamp:        Sat Aug 17 00:58:54 2013 (520E7D76)

And, the latest crash dump, during TeamViewer session, caused due to insufficient system resources.

Code:

BugCheck 3B, {c0000044, fffff80002f0a7fc, fffff88009450250, 0}

Probably caused by : win32k.sys ( win32k!zzzChangeStates+7d2 )

Followup: MachineOwner
---------

The first parameter means ....

Code:

EXCEPTION_CODE: (NTSTATUS) 0xc0000044 - Insufficient quota exists to complete the operation

So it may be either memory or network, apparently.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Which network connection you actually use, the wireless one, or the wired one?
Apparently it appears that the Atheros device is disabled.

Code:

Qualcomm Atheros AR5BWB222 Wireless Network Adapter:    This device is disabled.

So you are using the wired network I think? The driver is really old.

Code:

fffff880`04652000 fffff880`046bc000   Rt64win7   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Wed Feb 16 14:33:57 2011 (4D5B92FD)
    CheckSum:         000754A7
    ImageSize:        0006A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Realtek. Get the Win7 and WinServer 2008 R2 Auto Installation Program dated 2013/11/26.

Out of curiosity, I am asking two more things ... may not be very essential. But as it is a branded desktop, these are better to know ..
Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Let us know the results.

250 watts are not any PSU to have. How minimum the usage may be. Get one at least of 450 watts, depending on your operations.