Random BSOD help needed

xstevex · 28 May 2011

Good evening,
I have been trying to work out why I keep getting random BSOD's?

I have copied below a report from debugging tool!
I built my computer back at the end of March 2011 (So not long ago) and have had approx 50 BSOD's and each time doing completely different things, even just logging on and 10 minutes later just BSOD or could be 10 hours later just web browsing. I cant seem to pin it down to a spesific task?

I have run RAM tests and all are fine, ZIP files attched as requested.

System info below:-

OS Name Microsoft Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name STEVE-PC
System Manufacturer MSI
System Model MS-7309
System Type x64-based PC
Processor AMD Phenom(tm) 9350e Quad-Core Processor, 2000 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. V10.5, 01/04/2011
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume4
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name Steve-PC\Steve
Time Zone GMT Daylight Time
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.75 GB
Available Physical Memory 1.98 GB
Total Virtual Memory 7.50 GB
Available Virtual Memory 5.07 GB
Page File Space 3.75 GB
Page File C:\pagefile.sys

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\052811-21512-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c5c650
Debug session time: Sat May 28 15:11:47.689 2011 (UTC + 1:00)
System Uptime: 0 days 2:04:12.609
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffffffffffd8, 2, 0, fffff80002a8bfcb}
Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffffffffffd8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a8bfcb, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc6100
ffffffffffffffd8
CURRENT_IRQL: 2
FAULTING_IP:
nt!ExpScanGeneralLookasideList+a0
fffff800`02a8bfcb 418b40d8 mov eax,dword ptr [r8-28h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880035169b0 -- (.trap 0xfffff880035169b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000fd3e3770
rdx=00000000001f4000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a8bfcb rsp=fffff88003516b40 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000004 r10=00000000001f4000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!ExpScanGeneralLookasideList+0xa0:
fffff800`02a8bfcb 418b40d8 mov eax,dword ptr [r8-28h] ds:6ba0:ffffffff`ffffffd8=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a962a9 to fffff80002a96d00
STACK_TEXT:
fffff880`03516868 fffff800`02a962a9 : 00000000`0000000a ffffffff`ffffffd8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03516870 fffff800`02a94f20 : 00000000`00000000 ffffe7ce`8cd28b4d fffff8a0`088f8c70 fffff800`02c34400 : nt!KiBugCheckDispatch+0x69
fffff880`035169b0 fffff800`02a8bfcb : 00000000`00000000 fffff800`02cc6c40 00000000`00000000 00000000`00000007 : nt!KiPageFault+0x260
fffff880`03516b40 fffff800`02a81820 : 00000000`00000001 00000000`00000008 00000000`00000001 fffff800`02cc6c40 : nt!ExpScanGeneralLookasideList+0xa0
fffff880`03516ba0 fffff800`02a81d62 : 00000000`00000008 fffff880`03516c10 00000000`00000001 fffffa80`00000000 : nt!ExAdjustLookasideDepth+0x40
fffff880`03516bd0 fffff800`02d3332e : fffffa80`03db5b60 00000000`00000080 fffffa80`03cd5040 00000000`00000001 : nt!KeBalanceSetManager+0x1be
fffff880`03516d40 fffff800`02a88666 : fffff880`03163180 fffffa80`03db5b60 fffff880`0316dfc0 ffe3efb7`afa5d5b3 : nt!PspSystemThreadStartup+0x5a
fffff880`03516d80 00000000`00000000 : fffff880`03517000 fffff880`03511000 fffff880`03516700 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExpScanGeneralLookasideList+a0
fffff800`02a8bfcb 418b40d8 mov eax,dword ptr [r8-28h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!ExpScanGeneralLookasideList+a0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b
FAILURE_BUCKET_ID: X64_0xA_nt!ExpScanGeneralLookasideList+a0
BUCKET_ID: X64_0xA_nt!ExpScanGeneralLookasideList+a0
Followup: MachineOwner
---------
1: kd> .trap 0xfffff880035169b0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000fd3e3770
rdx=00000000001f4000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a8bfcb rsp=fffff88003516b40 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000004 r10=00000000001f4000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!ExpScanGeneralLookasideList+0xa0:
fffff800`02a8bfcb 418b40d8 mov eax,dword ptr [r8-28h] ds:6ba0:ffffffff`ffffffd8=????????
1: kd> .trap 0xfffff880035169b0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000fd3e3770
rdx=00000000001f4000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a8bfcb rsp=fffff88003516b40 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000004 r10=00000000001f4000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!ExpScanGeneralLookasideList+0xa0:
fffff800`02a8bfcb 418b40d8 mov eax,dword ptr [r8-28h] ds:6ba0:ffffffff`ffffffd8=????????

Please someone help as I thought I new enough about basic PC maintainance to solve this but it's beaten me

Steve

mgorman87 · 28 May 2011

You uploaded the actual exe file. Please upload the correct information and we'll go from there.

xstevex · 28 May 2011

Sorry mgorman87 that was an imbarrasing error!!!

Attached report as requested.

mgorman87 · 28 May 2011

There were only two crashes in the report. You state you've had 50?? I do see in your event logs that you are having a lot of BSODs. Do you run any sort of system cleaner? Follow the instructions in the next link to make sure your minidumps are set up correctly Blue Screen of Death (BSOD) Posting Instructions - Windows 7 & Vista - Tech Support Forum

Code:

Event[368]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-05-26T17:47:59.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Steve-PC
  Description: 
Fault bucket X64_0xc4_f6_VRF_UCOREW64+fdc, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=X64_0xc4_f6_VRF_UCOREW64+fdc&ID=6e19b607-f727-4c09-a101-b3f3df797e59
Cab Id: 0

Verified enabled dump that is pointing to UCOREW64.sys. That driver belongs to the ASRock BIOS upgrade software. Please uninstall the software.

Code:

 Log Name: Application
  Source: Windows Error Reporting
  Date: 2011-05-26T17:47:56.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Steve-PC
  Description: 
Fault bucket X64_0xc4_0_VRF_avgtdia+7bbf, type 0
Event Name: BlueScreen
Response: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=X64_0xc4_0_VRF_avgtdia+7bbf&ID=fb2bb632-9a06-492c-b919-3c542ffa0da8
Cab Id: 0

Verified enabled dump blaming avgtdia. This belongs to your AVG anti virus. Please uninstall and replace with Microsoft Security Essentials

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+
2. Prime95 - Run all three tests for 3-4 hours each or until fail - https://www.sevenforums.com/tutorials...t-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 10:11:47.689 2011 (UTC - 4:00)
System Uptime: 0 days 2:04:12.609
Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!ExpScanGeneralLookasideList+a0
BiosReleaseDate = 04/01/2011
SystemManufacturer = MSI
SystemProductName = MS-7309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 16 15:00:42.200 2011 (UTC - 4:00)
System Uptime: 0 days 4:06:51.745
Probably caused by : ntkrnlmp.exe ( nt!ObfDereferenceObjectWithTag+93 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x19_20_nt!ObfDereferenceObjectWithTag+93
BiosReleaseDate = 10/13/2010
SystemManufacturer = MSI
SystemProductName = MS-7309
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

xstevex · 28 May 2011

I also noticed AVG as a possible problem so I uninstalledf that 2 days ago??? I now have F-Secure.
I used to use CCleaner to clean the registry but after lots of bad reports I still use it but not to clean the registry! (I hope that CCleaner hasn't corupted my registry?)
How to I uninstal UCOREW64? My last BIOS upgarde was though MSI directly, I had V.A.30 and MSI had A.50.

I will now run the above tests as requested and let you know the reults.

mgorman87 · 28 May 2011

CCleaner erases your mini dump files. So I would cease use on that and try and get some more BSODs.

The crashes from UCORE were from two days ago. How long ago did you update your BIOS? And did you do it yourself?

xstevex · 28 May 2011

I updated my BIOS on the 25th May and yes I did it myself. I did it though MSI live update.
I will not use CCleaner again. My BIOS version has updated and it does say that it has updated to the latest version??? Perhaps I havn't done something that I should off??

mgorman87 · 28 May 2011

xstevex said:

I updated my BIOS on the 25th May and yes I did it myself. I did it though MSI live update.
I will not use CCleaner again. My BIOS version has updated and it does say that it has updated to the latest version??? Perhaps I havn't done something that I should off??

No the BIOS update was fine. I believe that a driver was installed on your computer to allow the BIOS update and for whatever reason driver verifier didn't like it and caused the crash. But it appears it's no longer on the system so you shouldn't need to worry about it.

xstevex · 28 May 2011

Oh good I though for minute I had buggered up the BIOS !!!!