Bsod 124

ok looks like it's the memory, it never passed any of the tests


ok replaced the memory with integral dd3 4gb, but still got blue screen of death so doing memtest86 on it now.

Hello Finlay and welcome to Sevenforums.

BSOD Analyse

I believe I've found your issue. You have a wireless USB adapter yes? They don't usually run very good with Windows. I'd suggest you to update the driver if you desire to continue using it.

Code:

Name    [00000007] NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter

Code:

SCMNdisP     General NDIS Protocol  General NDIS Protocol  Kernel        Boot       Running    OK         TRUE        FALSE        4,096      12,288     0      17/01/2007 07:48:03    C:\Windows\system32\DRIVERS\scmndisp.sys         4,096

http://downloadcenter.netgear.com/en...ration?product

Do this, and we'll continue if the problem continues.

Code:

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: fffffa800531b8f8, 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.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
¨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: fffffa80049718f8, 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.

Best Regards,
Frederik.

Aeneas Finlay said:

thanks I will give that a try.

Take all the time you'll need.

Best Regards,
Frederik.

Hello again,

Alrighty-

• Any sort of overclocking should be stopped. Overclocking is obviously producing a lot of heat. Also make sure that you're not having a motherboard feature that overclocks your computer automatically.
• Make sure that your computer is running cool. Install Speedfan for instance, and make sure that fans are running at the right speed. Also track down weird or noisy sounds.
• Windows 7 may have bugs in the OS if you ain't updating. Make sure that Windows Update is running on automatic updates, and not manual, or the 'never' feature.
• Let's stress test some of the hardware. The most common causer within hardware would be the memory -

There could be a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors. To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

• The next would be your processor -

Prime is a stress testing tool for CPU's.
Details below.

Hardware - Stress Test With Prime95

• If you have your system under warranty, consider replacing it.

Best Regards,
Frederik.

Andreas,
Be sure to:
Blue Screen of Death (BSOD) Posting Instructions

Question for you: If you boot into SAFE MODE, is the problem gone?

Aeneas Finlay said:

yeah it has not crashed when in safe mode, but since sometimes it can take a while to crash might just of been luck
done the memory test and replaced memory and did new test on new memory and it was fine
will try the processor test tomorrow

Great, we might also want to run Driver Verifier soon as it didn't crash in safe mode, but I want to do one troubleshoot at a time. By that we all won't get confused. :)

Best Regards,
Frederik.