Bsod Help please....

[soulwindstruck]

Asus M50sv Laptop
Processor: Intel Core 2 Duo [email protected]
Ram:2gb
Os:Win7 32bit
3dcard: Nividia geforce 9500m gs

I really didn't have any problems with my laptop until.. 1 day it just automatically restarted and had a bsod which i keep getting frequently now please help it's really a bother i really appreciate any help i can get.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 124
BCP1: 00000000
BCP2: 8585F4DC
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\020210-30170-01.dmp
C:\Users\Nax\AppData\Local\Temp\WER-46379-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Here ishe dmp file

http://rapidshare.com/files/34483673...70-01.dmp.html

please help me find the prob..

 

[zigzag3143]

Asus M50sv Laptop
Processor: Intel Core 2 Duo [email protected]
Ram:2gb
Os:Win7 32bit
3dcard: Nividia geforce 9500m gs

I really didn't have any problems with my laptop until.. 1 day it just automatically restarted and had a bsod which i keep getting frequently now please help it's really a bother i really appreciate any help i can get.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 124
BCP1: 00000000
BCP2: 8585F4DC
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\020210-30170-01.dmp
C:\Users\Nax\AppData\Local\Temp\WER-46379-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Here ishe dmp file

http://rapidshare.com/files/34483673...70-01.dmp.html

please help me find the prob..

Hi

I have tried to download the dmp from rapidshare 4 times servers were busy. Why dont you just attach it to the reply form using the attachment icon.

Let us know if you need help with that.

Ken

 

[soulwindstruck]

Oh here it is hope it helps

 

[zigzag3143]

Oh here it is hope it helps

Hi and welcome

this crash was caused by hardware. You can use these http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html to diagnose what.

Let us know if you need help

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\020210-30170-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a01000 PsLoadedModuleList = 0x82b49810
Debug session time: Tue Feb  2 08:54:20.516 2010 (GMT-5)
System Uptime: 0 days 0:00:10.530
Loading Kernel Symbols
.......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 8585f4dc, 0, 0}

Probably caused by : hardware

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8ab17cc4 82acffc5 8585f4c0 82b68c28 82b68c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8ab17ce4 82ad0def 82b68c20 8585f4c0 82b68c50 nt!WheapProcessWorkQueueItem+0x56
8ab17d00 82a6ef2b 82b68c20 00000000 848dba70 nt!WheapWorkQueueWorkerRoutine+0x1f
8ab17d50 82c0f66d 00000001 942b9412 00000000 nt!ExpWorkerThread+0x10d
8ab17d90 82ac10d9 82a6ee1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

 

[soulwindstruck]

sorry for the newbie question but.. isn't there anyway for me to narrow down which hardware? Im really not that good with hardware thingies

 

[ickymay]

sorry for the newbie question but.. isn't there anyway for me to narrow down which hardware? Im really not that good with hardware thingies

bluescreen view came up with

hal.dll hal.dll+5ba9 0x82e11000 0x82e48000 0x00037000 0x4a5bbf07 13/07/2009 23:11:03

It might be an idea to run something like speedfan to monitor your temperatures , as this could be a problem with your CPU

two drivers that need updating are

AsDsm.sys 0x88811000 0x8881b000 0x0000a000 0x46bc5723 10/08/2007 12:16:35
lullaby.sys 0x8881b000 0x88823000 0x00008000 0x46fa02cd 26/09/2007 06:57:17

AsDsm.sys - not sure ?
lullaby.sys - ASUS CopyProtect driver

how old is this machine and Is your bios the latest version ?

have you visited the ASUS site to get the latest drivers ?

 

[Capt.Jack Sparrow]

Hello, Welcome to SF,

You said it was working fine and one day i started BSOD. I its something with Driver or an update i guess maybe a System Restore can fix it ... Just a thought

Good Luck,
Captain

 

[soulwindstruck]

Oh i already tried system restore before but it didn't help sadly.. Is it possible that my usb keyboard is causing the error? Because when i plug it to the usb e-sata slot the bsod happens in about 70% of attempts i tried to plug it.. And i think everytime i get the bsod the keyboard is plugged in...

@ICKYMAY its about a year old.. Ill try the speed fan monitor.. But the bsod usually appears about 5-10minutes after startup.. So it doesnt give my computer the chance to warm up..

 

[usasma]

usb e-sata slot

Is this shaped just a tiny bit differently from the other USB slots?
If so, you shouldn't be plugging the USB keyboard into it - it could (and probably will) cause damage.

 

[ickymay]

Oh i already tried system restore before but it didn't help sadly.. Is it possible that my usb keyboard is causing the error? Because when i plug it to the usb e-sata slot the bsod happens in about 70% of attempts i tried to plug it.. And i think everytime i get the bsod the keyboard is plugged in...

yup at least try with another simple ps2 keyboard to eliminate it as a possibility :huh: