Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD With 0x00000124

03 Jan 2012   #21
carwiz

Windows 7 Pro-x64
 
 

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.


My System SpecsSystem Spec
.
04 Jan 2012   #22
firsttimebuild

windows 7 32-64
 
 

Quote   Quote: Originally Posted by carwiz View Post
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.
My System SpecsSystem Spec
04 Jan 2012   #23
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

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

04 Jan 2012   #24
GianniDPC

Windows 7 Home Premium x64
 
 

Quote   Quote: Originally Posted by firsttimebuild View Post
Quote   Quote: Originally Posted by carwiz View Post
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
My System SpecsSystem Spec
04 Jan 2012   #25
firsttimebuild

windows 7 32-64
 
 

Quote   Quote: Originally Posted by Dave76 View Post
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
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.
Code:
*******************************************************************************
*                                                                             *
*                        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:
Code:
*******************************************************************************
*                                                                             *
*                        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:
Code:
1: kd> lmntsm
start    end        module name
99400000 9940a000   ALSysIO  ALSysIO.sys  Sun Jul 10 08:27:36 2011 (4E18F1F8)
8b7a7000 8b7b0000   amdxata  amdxata.sys  Wed May 20 01:57:35 2009 (4A12F30F)
8199d000 819d4000   dump_nvstor32 dump_nvstor32.sys Wed Jul 01 08:17:14 2009 (4A4AAB0A)
8e1f5000 8e1f9fa0   jswpslwf jswpslwf.sys Thu May 15 18:28:43 2008 (482C105B)
90229000 9026d700   nvmf6232 nvmf6232.sys Fri May 01 03:45:40 2009 (49F9FFE4)
8b704000 8b729000   nvstor   nvstor.sys   Wed May 20 14:44:09 2009 (4A13A6B9)
8b770000 8b7a7000   nvstor32 nvstor32.sys Wed Jul 01 08:17:14 2009 (4A4AAB0A)
8bd89000 8bd92000   scmndisp scmndisp.sys Wed Jan 17 17:25:59 2007 (45ADEBA7)
994b9000 994c3000   secdrv   secdrv.SYS   Wed Sep 13 21:18:32 2006 (45080528)
8bdda000 8bde2000   spldr    spldr.sys    Tue May 12 00:13:47 2009 (4A084EBB)
994f1000 9955b000   spsys    spsys.sys    Tue May 12 00:37:10 2009 (4A085436)
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!
My System SpecsSystem Spec
04 Jan 2012   #26
firsttimebuild

windows 7 32-64
 
 

Quote   Quote: Originally Posted by GianniDPC View Post
Quote   Quote: Originally Posted by firsttimebuild View Post
Quote   Quote: Originally Posted by carwiz View Post
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

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!
My System SpecsSystem Spec
04 Jan 2012   #27
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Hi,

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

Regards,
Golden
My System SpecsSystem Spec
04 Jan 2012   #28
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Quote   Quote: Originally Posted by firsttimebuild View Post
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.
My System SpecsSystem Spec
04 Jan 2012   #29
firsttimebuild

windows 7 32-64
 
 

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.
My System SpecsSystem Spec
05 Jan 2012   #30
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

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.
My System SpecsSystem Spec
Reply

 BSOD With 0x00000124




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD 0x00000124 Hall.dll (Bsod is distorted/static sound)
I have been getting a ton of bsods I have re installed video drivers, updated and reinstalled windows 8. Did countless hardware test(Video ram, check memory, Cpu test) all passed temperatures stay around 25-35 c. Recently uninstalled all video drivers and re installed. The bsods sometimes go...
BSOD Help and Support
BSOD 0x00000124
my old os is vista and yesterday i format it and install win7 ultimate sp1 32 bit using bootable flash drive. i'm having the same problem . when i run my windows in normal modes blue screen problem occur repeatedly. now im using my laptop in safe mode w/ networking Problem signature: Problem...
BSOD Help and Support
Keep getting BSOD - 0x00000124
My PC started freezing, so I decided to reboot it to factory settings. But now I am getting a BSOD. I have tried different Nvidia drivers (including latest) but that doesn't make a difference. I have also update sound and direct X drivers. I have run lots of malware and virus scans, done a memory...
BSOD Help and Support
Bsod 0x00000124
Hey, the problem started a month ago, the screen freezes, just like that. Sometimes when you work in office, other times when you are on internet ...:mad: After the freeze I restarted the pc but I could'nt find anything in the logs An hour ago, it gives a BSOD with 0x0000124 ??? hardware issue?...
BSOD Help and Support
BSOD 0x00000124
Hello my fellow computer geeks. I have encountered my first BSOD on my first computer built. I apologize for sounding like an amateur as it is my first time dealing with this problem. Problem: So, one day I start my computer and it blue screens with the STOP error 0x00000124. I assume it's...
BSOD Help and Support
BSOD 0x00000124
Hello all, A friend of mine is having some issues with his computer. I've asked for help on other forums, but they can't seem to help.. I'll try to make it as short as possible, here goes! My friend bought a computer 2 years ago, with the following specs: GTX280 Intel Core2Duo E8500 MSI...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 06:50.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App