BSOD With 0x00000124

[carwiz]

Windows 7x86fre.win7_rtm.090713-1255.

You're still getting invalid memory addresses, page faults and cache faults. Too many hot fixes and updates were made to the RTM to expect it to run now with current drivers. Not to mention SP1. You can see by the date of July 13, 2009 that you're a bit out of date. Your RTM version is 32-bit so I don't know why you're claiming x64.

Update Windows and use the correct 32-bit drivers. I don't know what else to tell you. Chasing these errors are just a waste of time.

 

[firsttimebuild]

Windows 7x86fre.win7_rtm.090713-1255.

You're still getting invalid memory addresses, page faults and cache faults. Too many hot fixes and updates were made to the RTM to expect it to run now with current drivers. Not to mention SP1. You can see by the date of July 13, 2009 that you're a bit out of date. Your RTM version is 32-bit so I don't know why you're claiming x64.

Update Windows and use the correct 32-bit drivers. I don't know what else to tell you. Chasing these errors are just a waste of time.

I was claiming x64 because I did have x64 I then deleted my OS and did a clean install with a 32-bit OS.

 

[Dave76]

It is recommended to use driver sweeper when installing graphics drivers, it has resolved issue before.

Your Zip files are not complete, follow the Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes

Re-set your BIOS to defaults, this is not a good time to be changing any settings, it just complicates the trouble shooting.

Can you post your specs, this will help diagnose your system hardware.
Use these links to find your system specs.
Speccy Free System information Utility
System Info - See Your System Specs
View attachment 191434

Run memtest86+ to test your RAM, windows RAM test is not that good.
RAM - Test with Memtest86+
Run it with all RAM cards installed and for a minimum of 7 full passes, best to run overnight.

D/L 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


Your last crash is STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
This indicates that invalid system memory has been referenced.

Cause:
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffe9eaf2, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8b8d128c, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 81dab718
Unable to read MiSystemVaType memory at 81d8b160
 ffe9eaf2 

FAULTING_IP: 
Ntfs!NtfsAcquireScbForLazyWrite+13
8b8d128c 83780801        cmp     dword ptr [eax+8],1

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  8c90bbf8 -- (.trap 0xffffffff8c90bbf8)
ErrCode = 00000000
eax=ffe9eaea ebx=00000000 ecx=81dac100 edx=00000000 esi=9ca02d78 edi=870a4450
eip=8b8d128c esp=8c90bc6c ebp=8c90bc78 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
Ntfs!NtfsAcquireScbForLazyWrite+0x13:
8b8d128c 83780801        cmp     dword ptr [eax+8],1  ds:0023:ffe9eaf2=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 81c895f8 to 81cc88e3

STACK_TEXT:  
8c90bbe0 81c895f8 00000000 ffe9eaf2 00000000 nt!MmAccessFault+0x106
8c90bbe0 8b8d128c 00000000 ffe9eaf2 00000000 nt!KiTrap0E+0xdc
8c90bc78 81cdbe5d 9ca02d78 00000001 870a4450 Ntfs!NtfsAcquireScbForLazyWrite+0x13
8c90bca8 81ce3ed6 8c90bcc4 8101399b 847382e0 nt!CcWriteBehind+0x6cf
8c90bd00 81cb0f2b 847382e0 00000000 8472f798 nt!CcWorkerThread+0x164
8c90bd50 81e5166d 00000000 8101390b 00000000 nt!ExpWorkerThread+0x10d
8c90bd90 81d030d9 81cb0e1e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsAcquireScbForLazyWrite+13
8b8d128c 83780801        cmp     dword ptr [eax+8],1

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  Ntfs!NtfsAcquireScbForLazyWrite+13

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf45

FAILURE_BUCKET_ID:  0x50_Ntfs!NtfsAcquireScbForLazyWrite+13

BUCKET_ID:  0x50_Ntfs!NtfsAcquireScbForLazyWrite+13

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

