PLEASE HELP! Strange random BSOD's

AMD Processors Forums - ATI 10.3 beta/preview

When I run a complete scan with Malwarebyes I get one error:

Hijack.DisplayProperties
Registry Data
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CurrentVersion\Policies\Explorer\NoActiveDesktopChanges

Can this be the cause?....

I had that exact same error in Malwarebytes... Have not idea what it would affect.

googled it... it's nothing

OK.. use prime95 and did a blend test.

After one minute I got the errors

"FATAL ERROR: Rounding was 0.5, expected less than 0.4

I read somewhere it is because your VCORE is too low... is that right? Should I set the voltage higher? I didn't overclock...

I already ran 7 passes last night with no errors..

I don't know what to do next.

You guys can't read any other possible cause in my minidumps?

You guys see anything strange here:

Just minutes ago when I was in my MSI control center (see image in post above) I got a BSOD:

THE DRIVER IS ATTEMPTING TO ACCESS MEMORY AFTER IT HAS BEEN FREED

Minidump:

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Windows\Minidump\030510-23290-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e48e50
Debug session time: Fri Mar  5 13:03:01.900 2010 (GMT+1)
System Uptime: 0 days 0:13:57.882
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D5, {fffff9802ab8cda0, 0, fffff880075fa0a8, 0}
Unable to load image \??\C:\Program Files (x86)\MSI\Live Update 4\LU4\msibios64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for msibios64.sys
*** ERROR: Module load completed but symbols could not be loaded for msibios64.sys
Could not read faulting driver name
Probably caused by : msibios64.sys ( msibios64+90a8 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff9802ab8cda0, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff880075fa0a8, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
 
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb30e0
 fffff9802ab8cda0 
FAULTING_IP: 
msibios64+90a8
fffff880`075fa0a8 81791058444b7e  cmp     dword ptr [rcx+10h],7E4B4458h
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  System
CURRENT_IRQL:  0
TRAP_FRAME:  fffff8800337e950 -- (.trap 0xfffff8800337e950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff9802ab8cd90
rdx=0000000000000100 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880075fa0a8 rsp=fffff8800337eae0 rbp=fffff80002e205f8
 r8=fffff88002f64180  r9=0000000000000100 r10=0000000000000080
r11=fffff8800337ea00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
msibios64+0x90a8:
fffff880`075fa0a8 81791058444b7e  cmp     dword ptr [rcx+10h],7E4B4458h ds:ea90:fffff980`2ab8cda0=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002cfc1e4 to fffff80002c7cf00
STACK_TEXT:  
fffff880`0337e7e8 fffff800`02cfc1e4 : 00000000`00000050 fffff980`2ab8cda0 00000000`00000000 fffff880`0337e950 : nt!KeBugCheckEx
fffff880`0337e7f0 fffff800`02c7afee : 00000000`00000000 00000000`00000001 fffff880`0337ea00 00000000`0000000a : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`0337e950 fffff880`075fa0a8 : 00000000`206b6444 fffff880`082bc830 fffff880`00000000 fffff980`2ab8cd90 : nt!KiPageFault+0x16e
fffff880`0337eae0 00000000`206b6444 : fffff880`082bc830 fffff880`00000000 fffff980`2ab8cd90 00000000`00000001 : msibios64+0x90a8
fffff880`0337eae8 fffff880`082bc830 : fffff880`00000000 fffff980`2ab8cd90 00000000`00000001 fffff880`075f349d : 0x206b6444
fffff880`0337eaf0 fffff880`00000000 : fffff980`2ab8cd90 00000000`00000001 fffff880`075f349d 00000244`00000000 : 0xfffff880`082bc830
fffff880`0337eaf8 fffff980`2ab8cd90 : 00000000`00000001 fffff880`075f349d 00000244`00000000 00000000`00000000 : 0xfffff880`00000000
fffff880`0337eb00 00000000`00000001 : fffff880`075f349d 00000244`00000000 00000000`00000000 00000000`00000000 : 0xfffff980`2ab8cd90
fffff880`0337eb08 fffff880`075f349d : 00000244`00000000 00000000`00000000 00000000`00000000 00000000`00022288 : 0x1
fffff880`0337eb10 00000244`00000000 : 00000000`00000000 00000000`00000000 00000000`00022288 fffff880`082bc830 : msibios64+0x249d
fffff880`0337eb18 00000000`00000000 : 00000000`00000000 00000000`00022288 fffff880`082bc830 fffff880`082bc830 : 0x244`00000000
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
msibios64+90a8
fffff880`075fa0a8 81791058444b7e  cmp     dword ptr [rcx+10h],7E4B4458h
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  msibios64+90a8
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: msibios64
IMAGE_NAME:  msibios64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  493f38e9
FAILURE_BUCKET_ID:  X64_0xD5_VRFK_msibios64+90a8
BUCKET_ID:  X64_0xD5_VRFK_msibios64+90a8
Followup: MachineOwner
---------