Random Bluescreens

Drakinus · 30 Apr 2011

I've bougt a new pc about 1 month back and i've had several BSOD's. I've got Windows 7 home premium 64bits as originally installed OS in my system.

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)
Language: Dutch (Regional Setting: Dutch)
System Manufacturer: MEDIONPC
System Model: MS-7708
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz (8 CPUs), ~2.9GHz
Memory: 8192MB RAM
Available OS Memory: 8184MB RAM

I hope you can help me,
Thank you in advance,
Drakinus

Dave76 · 30 Apr 2011

Hi Drakinus, your minidump indicates a Stop 0x124 hardware fault. The minidumps don't give much information for this Stop error.

Start with filling in your system specs, in order to troubleshoot we need to know more about your system.
Download this free program for more information on your system: SIW - System Information for Windows

The perfromreport indicates a hard drive fault.
Download your hard drive testing program from the manufactures site.

If you have either of these hard drives you can get them from these links.
D/L and run Western Digital Lifeguard
D/L and run Seagate SeaTools

Run both short and long (full) tests.

Code:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x86 compatible
Mini Kernel Dump does not contain unloaded driver list
BugCheck 124, {0, 8695e024, 0, 0}
Probably caused by : hardware
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred.
BUGCHECK_STR:  0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

If the hard drives come up clean then run:

CPU - Stress Test with Prime95 - Torture test
First open Real Temp to monitor CPU temperatures, don't go over 77 °C.
Open Prime95 and stop the test if it is running, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 8, then click OK to start the test.

With 8GB RAM you may need to adjust the timings and voltages.
D/L and run RAM - Test with Memtest86+ , leave all the RAM cards in for the first test.

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?

Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

If your running AVG Anti-Virus, You should un-install it for testing, it is known to cause BSoDs on some Win7 systems.
I recommend to D/L MSE, update it through Windows Update and run a Full scan, for testing purposes.

Drakinus · 01 May 2011

So I added my computer specs to my profile.
First of all I tested my harddrive with seagate, and with all tests, it passed.
After that i checked my temp with Prime95, it was around 77°C but it peeks at 80°C sometimes, but it falls back to 77 again after that. (I turned it on for about 15 Minutes, is that enough?) (I don't really know what to look at on prime95 itself tho).
Minimum and Maximum temps are 32°C and 80°C
Here's the screenshot from CPU-Z
Also I uninstaled AVG (Which took me quite a long time, because I couldn't just uninstall it, needed to download a program to uninstall it.) and installed MSE.

I haven't quite got around to MEMTEST86+ but I thought I submitted the info I already gotten. Since I don't know if i have time to test it today. Maybe with the info I gave you might already have some tips or advices. Thanks for the fast response by the way!

Drakinus · 01 May 2011

I did get around doing the Memtest, and it passed the test, no errors whatsoever.
So i'm hoping it was just my AVG. I'll post again if i'm still having BSOD's.

Thank you for your help so far. :)
Greetings, Drakinus

Dave76 · 01 May 2011

Good information with the snips.

Prime95 maxes out the CPU, if it shows an error or stops on it's own, that is a fault.
Intel lists your CPU max temp at 77°C, I wouldn't let it go past that, it possible to damage the CPU.
Are you running the stock Intel CPU cooler?
Even with the stock cooler your Prime95 temps should be 70°C at the most.
Check if the cooler is loose, you shouldn't be able to turn it.

How long did you run memtest86+ for?
It does different tests that can stress your RAM, the errors usually come in test #5 & #7, with 8GB RAM it will take a long time to get that far, 7-12 hours.
Best to run it overnight.

With 8GB RAM you will likely need to bump the CPU integrated memory controller.

Let us know if you get any more BSoDs.

Drakinus · 01 May 2011

the stock Intel CPU cooler, how do I check that one?
And to bump the CPU integrated memory controller, how do I do that one?
I let memtest86+ run for about 2hr, and it was at 100%
I'll check if the cooler is loose when i still get the BSOD's, because I don't really wanna open up my pc, because of the warranty.

And I usually check the temps while I play some games, just to check up, and It doesn't really go over 70°C.

Thanks again. :)

yowanvista · 01 May 2011

Drakinus said:

the stock Intel CPU cooler, how do I check that one?
And to bump the CPU integrated memory controller, how do I do that one?
I let memtest86+ run for about 2hr, and it was at 100%
I'll check if the cooler is loose when i still get the BSOD's, because I don't really wanna open up my pc, because of the warranty.

And I usually check the temps while I play some games, just to check up, and It doesn't really go over 70°C.

Thanks again. :)

Just check if the cpu fan is spinning :)

Dave76 · 01 May 2011

You really need to run memtest86+ for a minimum of 7 passes, this will take a long time with 8GB RAM, welcome to the joys of the 'Got lots a RAM' club, best to run overnight as it will take 8-12 hours.

The most stressful tests seems to be #5 & #7, see a lot of errors from these tests.

If you run the full test and get no errors then you won't need a memory controller voltage bump.

As with all electronics, testing with memtest86+ (which is the best RAM testing program available) doesn't mean your RAM is guaranteed to be 100% error free. It is a very good way to find errors, have seen it give no errors a few times and then on the next test give some errors.
These can be fixed by adjusting the RAM settings sometimes, other times the RAM will need to be replaced.

Max gaming temps of 70°C is acceptable, but high for me.
I would re-apply the thermal paste between the CPU and CPU cooler, whether by yourself or through the warranty.
You can get a much better CPU cooler for around $25, well worth the investment as it will keep the CPU much cooler under load.
Mine is 58°C when running Prime95.