The other crashes:

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffc07, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8c4d4629, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)
MODULE_NAME: Ntfs
.............................................................................................................................
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: 00000000, Machine Check Exception
Arg2: 8583e01c, Address of the WHEA_ERROR_RECORD structure.
Arg3: b41e2000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000135, Low order 32-bits of the MCi_STATUS value.
MODULE_NAME: hardware
............................................................................................................................
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: 00000000, Machine Check Exception
Arg2: 8594d01c, Address of the WHEA_ERROR_RECORD structure.
Arg3: b6004000, High order 32-bits of the MCi_STATUS value.
Arg4: 67000135, Low order 32-bits of the MCi_STATUS value.
MODULE_NAME: hardware
.................................................................................................................................
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 850bd008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8d84b4da, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
MODULE_NAME: atikmpag
.................................................................................................................................
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ff000004, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 81e60aa6, If non-zero, the instruction address which referenced the bad memory address.
Arg4: 00000002, (reserved)
MODULE_NAME: nt
....................................................................................................................................
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: 00000000, Machine Check Exception
Arg2: 8603201c, Address of the WHEA_ERROR_RECORD structure.
Arg3: b4002000, High order 32-bits of the MCi_STATUS value.
Arg4: c5000135, Low order 32-bits of the MCi_STATUS value.
MODULE_NAME: hardware

This is a hardware issue, please fill in your system specs so we can proceed.




Driver list:

1: kd> lmntsm
start    end        module name
99400000 9940a000   [COLOR="red"]ALSysIO  ALSysIO.sys  Sun Jul 10 08:27:36 2011[/COLOR] (4E18F1F8)
8b7a7000 8b7b0000   [COLOR="Red"]amdxata  amdxata.sys  Wed May 20 01:57:35 2009[/COLOR] (4A12F30F)
8199d000 819d4000   [COLOR="red"]dump_nvstor32 dump_nvstor32.sys Wed Jul 01 08:17:14 2009[/COLOR] (4A4AAB0A)
8e1f5000 8e1f9fa0   [COLOR="red"]jswpslwf jswpslwf.sys Thu May 15 18:28:43 2008[/COLOR] (482C105B)
90229000 9026d700   [COLOR="red"]nvmf6232 nvmf6232.sys Fri May 01 03:45:40 2009[/COLOR] (49F9FFE4)
8b704000 8b729000   [COLOR="red"]nvstor   nvstor.sys   Wed May 20 14:44:09 2009[/COLOR] (4A13A6B9)
8b770000 8b7a7000  [COLOR="red"] nvstor32 nvstor32.sys Wed Jul 01 08:17:14 2009 (4A4AAB0A)[/COLOR]
8bd89000 8bd92000   [COLOR="red"]scmndisp scmndisp.sys Wed Jan 17 17:25:59 2007[/COLOR] (45ADEBA7)
994b9000 994c3000   [COLOR="red"]secdrv   secdrv.SYS   Wed Sep 13 21:18:32 2006[/COLOR] (45080528)
8bdda000 8bde2000   [COLOR="red"]spldr    spldr.sys    Tue May 12 00:13:47 2009 (4A084EBB)[/COLOR]
994f1000 9955b000   [COLOR="red"]spsys    spsys.sys    Tue May 12 00:37:10 2009 (4A085436)[/COLOR]

Your drivers are mostly old versions.
Go to your motherboard website and update all your drivers.
Do not use the CD that came with your motherboard, they are old.

 

[GianniDPC]

Windows 7x86fre.win7_rtm.090713-1255.

You're still getting invalid memory addresses, page faults and cache faults. Too many hot fixes and updates were made to the RTM to expect it to run now with current drivers. Not to mention SP1. You can see by the date of July 13, 2009 that you're a bit out of date. Your RTM version is 32-bit so I don't know why you're claiming x64.

Update Windows and use the correct 32-bit drivers. I don't know what else to tell you. Chasing these errors are just a waste of time.

I was claiming x64 because I did have x64 I then deleted my OS and did a clean install with a 32-bit OS.

Why did you delete the x64 windows :shock:

 

[firsttimebuild]

It is recommended to use driver sweeper when installing graphics drivers, it has resolved issue before.

Your Zip files are not complete, follow the Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes

Re-set your BIOS to defaults, this is not a good time to be changing any settings, it just complicates the trouble shooting.

Can you post your specs, this will help diagnose your system hardware.
Use these links to find your system specs.
Speccy Free System information Utility
System Info - See Your System Specs
View attachment 191434

Run memtest86+ to test your RAM, windows RAM test is not that good.
RAM - Test with Memtest86+
Run it with all RAM cards installed and for a minimum of 7 full passes, best to run overnight.

D/L 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


Your last crash is STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
This indicates that invalid system memory has been referenced.

Cause:
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffe9eaf2, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8b8d128c, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 81dab718
Unable to read MiSystemVaType memory at 81d8b160
 ffe9eaf2 

FAULTING_IP: 
Ntfs!NtfsAcquireScbForLazyWrite+13
8b8d128c 83780801        cmp     dword ptr [eax+8],1

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  8c90bbf8 -- (.trap 0xffffffff8c90bbf8)
ErrCode = 00000000
eax=ffe9eaea ebx=00000000 ecx=81dac100 edx=00000000 esi=9ca02d78 edi=870a4450
eip=8b8d128c esp=8c90bc6c ebp=8c90bc78 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
Ntfs!NtfsAcquireScbForLazyWrite+0x13:
8b8d128c 83780801        cmp     dword ptr [eax+8],1  ds:0023:ffe9eaf2=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 81c895f8 to 81cc88e3

STACK_TEXT:  
8c90bbe0 81c895f8 00000000 ffe9eaf2 00000000 nt!MmAccessFault+0x106
8c90bbe0 8b8d128c 00000000 ffe9eaf2 00000000 nt!KiTrap0E+0xdc
8c90bc78 81cdbe5d 9ca02d78 00000001 870a4450 Ntfs!NtfsAcquireScbForLazyWrite+0x13
8c90bca8 81ce3ed6 8c90bcc4 8101399b 847382e0 nt!CcWriteBehind+0x6cf
8c90bd00 81cb0f2b 847382e0 00000000 8472f798 nt!CcWorkerThread+0x164
8c90bd50 81e5166d 00000000 8101390b 00000000 nt!ExpWorkerThread+0x10d
8c90bd90 81d030d9 81cb0e1e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsAcquireScbForLazyWrite+13
8b8d128c 83780801        cmp     dword ptr [eax+8],1

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  Ntfs!NtfsAcquireScbForLazyWrite+13

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf45

FAILURE_BUCKET_ID:  0x50_Ntfs!NtfsAcquireScbForLazyWrite+13

BUCKET_ID:  0x50_Ntfs!NtfsAcquireScbForLazyWrite+13

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

The other crashes:

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffc07, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8c4d4629, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)
MODULE_NAME: Ntfs
.............................................................................................................................
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: 00000000, Machine Check Exception
Arg2: 8583e01c, Address of the WHEA_ERROR_RECORD structure.
Arg3: b41e2000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000135, Low order 32-bits of the MCi_STATUS value.
MODULE_NAME: hardware
............................................................................................................................
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: 00000000, Machine Check Exception
Arg2: 8594d01c, Address of the WHEA_ERROR_RECORD structure.
Arg3: b6004000, High order 32-bits of the MCi_STATUS value.
Arg4: 67000135, Low order 32-bits of the MCi_STATUS value.
MODULE_NAME: hardware
.................................................................................................................................
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 850bd008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8d84b4da, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
MODULE_NAME: atikmpag
.................................................................................................................................
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ff000004, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 81e60aa6, If non-zero, the instruction address which referenced the bad memory address.
Arg4: 00000002, (reserved)
MODULE_NAME: nt
....................................................................................................................................
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: 00000000, Machine Check Exception
Arg2: 8603201c, Address of the WHEA_ERROR_RECORD structure.
Arg3: b4002000, High order 32-bits of the MCi_STATUS value.
Arg4: c5000135, Low order 32-bits of the MCi_STATUS value.
MODULE_NAME: hardware

This is a hardware issue, please fill in your system specs so we can proceed.




Driver list:

