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: Massive BSOD PLZ HELP

15 Jun 2010   #1

Windows 7

Hi im dessperate I recentlly sent my pc to a Win 7 installation , but since then massive ammounts of BSOD not lying 15 a day... so I took it back but they had my pc for a week and simply told me that it was ok(they didnt used my pc so no BSOD for them) so I tested it out but omg is the same... please i need help I get that 0x124 msg

My pc:
AMD Phenom Quad-Core
4gb Ram
Window 7 32- bit
ATI Radeon HD 3400 Series

Idk what else u need plz help

My System SpecsSystem Spec
15 Jun 2010   #2

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install


Code 124 is a common, but hard to diagnose problem. If you read this and try the suggestions, given, it may help. You had many, many dump files. I have read a few and have always found the bug code to report 124. Most likely a hardware problem.

 icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Low\Temporary Internet Files\Content.IE5\35JPVY5O\dump[1]\061310-21902-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82a3c000 PsLoadedModuleList = 0x82b84810
Debug session time: Sun Jun 13 16:40:15.805 2010 (GMT-4)
System Uptime: 0 days 0:00:16.146
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, 8606c4dc, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
1: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
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.
Arg1: 00000000, Machine Check Exception
Arg2: 8606c4dc, 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_AuthenticAMD
8d183cc4 82b0afc5 8606c4c0 82ba3c28 82ba3c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8d183ce4 82b0bdef 82ba3c20 8606c4c0 82ba3c50 nt!WheapProcessWorkQueueItem+0x56
8d183d00 82aa9f3b 82ba3c20 00000000 84fe0020 nt!WheapWorkQueueWorkerRoutine+0x1f
8d183d50 82c4a6bb 00000001 a47b80fe 00000000 nt!ExpWorkerThread+0x10d
8d183d90 82afc0f9 82aa9e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
Followup: MachineOwner
1: kd> lmtsmn
start    end        module name
8ad3f000 8ad87000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8ae30000 8ae39000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8ac00000 8ac09000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8ae0d000 8ae30000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
8aa39000 8aa41000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
8aa83000 8ab2e000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8b410000 8b435000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
8aa41000 8aa83000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8b013000 8b070000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
8b435000 8b442000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8b200000 8b211000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
8b44d000 8b456000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b442000 8b44d000   dump_ataport dump_ataport.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
8b456000 8b467000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
8ae6d000 8ae7e000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
8ae39000 8ae6d000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8b07e000 8b087000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8b1ce000 8b200000   fvevol   fvevol.sys   Mon Jul 13 19:13:01 2009 (4A5BBF7D)
8b36e000 8b39f000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
82a05000 82a3c000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
8b3f6000 8b3fe000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
80ba5000 80bad000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
8afd8000 8afeb000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8b17c000 8b1a1000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
8aa1d000 8aa28000   mcupdate mcupdate.dll Mon Jul 13 19:13:13 2009 (4A5BBF89)
8aa00000 8aa16000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8ad87000 8ad8f000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8afad000 8afd8000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8b3e6000 8b3f6000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8b087000 8b13e000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
8b13e000 8b17c000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
82a3c000 82e4c000   nt       ntkrpamp.exe Sat Feb 27 02:33:35 2010 (4B88CACF)
8ae7e000 8afad000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8adc4000 8add5000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
8ad9a000 8adc4000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8ade5000 8adec000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
8adec000 8adfa000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8b070000 8b07e000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8aa28000 8aa39000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
8b1a1000 8b1ce000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
8ad19000 8ad3f000   SCSIPORT SCSIPORT.SYS Mon Jul 13 19:45:55 2009 (4A5BC733)
8b3de000 8b3e6000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
8ac0f000 8ad10000   spnc     spnc.sys     Mon Mar 23 02:38:33 2009 (49C72E69)
8b225000 8b36e000   tcpip    tcpip.sys    Mon Jul 13 19:13:18 2009 (4A5BBF8E)
8ad8f000 8ad9a000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8add5000 8ade5000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8abad000 8abf8000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8b39f000 8b3de000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8ab2e000 8ab9f000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
8ab9f000 8abad000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8ad10000 8ad19000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
Mini Kernel Dump does not contain unloaded driver list
It may be a hardware problem.
My System SpecsSystem Spec


Thread Tools

Similar help and support threads
Thread Forum
Massive depreciation on RAM?
So I'm gonna sell my Kingston 2GB DDR3-10600 CL9 240-Pin DIMM since it's not compatible with my system. I found a local shop, but the person will buy it for only $4.47 (₱200); it's original price is $33.55 (₱1500). That's around 86.66% value reduction. The usage time of less than 20 minutes. Why?...
Hardware & Devices
Frequent BSOD with massive slowdown, possibly caused by ntoskrnl.exe
Hello all. My computer with Windows 7 Home Edition x64 has been getting frequent BSOD as well as being super slow and unresponsive. I have attached a copy of the recent dump files hoping to find anything out as to why this is happening. I am appreciative for any input I receive.
BSOD Help and Support
Massive HDD lag
Hello. Since i have some problems with my hdd I would like to ask you for some optimization advice. Currently I am running Windows 7 Ultimate Sp1 64bit operating system with latest drivers (altough not latest BIOS). Sometimes my hdd lags very badly, by that, I mean it is overloading. It is very...
Performance & Maintenance
Massive BSOD problem
I recently built a new computer system in early March with a Windows XP OS. It worked perfectly for about a month and then began giving the BSOD regularly, at least once a day. I initially assumed that this might be a problem with my newer hardware not being compatible with XP so I upgraded to...
BSOD Help and Support
Just a few massive problems.
I put win7 on an empty 80GB HDD a few days after it was released and have been using it every day since, every day up to today that is, why? Win 7 has completely filled up the 80GB drive. Check out what this beta has done. The Windows folder is now 7.7GB, thatís bad but not as bad as this...
General Discussion

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+