Drakinus · 02 May 2011

I just started my pc and after 15 minutes, it crashed again. I didn't do anything on it, so i doubt it has anything to do with the temerature. I opened him up anyway, and the fan is working tho.
For your info, I don't know anything about hardware. (How to control it and change it and such)

I'll let my pc run overnight tonight while doing memtest86+.
Any hints or tips on anything else that may help?
I appreciate your help, I really do :)
This forum is great.

Edit: PS: I uploaded the last dumpfile, might shed some light in the matter.

Dave76 · 02 May 2011

It is possible for a CPU to overheat at an idle, since your gaming temps are ok, it's likely not CPU overheating caused.

Let's see the memtest86+ results, then can check other things from there.

The new dump file reports a stop 0x24 which is a NTFS_File_System error, which indicates a problem with your hard drive.
Did you run the Seagate SeaTools 'Full test'?

This error can be caused by RAM issues, be sure to run memtest86+ first.

Check Device manager for any yellow triangles, this means a driver problem.

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
BugCheck 24, {1904fb, fffff8800a0b9738, fffff8800a0b8f90, fffff8800120ff20}
Probably caused by : Ntfs.sys ( Ntfs!NtfsUninitializeNtfsMcb+98 )
Followup: MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        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: fffff8800a0b9738
Arg3: fffff8800a0b8f90
Arg4: fffff8800120ff20
Debugging Details:
------------------
 
EXCEPTION_RECORD:  fffff8800a0b9738 -- (.exr 0xfffff8800a0b9738)
ExceptionAddress: fffff8800120ff20 (Ntfs!NtfsUninitializeNtfsMcb+0x0000000000000098)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT:  fffff8800a0b8f90 -- (.cxr 0xfffff8800a0b8f90)
rax=fffff8a0152287e0 rbx=fffff8a01523c820 rcx=f8a003fe58a0b7e0
rdx=0000000000000001 rsi=0000000000000000 rdi=fffff8a01523c7e0
rip=fffff8800120ff20 rsp=fffff8800a0b9970 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff88001263980
r11=fffff8800a0b9b52 r12=0000000000000705 r13=0000000000000000
r14=0000000000000000 r15=fffff8a01523c958
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
Ntfs!NtfsUninitializeNtfsMcb+0x98:
fffff880`0120ff20 488901          mov     qword ptr [rcx],rax ds:002b:f8a003fe`58a0b7e0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
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 fffff800033140e8
 ffffffffffffffff 
FOLLOWUP_IP: 
Ntfs!NtfsUninitializeNtfsMcb+98
fffff880`0120ff20 488901          mov     qword ptr [rcx],rax
FAULTING_IP: 
Ntfs!NtfsUninitializeNtfsMcb+98
fffff880`0120ff20 488901          mov     qword ptr [rcx],rax
BUGCHECK_STR:  0x24
LAST_CONTROL_TRANSFER:  from fffff88001292b2f to fffff8800120ff20
STACK_TEXT:  
fffff880`0a0b9970 fffff880`01292b2f : fffff880`0a0b9a28 00000000`00000130 fffff8a0`1523c5c0 fffff880`0120f972 : Ntfs!NtfsUninitializeNtfsMcb+0x98
fffff880`0a0b99a0 fffff880`01297cc1 : fffff800`01010000 00000000`00000000 fffff800`03280600 00000000`00000001 : Ntfs!NtfsDeleteScb+0x8b
fffff880`0a0b99e0 fffff880`0121085c : fffff8a0`1523c5f0 fffff8a0`1523c6f0 fffff800`03280600 fffff880`0a0b9b52 : Ntfs!NtfsRemoveScb+0x61
fffff880`0a0b9a20 fffff880`0129564c : fffff8a0`1523c5c0 fffff800`03280600 fffff880`0a0b9b52 fffffa80`0f101010 : Ntfs!NtfsPrepareFcbForRemoval+0x50
fffff880`0a0b9a50 fffff880`012170e2 : fffffa80`0f101010 fffffa80`0f101010 fffff8a0`1523c5c0 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xdc
fffff880`0a0b9ad0 fffff880`012a5193 : fffffa80`0f101010 fffff800`03280600 fffff8a0`1523c5c0 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`0a0b9b10 fffff880`01294357 : fffffa80`0f101010 fffff8a0`1523c6f0 fffff8a0`1523c5c0 fffffa80`07dd8180 : Ntfs!NtfsCommonClose+0x353
fffff880`0a0b9be0 fffff800`030eda21 : 00000000`00000000 fffff800`03280600 fffffa80`0e992601 00000000`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`0a0b9cb0 fffff800`03380cce : 00000000`0a499824 fffffa80`0e992660 00000000`00000080 fffffa80`06d04740 : nt!ExpWorkerThread+0x111
fffff880`0a0b9d40 fffff800`030d4fe6 : fffff880`009b2180 fffffa80`0e992660 fffffa80`06d17b60 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0a0b9d80 00000000`00000000 : fffff880`0a0ba000 fffff880`0a0b4000 fffff880`0a0b99e0 00000000`00000000 : nt!KxStartSystemThread+0x16
 
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  Ntfs!NtfsUninitializeNtfsMcb+98
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME:  Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b
STACK_COMMAND:  .cxr 0xfffff8800a0b8f90 ; kb
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsUninitializeNtfsMcb+98
BUCKET_ID:  X64_0x24_Ntfs!NtfsUninitializeNtfsMcb+98
Followup: MachineOwner
---------