1: kd> lmntsm
start    end        module name
99400000 9940a000   [COLOR="red"]ALSysIO  ALSysIO.sys  Sun Jul 10 08:27:36 2011[/COLOR] (4E18F1F8)
8b7a7000 8b7b0000   [COLOR="Red"]amdxata  amdxata.sys  Wed May 20 01:57:35 2009[/COLOR] (4A12F30F)
8199d000 819d4000   [COLOR="red"]dump_nvstor32 dump_nvstor32.sys Wed Jul 01 08:17:14 2009[/COLOR] (4A4AAB0A)
8e1f5000 8e1f9fa0   [COLOR="red"]jswpslwf jswpslwf.sys Thu May 15 18:28:43 2008[/COLOR] (482C105B)
90229000 9026d700   [COLOR="red"]nvmf6232 nvmf6232.sys Fri May 01 03:45:40 2009[/COLOR] (49F9FFE4)
8b704000 8b729000   [COLOR="red"]nvstor   nvstor.sys   Wed May 20 14:44:09 2009[/COLOR] (4A13A6B9)
8b770000 8b7a7000  [COLOR="red"] nvstor32 nvstor32.sys Wed Jul 01 08:17:14 2009 (4A4AAB0A)[/COLOR]
8bd89000 8bd92000   [COLOR="red"]scmndisp scmndisp.sys Wed Jan 17 17:25:59 2007[/COLOR] (45ADEBA7)
994b9000 994c3000   [COLOR="red"]secdrv   secdrv.SYS   Wed Sep 13 21:18:32 2006[/COLOR] (45080528)
8bdda000 8bde2000   [COLOR="red"]spldr    spldr.sys    Tue May 12 00:13:47 2009 (4A084EBB)[/COLOR]
994f1000 9955b000   [COLOR="red"]spsys    spsys.sys    Tue May 12 00:37:10 2009 (4A085436)[/COLOR]

Your drivers are mostly old versions.
Go to your motherboard website and update all your drivers.
Do not use the CD that came with your motherboard, they are old.

I know most of my drivers are of later version at the moment, up intill a week or so ago I had all the latest drivers for my mobo, gpu, cpu ect but I read a post on a different forum saying that this issue could be my gpu drivers I heard people got this problem from the latest ATI drivers so I uninstalled my drivers and tried older version as I posted earlier in this topic, I will uninstall all drivers once again this time using driver sweeper in safe mode to delete the remnants of the files and reinstall all the latest ones again and post my results.

If I still get blue screen/stop errors I will post them again with the details you suggest above.

I know it's common procedure to remove any over clock to see if there causing this error but for some reason when I go to bios to try and reset my cpu to stock speeds it reverts my cpu core clock to 803Mhz instead of 3.2Ghz. If any one has any ideas why this has happened could you let me know I'm new to all this pc malarky and I'm still learning!

 

[firsttimebuild]

Windows 7x86fre.win7_rtm.090713-1255.

You're still getting invalid memory addresses, page faults and cache faults. Too many hot fixes and updates were made to the RTM to expect it to run now with current drivers. Not to mention SP1. You can see by the date of July 13, 2009 that you're a bit out of date. Your RTM version is 32-bit so I don't know why you're claiming x64.

Update Windows and use the correct 32-bit drivers. I don't know what else to tell you. Chasing these errors are just a waste of time.

I was claiming x64 because I did have x64 I then deleted my OS and did a clean install with a 32-bit OS.

Why did you delete the x64 windows :shock:

The reason I deleted my x64 OS was because I had no idea what was causing this problem I did that before I posted this topic. As my name suggest this is indeed my "First Time Build" I'm a bit of a pc noob and I thought a clean install would fix this error!

Unfortunately for me it did not! This error is really annoying me to be honest the amount of time I've spent uninstalling and reinstalling of drivers and software is ridiculous and the amount of crashes in between is even more ridiculous!

I really wanted to fix this problem ASAP because I just had a butt load of gaming accessories off my girlfriend for christmas and I have'nt had the opportunity to use any of them yet!

 

[Golden]

Hi,

You need to reset the BIOS using "Load with Failsafe Defaults" or something very similar? Do you see that setting?

Regards,
Golden

 

[Dave76]

I know it's common procedure to remove any over clock to see if there causing this error but for some reason when I go to bios to try and reset my cpu to stock speeds it reverts my cpu core clock to 803Mhz instead of 3.2Ghz. If any one has any ideas why this has happened could you let me know I'm new to all this pc malarky and I'm still learning!

This is one of the reasons we need more information, with your hardware details we can check what drivers may need updated.
With CPUZ mainboard screen we can see your BIOS version.
My guess, due to limited info, is you might need driver updates and look at the BIOS version you have now.
If you haven't updated it yet, it's probably several version old.

With some of the logs in the BSOD posting instructions we can find system errors and maybe get a better idea on how to help you.

