Please help me with my BSODs

[digiknowzone]

I experience BSODs every time my laptop is plugged in. But no BSODs happen when I'm not plugged in. Please help me on what I need to do.

Here are my laptop's specs:

Asus K42jC-vx169
Core i5 M460 2.53GHz
2Gb Ram
320Gb HDD
1gb VRAM (Nvidia GeForce CUDA 310M)
Windows 7 ultimate 64-bit

Thanks in advance!

 

[Maguscreed]

You are getting a very specific type of crash report here that is almost always related to one of 2 things
1 - a unstable overclock
2 - failing hardware / lack of power

Before going any further I have to ask if you have altered memory timings, or performed any manner of overclocking on this laptop?

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: fffffa80047b9028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000020e0f, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0316ba58 fffff800`0341b903 : 00000000`00000124 00000000`00000000 fffffa80`047b9028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`0316ba60 fffff800`035d8513 : 00000000`00000001 fffffa80`04805a70 00000000`00000000 fffffa80`04805ac0 : hal!HalBugCheckSystem+0x1e3
fffff880`0316baa0 fffff800`0341b5c8 : 00000000`00000728 fffffa80`04805a70 fffff880`0316be30 fffff880`0316be00 : nt!WheaReportHwError+0x263
fffff880`0316bb00 fffff800`0341af1a : fffffa80`04805a70 fffff880`0316be30 fffffa80`04805a70 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0316bc50 fffff800`0341add5 : 00000000`00000004 00000000`00000001 fffff880`0316beb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0316bc90 fffff800`0340ee88 : 00000000`00000000 00000000`0055bb60 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0316bcc0 fffff800`034c27ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0316bcf0 fffff800`034c2613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0316be30 00000000`6ce06ca6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0055bb4c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6ce06ca6


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

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

 

[digiknowzone]

You are getting a very specific type of crash report here that is almost always related to one of 2 things
1 - a unstable overclock
2 - failing hardware / lack of power

Before going any further I have to ask if you have altered memory timings, or performed any manner of overclocking on this laptop?

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: fffffa80047b9028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000020e0f, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0316ba58 fffff800`0341b903 : 00000000`00000124 00000000`00000000 fffffa80`047b9028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`0316ba60 fffff800`035d8513 : 00000000`00000001 fffffa80`04805a70 00000000`00000000 fffffa80`04805ac0 : hal!HalBugCheckSystem+0x1e3
fffff880`0316baa0 fffff800`0341b5c8 : 00000000`00000728 fffffa80`04805a70 fffff880`0316be30 fffff880`0316be00 : nt!WheaReportHwError+0x263
fffff880`0316bb00 fffff800`0341af1a : fffffa80`04805a70 fffff880`0316be30 fffffa80`04805a70 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0316bc50 fffff800`0341add5 : 00000000`00000004 00000000`00000001 fffff880`0316beb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0316bc90 fffff800`0340ee88 : 00000000`00000000 00000000`0055bb60 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0316bcc0 fffff800`034c27ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0316bcf0 fffff800`034c2613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0316be30 00000000`6ce06ca6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0055bb4c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6ce06ca6


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

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

No sir. But I must tell you that the processor series of my laptop has a sort of a "turbo". The original 2.53 Ghz can reach up to 2.8 I think when it's needed. It's a built-in ability.

 

[Maguscreed]

Yeah that feature should not be resulting in this kind of behavior.

This kind of error is really hard to pinpoint. The only software I've seen it caused by is bad dvd/cd NIC stuff. I don't think that's your case here though.

A memory test can be easily run overnight while you sleep using these steps.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

If you are still under ASUS support I would ahead and contact them explaining the error you've received. You might even want to include the minidump snippet I attached above.

 

[digiknowzone]

Yeah that feature should not be resulting in this kind of behavior.

This kind of error is really hard to pinpoint. The only software I've seen it caused by is bad dvd/cd NIC stuff. I don't think that's your case here though.

A memory test can be easily run overnight while you sleep using these steps.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

If you are still under ASUS support I would ahead and contact them explaining the error you've received. You might even want to include the minidump snippet I attached above.

I've already run a memtest several months ago, and there were no negative results. How should I proceed with this?

 

[Maguscreed]

Just out of curiosity, how long did you run memtest and for how many passes?
We reccomend a minimum of 7 which is why I say overnight.

Harddrive diagnostics can also help, but I have no idea what brand hdd they have put in that laptop so I can't point you to the manufacturer's site to get the diagnostic software.

As for contacting ASUS, that's actually fairly simple, you just create an account there and submit a support ticket.

 

[digiknowzone]

I can't fairly remember how many passes there were but I'm sure that there were no negative results. But just to be sure, I'll run a memtest again tonight.

I already sent a technical inquiry request to ASUS support.

 

[Maguscreed]

Sorry things have been hectic for me the last couple of days.
Well since memtest actually crashed that definitely supports the hardware problem theory.
As it completely rules out windows as a factor.

Unfortunately I'm not closer to telling you what the problem is if memtest is crashing but not showing any errors.

We can try running prime95 to see if it produces any instruction set errors in the cpu.
|MG| Prime95 26.6 Build 3 Download

 

[digiknowzone]

Sorry things have been hectic for me the last couple of days.
Well since memtest actually crashed that definitely supports the hardware problem theory.
As it completely rules out windows as a factor.

Unfortunately I'm not closer to telling you what the problem is if memtest is crashing but not showing any errors.

We can try running prime95 to see if it produces any instruction set errors in the cpu.
|MG| Prime95 26.6 Build 3 Download

Thank you for getting out of your way to answer my question. I really appreciate it. I'll try your suggestion.

I also would like to try changing the RAM at first, but the problem is that I'm still under warranty, and I might break the warranty rule if ever I try "tampering" their hardware. Thanks again. I'll let you know what happens with the test.

P.S. As I understand, the memtest will work with both 32-bit and 64-bit OS right?