Random BSODs and applications crashes on a fresh Win7 install

[Dave76]

RMA the Corsair RAM, see if new ones will run better.
Is the 'VDDNB Over Voltage' still set to 1.350v?

It does sound like a motherboard or PSU issue.
Check your CMOS battery voltage again with HWinfo64, it's VBAT, should be at least 3.0v.

A problem PSU can cause the issues you have mentioned.
Do you have another PSU to test with?
Do you have a lot of USB devices plugged in?
Any other peripherals that might be drawing power?

 

[R4ndom]

Hi, will definitely rma the corsair as it's useless.

The vddnb voltage is set to 1.350v.

The vbat maintants a stable 3.288. I attach a HW monitor report on voltages, temps, etc. First column indicates current voltage/temperatures, then minimum and maximum values.

I only have a webcam and a printer as usb devices, both used very occasionally. As mentioned before, crashes happen when pc is on idle and never under load.

Unfortunately no other psu to try with, as I spent money on RAMs that are also defective

I attach dumps with latest crashes - one from 18 march and 2(!) today in a space of 15minutes (strange it happened exactly 1 week after the last one) but I guess it's just a coincidence and this board has serious problems with RAMs as it won't even take corsairs, which are supposed to be compatible with.

Shall I upload screenshots of BIOS as well, maybe other tweaks can be done so that this finally becomes stable after 4 months? What do you think?

You asked what kind of errors I get in the event viewer: well, windows explorer crashes, firefox crashes, skype crashes, SCII crashes, basically everything crashes and then I get a blue screen. but it all happens in an irregular pattern. there is however one thing in common: the BS is always preceeded by app crashes - since this morning virtually everything has been crashing.
apart from that "side by side error" code 72

thanks!

 

[Dave76]

You can post the BIOS screen shots and I'll take a look and see if anything needs adjustments.

Last two crashes.

Again it's blaming the kernal, which the debugger will do if it can't find the real cause.

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88003185618
Arg3: fffff88003184e70
Arg4: fffff80002ee137a

Debugging Details:
------------------