Start with posting your 'System Specs'.
Then the complete BSOD Dump & System File Collection info, this will help us to help you, and we won't have to guess.

The drivers I posted in RED are out of date, these out of date drivers are known to cause errors and crashes.

 

[firsttimebuild]

Ok, This is lot of information to take in at once.
First of all I'd like to say thank you dave76, I know how hard it is to try and help people who have little or no knowledge with computers, it's greatly appreciated.

You've asked for me to post pictures of my system spec and CPU-Z
So here they are.

Tonight I'll run memtest and post my results here in the morning.

UPDATE: Ran memtest over night it got to 1300% and had 0 errors.

 

[Dave76]

Thank you for posting the information.

It's difficult to analyze this type of crash with little to go on.

Can you enter your system specs in the drop box 'My System Specs' in the lower left corner of any of your posts, this will help us find you system information without searching through the thread.
Most members here are helping in several threads at the same time, easy access to your specs will help everyone.

How many passes did you do with memtest86+?

Can you re-set your BIOS to defaults, this is not a good time to be changing any settings, it just complicates the trouble shooting.

 

[firsttimebuild]

Ok I've added my system spec.
As I've said above when I go into the bios to reset my hardware to factory settings.
I go to default settings, but when I boot up into windows it says on CPU-Z and Core temp that my cpu is only running at 803Mhz When my stock clock speed should be 3.2Ghz I don't know why this is happening.

I did the memtest in total 4 times 3 times to 100% then over night to 1300%.
0 errors found.

 

[Devilz]

Here is the list of CPU's supported by your motherboard.

ASRock > Products > N68C-S UCC > CPU Support List

By looking at cpuz screenshot you have posted, its look your cpu is not supported with this motherboard cause you are running at 3GHz (underclock) whereas by looking at the cpu support list, maximum speed this motherboard can support is 2.8 GHz

 

[Dave76]

Is 'Cool and Quiet' enabled?

This is a CPU function that lets your CPU run at lower frequency and voltage when you system is at idle or low load, it will ramp up when your system is under a high load.

Devilz has a good point.
From your motherboard site:

Support up to 95W Socket AM3 processors

From the AMD site:

HDT90ZFBK6DGR AMD Phenom™ II X6 Black 1090T 3200 125 W

Check for BIOS update related to CPU compatibility.
You may need to get a different motherboard.

 

[firsttimebuild]

But I don't understand? On the box it says supports phenom II and six core ready.
It worked perfectly for 5 months before this error started occurring. :S

 

[Devilz]

Its definitely hardware issue, you have mentioned in your previous posts you have changed your graphic card and ram so we are only left with cpu

 

[firsttimebuild]

So do you think there something wrong with the cpu? Or just that its not compatible with the motherboard? I was about to upgrade to 16GB DDR3 if you think it's the motherboard I'll invest into that first.

 

[Devilz]

Its look like I've to deliver bad news mate. Yes definitely, its compatibility issue. Your CPU is designed to run at 3.2GHz (stock speed) and your motherboard can support CPU's up to 2.8GHz (maximum).

ASRock > Products > N68C-S UCC > CPU Support List

If you look here, your MB can support 3 phenom II x6 CPU's, 2.6GHz, 2.7GHz & 2.8GHz respectively and these all run @ 95W. And if you look here

AMD Phenom

The CPU you got is 3.2GHz and needs 125W to operate.

Hope this will help

 

[Dave76]

Your motherboard supports up to 95w CPU. The Phenom II X6 1055T, 1075T, 1090T and 1100T are 125w.

Your motherboard supports the Phenom II X6 1065T and 1045T only.

If you want to keep the Phenom II X6 1090T you should get a new motherboard. Be sure to check the CPU compatibility list before buying.

 

[firsttimebuild]

Order a new motherboard soon! Hopefully this will completely fix this problem!
One thing now though I can't decide between these 2 motherboards I was wondering if any 1 could help me decide between them.

Gigabyte 990FXA-UD3 SKT-AM3+

OR

Asrock 890FX Deluxe5 AM3+

 

[Dave76]

Both are good choices.

Go to the motherboard support forum for each and check if they are having any serious issues.
There will always be issues, some caused by the motherboard and some not.

If there is a reoccurring issue, you might want to research it further.