PLEASE HELP! Strange random BSOD's

[wzzly]

Hello all,

I have a huge problem. I just got my new build PC and I'am having BSOD's. Especialy when I working in Photoshop or in games.

The BSOD's have different error causes all the time if I look at the minidumps...

Can somebody please read my attached last 10 minidumps to see what's wrong??

It also happens alot when play 3D games like GTA4. And when doing things in photoshop (applications that use alot of RAM)

Some files that de minidump told might be the cause are:

- ntoskrnl.exe
- atipmdag.sys
- win32k.sys
- dxgkrnl.sys

But I don't know how to read the dumpfiles any further...

I thought it might be my RAM but I scanned it with memtest86+ and no errors where found. I updated all my drivers and uninstalled and reinstalled my videodrivers. I don't know what to do next... Please help because I need this computer for my work.

Hope somebody can help.

Thanks in advance

 

[Jonathan_King]

Some possible causes I see for this are you video card drivers, DirectX, Daemon Tools, and your network drivers.

I would recommend updating all of those, removing Daemon tools.

If you need help finding drivers that need to be updated, use this tool: Driver Easy - Free Driver Detect & Download Software

You can also try a system files check. Open an elevated command prompt and enter sfc /scannow.

Good luck!

~JK

 

[wzzly]

Hej JK,

thanks for your fast reply. I update everything with the program you told and uninstalled deamon tools. I hope I don't get any BSOD's anymore then.

But does that mean I can't use deamon tools anymore at all??

 

[wzzly]

Ok just playing GTA4 to test if the BSOD's were gone... after 2 minutes another BSOD:

SYSTEM_SERVICE_EXCEPTION

atipmdag.sys

Already have updated the new ATI drivers.

Included the minidump

any suggestions?

 

[Jonathan_King]

Still looks like your atipmdag.sys driver.

Try downloading the latest drivers for your card here: https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/10-2_vista64_win7_64_dd.exe

 

[wzzly]

I get redirected to this site when I use that link: Advanced Micro Devices, Inc. - Unauthorized Download

But I already have latest ATI 10.2 drivers...

 

[wzzly]

Update:

- BSOD's still apear when gaming/ photoshop etc. But mostly with games.
- Did a chkdsk /r --> no errors
- Did a sfc /scannow --> no errors
- Used memtest86+ for 7 passes --> no errors
- Updated my ATI graphic card drivers
- Updated BIOS

I read somewhere that some people have BSOD's because there RAM voltages are not set correctly in their BIOS. My RAM should have voltages of 1.5V. In my BIOS I see the next numbers:

DRAM Voltage:
- auto: 1.500V
- min: 0.906V
- max: 1.898V

DDR_VREF_CA_A:
- auto: 0.750V
- min: 0.450V
- max: 1.150V


DDR_VREF_CA_B:
- auto: 0.750V
- min: 0.450V
- max: 1.150V


DDR_VREF_DA_A:
- auto: 0.750V
- min: 0.450V
- max: 1.150V

DDR_VREF_DA_B:
- auto: 0.750V
- min: 0.450V
- max: 1.150V

PCH:
- auto: 0.050V
- min: 0.451V
- max: 1.953V

Are these numbers OK?

What's the next step? Please help...

 

[jl3nz]

I am having similar random BSODs as well. I have updated DirectX, Sound Card, Network, and Video Drivers. I too have ATI's CCC 10.2. I have ran Chkdsk (no errors), Memtest86+ (no errors)... so I am at a loss as well. I have a sneaky suspicion that it is the ATI 10.2 drivers. When I had ATI 10.1 drivers, I didn't really get BSODs at all, but I did get weird vertical video lines that locked the computer that they fixed in the 10.2 version. Ever since I have updated to 10.2 I get a ridiculous amount of random BSODs. I have included some of my most recent minidump files.

 

[wzzly]

I have also tried the new BETA drivers 10.3 , but they have the same problem... so if it's the driver... then we probably have to wait till 10.4...

 

[jl3nz]

Where did you find the BETA 10.3 drivers?

 

[wzzly]

AMD Processors Forums - ATI 10.3 beta/preview

 

[wzzly]

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?....

 

[jl3nz]

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

 

[wzzly]

googled it... it's nothing

 

[wzzly]

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...

 

[win7clutz]

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...

Unlikely... Troubleshoot memory.

 

[Jonathan_King]

Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

 

[wzzly]

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:

 

[wzzly]

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:

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
---------

 

[Jonathan_King]

I would strongly recommend stop overclocking. Reset all values to the factory defaults.