EXCEPTION_RECORD:  fffff88003185618 -- (.exr 0xfffff88003185618)
ExceptionAddress: fffff80002ee137a (nt!ExAcquireFastMutex+0x000000000000001a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003184e70 -- (.cxr 0xfffff88003184e70)
rax=0000000000000001 rbx=fa8005c7dd8004c0 rcx=fa8005c7dd8004c0
rdx=fffffa8003a9b040 rsi=fffff88003185a01 rdi=0000000000000000
rip=fffff80002ee137a rsp=fffff88003185850 rbp=fffff8000306f260
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002e53000
r11=fffff88003185850 r12=fffff8a009c5a010 r13=fffff8a009b1ea10
r14=fffff8a009c5a300 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ExAcquireFastMutex+0x1a:
fffff800`02ee137a f00fba3100      lock btr dword ptr [rcx],0 ds:002b:fa8005c7`dd8004c0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003101100
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsTeardownFromLcb+fb
fffff880`0122688b 83bfc000000000  cmp     dword ptr [rdi+0C0h],0

FAULTING_IP: 
nt!ExAcquireFastMutex+1a
fffff800`02ee137a f00fba3100      lock btr dword ptr [rcx],0

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff8800122688b to fffff80002ee137a

STACK_TEXT:  
fffff880`03185850 fffff880`0122688b : fffff8a0`09c5a010 fffff800`0306f260 fffff880`03185a01 fffff880`012aecc1 : nt!ExAcquireFastMutex+0x1a
fffff880`03185880 fffff880`012ac63c : fffffa80`049a3ce0 fffffa80`04cb4180 fffff8a0`09c5a010 fffff8a0`09c5a3a8 : Ntfs!NtfsTeardownFromLcb+0xfb
fffff880`03185910 fffff880`0122e0e2 : fffffa80`049a3ce0 fffffa80`049a3ce0 fffff8a0`09c5a010 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`03185990 fffff880`012bc193 : fffffa80`049a3ce0 fffff800`0306f260 fffff8a0`09c5a010 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`031859d0 fffff880`012ab357 : fffffa80`049a3ce0 fffff8a0`09c5a140 fffff8a0`09c5a010 fffffa80`04cb4180 : Ntfs!NtfsCommonClose+0x353
fffff880`03185aa0 fffff800`02ed9361 : 00000000`00000000 fffff800`031c5700 fffff800`030d0800 fffffa80`00000005 : Ntfs!NtfsFspClose+0x15f
fffff880`03185b70 fffff800`03169f7a : 00000000`00000000 fffffa80`03a9b040 00000000`00000080 fffffa80`03943840 : nt!ExpWorkerThread+0x111
fffff880`03185c00 fffff800`02ec09c6 : fffff880`02fd5180 fffffa80`03a9b040 fffff880`02fdffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03185c40 00000000`00000000 : fffff880`03186000 fffff880`03180000 fffff880`031858a0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsTeardownFromLcb+fb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

STACK_COMMAND:  .cxr 0xfffff88003184e70 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsTeardownFromLcb+fb

BUCKET_ID:  X64_0x24_Ntfs!NtfsTeardownFromLcb+fb

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff680007ffc00
Arg3: db5000010e48a867
Arg4: fffffa80047a86f0

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41201

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ef183e to fffff80002e95c80

STACK_TEXT:  
fffff880`0a37f878 fffff800`02ef183e : 00000000`0000001a 00000000`00041201 fffff680`007ffc00 db500001`0e48a867 : nt!KeBugCheckEx
fffff880`0a37f880 fffff800`02e60be1 : fffffa80`062b6180 fffff880`0107d751 00000000`00000001 db500001`0e48a867 : nt! ?? ::FNODOBFM::`string'+0x13c82
fffff880`0a37f8c0 fffff800`02e60843 : fffffa80`047a86f0 fffffa80`06c84b30 fffffa80`06c84b30 00000000`fff80000 : nt!MiQueryAddressState+0x2b1
fffff880`0a37f910 fffff800`0316f434 : 00000000`00000000 00000000`fff81000 fffffa80`047a86f0 00000000`03e4f9f0 : nt!MiQueryAddressSpan+0x73
fffff880`0a37f980 fffff800`02e94f13 : ffffffff`ffffffff fffffa80`04fdcb60 00000000`00000000 00000000`006ae158 : nt!NtQueryVirtualMemory+0x382
fffff880`0a37fa70 00000000`77b0154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`006ae138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b0154a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+13c82
fffff800`02ef183e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13c82

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ecdc9f2

FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13c82

BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13c82

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

There is a couple new BIOS versions, update your BIOS to M5A78L/USB3 BIOS 1003

Run Check Disk again, let's see if there are any more errors to fix.

Did you increase the CPU voltage as mentioned in post #59?
Give the CPU voltage a bump, increase the CPU Over Voltage an additional 0.10v.

At this point, if none of the above help, you may need to Clean Install of Windows 7.

I still think it could be the PSU or motherboard, as indicated by the random changes in the RAM settings.
The best way is to borrow a PSU, if you can't then consider getting a new one. Antec, Corsair and Seasonic are good, recommended brands.

 

[R4ndom]

Thanks Dave for answering. I'll post screenshots of the BIOS shortly. Now I flashed the BIOS with the new version you linked to. Funny thing though, I had to flash it from a FAT32 formatted usb drive, as it would report "invalid boot block" when trying to flash from a NTFS usb device. In fact, I had lost hope that Asus would ever realease any update to their BIOS for this MB, that's why I wasn't even checking their website for updates. And still if you look at the changelog almost every single of them concerned stability/memory compatibility issues. So I hope finally they resolved the problems, will see how it works and report back. Yes, I had upped the cpu voltage to the suggested values. I hope however that all those problems were due to the MB instability that, hopefully, has been fixed with the last update - fingers crossed

 

[Dave76]

Yes, we can hope the BIOS upgrade helps.

All BIOS flashes that I know about have to be done from a fat32 formatted USB stick.

Let us know how your system is running.
Good luck.

 

[R4ndom]

Hi Dave,

Unfortunately the BIOs update didn't help, I attach a file with 6-7 latest BSODs which mostly happened, again, while I was doing nothing on the PC, the latest one when I was writing this post, as a consequence, I'm writing it again...

I re-checked the Corsair RAMs, as sending them for RMA means paying 12EUR for shipment and I'm not even sure it's the RAMs fault, and the reason for that is the fact that I re-ran the memtest on them and it was stable for 17 hours. Upon 2nd test, it ran for 30mins and spit out errors, subsequent test showed the same. But after BIOS tweaks I was able at least to boot them.

I rolled back to older graphics drivers, as some people reported problems with latest ones, to no avail, still BSODing. I will test with my ancient 7600 GS.

I just ran a chkdisk - in fact it ran itself after a ...th BSOD, found some errors (I think, as it showed something linked to appcrash explorer.exe and I think corrected something.

And again, skype crashes even before it launches, same for firefox, starcraft reporting corrupted files and crashing as well - during startup and closing, and once even during gameplay.

Do you think starcraft crash logs could shed some light on the issues I'm having?

Another weird thing I noticed: I loaded the seatools to recheck the hdd and both disks are duplicated, e.g. in the main screen I see each of them twice... wow, I think that adds even more spice to the problems I already have.

I attach screenshots of my BIOS as well as jcgriff zip with latest crashes. Thanks!


View attachment 205839

View attachment 205840

View attachment 205841

View attachment 205842

View attachment 205843

View attachment 205844

 

[Dave76]

Download HWiNFO64 and post a screen shot of the 'System Summary' and complete 'Sensor Status' pages.
I want to compare them to the last one.

Be sure to ground yourself, use a grounding strap. Check that the RAM and graphics cards are firmly connected, remove, inspect and re-seat.
Manually set the RAM to manufacturers specs, first 4 timings to 9-9-9-24, leave the rest on 'Auto', and Command Rate of 2T.
Run memtest86+, again, if you get any errors you can stop the test.
One error is too many.

If you get errors with the RAM set at these timings and voltages, there is a problem.
Possibilities are the RAM, PSU, motherboard, or CPU.

Remove the CPU cooler, pull off the CPU and check for bent pins.

 

[R4ndom]

Thanks Dave, will try these. However, I recently checked the CPU cooler, installed a new one over the stock one and I did it AFTER I had been having all the issues mentioned since the beginning of this thread.

Another issue in the meantime, I ran sfc /scannow command at boot and it won't even run, just a cursor blinking following a phrase "this may take long time, blablabla". If I try to run the same under Windows, it stops after 10% saying Windows resource protection cannot perform the requested operation".

As for RAM timings, the manufacturer recommended ones are 9-9-9-20 @ 1333 and that's what I set. 9-9-9-24 was for the Corsair, but since I had even bigger stability issues, I rolled back to OCZ.

HW screenshots as requested.

View attachment 205870

View attachment 205871

 

[Dave76]

When you changed the CPU cooler did you take off the CPU and check for bent pins?
This can be ruled out at no cost, only time.

Disconnect everything that is not required for the system to function.
All externals, sound cards, etc.
Try using different keyboard and mouse.

The PSU voltages are low or not reported correctly.
In post #30:
+3.3V 1.860 V
AVCC3 4.056 V
+12V 8.016 V
Same in the last HWiNFO64, your system wouldn't run at these voltages, but it still should be looked into.
It's not unusual for newly released CPUs to have incorrect information read by these apps.
Make sure you have the latest version of HWiNFO64, 3.94-1550.

Check in your voltages in the BIOS: Power > Hardware Monitor Configuration > VCORE Voltage, 3.3V Voltage, 5V Voltage, 12V Voltage
Page 2-18 in your manual.

D/L Speccy and click 'Motherboard' and check the voltages.

Your issues and wide range of BSoDs indicate a hardware problem, narrowing it down is the difficult part.
The HDDs seem ok, but have errors, RAM and crashes are erratic.

At this point, you can check if everything is connected properly: CPU bent pins, RAM and GPU seated correctly, cables etc.
Then you are going to have to check the major components, either by check new or known good components in your system or your components in a known good system.
I would start with the PSU.

Here are a couple of links to PSU testing.

Power Supply Troubleshooting Guide

PC Hardware Troubleshooting, Part 1 - Isolating ATX Power Supply and related circuit faults

 

[R4ndom]

I swapped my GPU with an old GF7600GS 256MB and haven't had any app crash or bsod since, but I only did it a couple of hours ago, so can't judge definitely if it helped.

Before, I had BSODs for the last 2-3 days immiediately after logging in to windows. After swapping the card, removing old drivers, installing new ones (here strange things, as nvidia drivers wouldn't install with a message "could not find adapter" or smth like that). I had to install first MS drivers and only then the nvidia ones would install.

So far, so good, now I'm only wondering if it's PSU or GPU's fault, since 7600 draws a way less power than 550Ti.

Voltages in BIOS are reported correctly, must be buggy software.

Forgot to mention that I ran prime95 last night and it showed some hardware issues, halting after 49minutes of tests in "blend" mode.

 

[Dave76]

Find a supplier with a good return policy, get a 650 or 750w PSU.
If it works with your 550Ti you've found the answer. If it doesn't work you can return it.

Be sure to get a good quality brand, others can cause issues.

Recommended brands:
Seasonic
Corsair
PC Power & Cooling
Antec

 

[R4ndom]

Hi, it crashes as well with the old GS7600. Today I had problems getting into windows, 2-3 times it reported it couldn't load desktop, start some shell command, then finally I got 2 bsods in a row - I attach the zip with them.

also MSEssentials would not start before the BSODs occured. I'll rescan the PC for virus/malware.

Since the last post I wrote, there have been numerous app crashes, including the windows ones. So I'm afraid GPU isn't the answer here.

It's difficult to find such a supplier here, I would say the market is painfully supplier-oriented and not client-oriented

 

[Dave76]

Your last crash.

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 000000000470d001
Arg3: 000000000000b4a7
Arg4: fffff70001080000

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
LAST_CONTROL_TRANSFER:  from fffff80002ee2717 to fffff80002e8bc80

STACK_TEXT:  
fffff880`0384a7d8 fffff800`02ee2717 : 00000000`0000001a 00000000`00041284 00000000`0470d001 00000000`0000b4a7 : nt!KeBugCheckEx
fffff880`0384a7e0 fffff800`02ebd0e0 : fffff700`01080000 ca700000`305dc867 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4ac3
fffff880`0384a820 fffff800`02e784bf : fffffa80`00000000 00000000`047e0fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x4e8
fffff880`0384a9e0 fffff800`02e8af13 : ffffffff`ffffffff 00000000`03e4e2a0 00000000`03e4e268 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0384aae0 00000000`772e14fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03e4e1d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772e14fa

MsMpENG is the antimalware detection engine used by Windows Defender/MSE. There is something interfering with it.
Did you re-run the previous anti-virus un-installers?

Just re-read the thread, at this point I would suggest replacing the PSU with a 650 or 750w PSU.
Be sure to get a good quality one, you can check the brands supplier at this site: POWER SUPPLY REVIEW DATABASE
Recommended brands:
Corsair
Seasonic
Antec
XFX
PC Power & Cooling

The OEM to look for is Seasonic, CWT.

 

[R4ndom]

Hi Dave,
thanks for advice. Before I decide to buy a new PSU though, I'd like to ask whether it's possible that a faulty PSU can cause memory management errors and file corruption, MSE startup errors, application crashes as well as all the other issues that I described so far? I don't doubt it can, but I'd like some more background info if possible
Since last time, with the old 7600GS installed I was still getting problems, windows explorer crashing immediately on windows startup, weird desktop compositions - for example the bar with quick launch icons would get every now and then non-transparent, HWmonitor would crash before launch, etc.
I put back the 550Ti, Windows booted up fine, I could use the PC for one day w/o problems. Then it started again, windows explorer wouldn't load, I also got 4 blue screens today.
On Asus website I noticed they put yet another BIOS update, just 1 month after the previous one which is supposed to again "improve stability". It's marked with 1103 and dates from April. We'll see, but for me there's clearly a problem with MB as well, as when I loaded the new BIOS, windows booted up just fine and has been stable for the last couple of hours. As if system's performace was degrading after using it for some time and needed continuous reset of parameters.
So before cashing out another 100euros for a new PSU, I'll see what their last update brings about.

 

[Dave76]

At this point the options are:

• Faulty motherboard, BIOS update may help solve this and "improve stability" makes it worth a try
• Faulty CPU, maybe bent pins
• Faulty PSU

A failing PSU will give many different kinds of errors and crashes. If the system is not getting smooth continuous voltage it can cause all issues you have described and have been experiencing.

 

[R4ndom]

Hi Dave and thanks for the tips. I had another BSOD today while running prime95 in blend torture test (I think it was still running, but I'm not sure, because i was not in front of the PC when it happened, returned after some time to the room just to see the windows log in screen and then info that it had BSODed). I attach the dump file as usual, can you make anything out of it? it's the one from 17 May. So it seems yet another BIOS update for nothing, although for 2 days it ran smoothly, without any errors.

I notice something else which seems strange to me: no matter how I distribute RAM sticks in the slots (they're black-blue and black blue) it always tells me that it runs in dual channel (CPU-Z), while it should only be in dual when put blue-blue and black-black - this is not the case. I have them now in black-blue next to each other and it still says dual channel. Possibly off-top, but it looks strange to me.

After rebooting the PC (I ran chkdsk on c drive which again gave no errors) I was getting every 5 seconds windows explorer crash errors. Reboot again, errors gone...

EDIT: prime95 ran for 12 hours straight all night and detected no errors, no BSOD either..., I'll start OCCT and leave it for a while to see.

 

[Dave76]

Your motherboard manual says when installing two RAM cards they should be in the Blue slots.
Strange the it is showing dual channel when in bule-black slots.
Programs like CPU-Z can get the wrong information on new CPUs, always a good idea to cross check with other programs like HWiNFO64.

The last crash:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!TimersProc+142
Usual causes:  System service, Device driver, graphics driver, ?memory
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

What was the CPU temp during the prime95 test?

It's good that prime95 pasted the second time.
Let us know how the OCCT test went.

 

[R4ndom]

Hi Dave,

thanks for answering. I reset the RAMs back in blue-blue configuration today and also switched to the Corsair ones, the reason for that being another BSOD while PC was left on idle.

CPU-Z reports as dual, but this is correct, as I put them in the configuration according to the manual. I couldn't find info about dual-single memory setting in HWinfo.

PC had functioned perfectly for the last 3 days though with OCZ RAMs in, I did prime test for more than 12 hours without errors, during which CPU temps didn't exceed 43C, OCCT the same, no warnings, PC stable as a rock.

I notice that the las crash from 17/05 seems to be different from previous ones, but I don't quite get what it's connected with? memory issues again?

I attach today's crash of 20/05 - this one occured with OCZ modules and BIOS set to default, after that I decided to give the Corsairs another chance.

CPU temps never exceeds 45C - this while playing SCII or doing OCCT, the CPU isn't overclocked and the Corsair RAM is set to its default - except for the command rate which I had to manually set at 2T, otherwise the PC won't boot.

thanks!

 

[R4ndom]

Only lasted a couple of hours, I came back to my room to see the PC reset itself, but not with a typical BSOD blue screen, the screen simply went black and shortly after I saw the BIOS POST message... and this happened 3 times today in a couple of minutes intervals.

The only difference I see before the last BIOS update and now is that other programmes don't crash - so far... whereas windows is as unstable as it was before.

WhoCrashed reports [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR, would you please have a look at the two latest dumps I attach? Actually a funny thing (if it can be funny not being able to use your pc for 6months, but that's a different story). The last reboot took place out of the blue, with PC perfectly on idle, just skype and firefox running in background, actually today I never got the typical BSOD with a message "dumping memory blablabla and after reboot there was no the usual "windows has recovered after an error. blablabla". so although there were 3 BSODs today, only 2 were registered...

thanks!
[/FONT]

 

[Dave76]

Did you change the BIOS voltage as suggested previously?

What is the RAM frequency?

If not 1333MHz then manually set it to that.
Manually set the RAM to manufacturers specs, 9-9-9-24 and Command Rate of 2T.
DRAM voltage to 1.65v manually.
Set the 'VDDNB Over Voltage' to 1.250v.

If that's not stable, we'll bump the CPU voltage a little.
Can you upload the CPUZ CPU tab under full load?
Go to 'CPU Over Voltage' and tell us the options there.
Start with a +0.10v.

Did you increase the CPU voltage as mentioned in post #59?
Give the CPU voltage a bump, increase the CPU Over Voltage an additional 0.10v.
Is the 'VDDNB Over Voltage' still set to 1.350v?

Both of the last crashes are the same.

STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes: Hardware, Incompatibility, May be driver corruption

This is blaming the CPU, the possibilities are: bad CPU, CPU/socket bent pins, loose cable connections, unstable power supply, CPU idle power too low.
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

This can be heat related (we've already looked into that), defective hardware: usually memory, processor or PSU.
It is possible that it is driver related but usually not the case, you have updated all the motherboard drivers from the mobo website, correct?
Remove ALL power and reseat all cards, memory, GPU, Sound, and any others you have installed.
Be sure to check all cables on both ends - actually remove and reconnect - check for anything that doesn't fit tight or seems a little loose.
Also check your CPU cooler fan connections.


Check this post for anything we haven't tried yet: Stop 0x124 - what it means and what to try

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004b65038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031a15b0 fffff800`030d8ca9 : fffffa80`04b65010 fffffa80`03a51040 00000000`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a1ad0 fffff800`02fb9587 : fffffa80`04b65010 fffff800`030332d8 fffffa80`03a51040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a1b00 fffff800`02f20985 : fffff800`03094ae0 00000000`00000001 fffffa80`04b57170 fffffa80`03a51040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a1b40 fffff800`02e9f851 : fffff880`00c5ae00 fffff800`02f20960 fffffa80`03a51000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a1b70 fffff800`0312ce6a : 00000000`00000000 fffffa80`03a51040 00000000`00000080 fffffa80`03943840 : nt!ExpWorkerThread+0x111
fffff880`031a1c00 fffff800`02e86f06 : fffff880`02fd5180 fffffa80`03a51040 fffff880`02fdffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1c40 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a0fc0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

Can you translate these?
tell me what apps are crashing?

2012-04-21 11:33	Application Hang	Program firefox.exe w wersji 11.0.0.4454 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: c88
 Godzina rozpoczęcia: 01cd1fa6ff9f4216
 Godzina zakończenia: 18
 Ścieżka aplikacji: D:\Mozilla Firefox\firefox.exe
 Identyfikator raportu: ce425251-8ba5-11e1-a87b-14dae9c5e52a


2012-04-06 17:31	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: a10
 Godzina rozpoczęcia: 01cd141aa29f32ec
 Godzina zakończenia: 16
 Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
 Identyfikator raportu: 


2012-03-13 21:41	Application Hang	Program SopCast.exe w wersji 3.4.7.45585 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: 794
 Godzina rozpoczęcia: 01cd01611e99e1a5
 Godzina zakończenia: 7
 Ścieżka aplikacji: D:\SopCast\SopCast.exe
 Identyfikator raportu: 81ab542a-6d54-11e1-ba62-14dae9c5e52a


2012-02-21 23:29	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: d8
 Godzina rozpoczęcia: 01ccf0f0834850c2
 Godzina zakończenia: 46
 Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
 Identyfikator raportu: 


2012-02-17 20:06	Application Hang	Program PRIME95.EXE w wersji 24.14.1.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: df0
 Godzina rozpoczęcia: 01ccedae9183c0d4
 Godzina zakończenia: 18902
 Ścieżka aplikacji: D:\Prime95\PRIME95.EXE
 Identyfikator raportu: b891b03a-59a2-11e1-9fb2-14dae9c5e52a


2012-02-16 18:16	Application Hang	Program Setup.exe w wersji 10.0.30319.1 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: d10
 Godzina rozpoczęcia: 01ccecd661a87b3d
 Godzina zakończenia: 3
 Ścieżka aplikacji: E:\f756663a13d0803aebfe4c0a820e1b34\Setup.exe
 Identyfikator raportu: 


2012-02-05 21:56	Application Hang	Program i_view32.exe w wersji 4.3.2.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: e90
 Godzina rozpoczęcia: 01cce450eefff8a5
 Godzina zakończenia: 3
 Ścieżka aplikacji: D:\IrfanView\i_view32.exe
 Identyfikator raportu: 4e4560cf-5044-11e1-b192-14dae9c5e52a


2012-02-05 21:55	Application Hang	Program i_view32.exe w wersji 4.3.2.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: eac
 Godzina rozpoczęcia: 01cce450c934bc3a
 Godzina zakończenia: 4
 Ścieżka aplikacji: D:\IrfanView\i_view32.exe
 Identyfikator raportu: 22491eff-5044-11e1-b192-14dae9c5e52a


2012-02-04 00:11	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: e24
 Godzina rozpoczęcia: 01cce2d169e15786
 Godzina zakończenia: 28
 Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
 Identyfikator raportu: 


2012-02-04 00:10	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: 950
 Godzina rozpoczęcia: 01cce2d14a701630
 Godzina zakończenia: 27
 Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
 Identyfikator raportu: 


2012-02-02 18:45	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: 458
 Godzina rozpoczęcia: 01cce1dab113816d
 Godzina zakończenia: 25
 Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
 Identyfikator raportu: 


2012-01-31 20:10	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: f1c
 Godzina rozpoczęcia: 01cce0531b10e575
 Godzina zakończenia: 41
 Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
 Identyfikator raportu: 


2012-01-17 20:10	Application Hang	Program explorer.exe w wersji 6.1.7601.17567 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
 Identyfikator procesu: dcc
 Godzina rozpoczęcia: 01ccd5533cb9462d
 Godzina zakończenia: 41565
 Ścieżka aplikacji: C:\Windows\explorer.exe
 Identyfikator raportu: