Windows 7 Too many BSODS :(

[manojr]

Hi,
Just before I go to sleep.
COuld you see any errors on these logs at all thats actually causing my system to fail again n again please?
these are all fresh logs .
one thing amazes me is the BSOD errors are all different and pointing out different things.

regards,Manojr

 

[cybercore]

Just before I go to sleep.
COuld you see any errors on these logs at all thats actually causing my system to fail again n again please?

Sure, all kinds of errors including 0x124 (hardware). In the bios, look for memory options, download and study your bios manual.











Crash Dumps:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\DMP\031311-15459-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*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.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x8281f000 PsLoadedModuleList = 0x82967810
Debug session time: Sun Mar 13 17:54:25.968 2011 (UTC - 5:00)
System Uptime: 0 days 0:18:42.903
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
...........
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: 858a9024, Address of the WHEA_ERROR_RECORD structure.
Arg3: f6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000181, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1f

STACK_TEXT:  
807cb8cc 82c3df3f 00000124 00000000 858a9024 nt!KeBugCheckEx+0x1e
807cb908 828ee004 858a1c31 858a9024 82887610 hal!HalBugCheckSystem+0xab
807cb938 82c3e1f1 85898668 82c4be40 00000005 nt!WheaReportHwError+0x230
807cba4c 82c3e2e3 85898668 858986b8 00000000 hal!HalpMcaReportError+0x3b
807cba70 82c3e54f 00000000 858986b8 807cbb90 hal!HalpMceHandler+0x8b
807cba80 82c345f5 00000000 00000001 00000000 hal!HalpHandleMachineCheck+0x3b
807cbb90 82c31261 00000002 807c6750 3f3f7852 hal!HalpMcaExceptionHandler+0x87
807cbb90 00000000 00000002 807c6750 3f3f7852 hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

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

























Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\DMP\031311-17612-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*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.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82839000 PsLoadedModuleList = 0x82981810
Debug session time: Sun Mar 13 17:25:45.149 2011 (UTC - 5:00)
System Uptime: 0 days 0:04:49.084
Loading Kernel Symbols
................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {828be8, ff, 8, 828be8}

Probably caused by : ntkrpamp.exe ( nt!PoIdle+538 )

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






















Loading Dump File [F:\a\Minidump\D M P\DMP\031311-24414-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*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.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82841000 PsLoadedModuleList = 0x82989810
Debug session time: Sun Mar 13 18:15:34.980 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:32.931
Loading Kernel Symbols
................................................
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..
*** WARNING: Unable to verify timestamp for Unknown_Module_8b2174c7
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_8b2174c7
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {807c4a80, 27f43963, 807dfc00, 0}

Unknown module 'Unknown_Module_8b2174c7' found on stack, using vad to reload module.
!vad_reload -1 0xffffffff8b2174c7
8a01ff45: Unable to get VAD.PrivateMemory
Probably caused by : Unknown_Module_8b2174c7 ( Unknown_Module_8b2174c7+22956ef )

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























Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\DMP\031311-23181-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*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.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82849000 PsLoadedModuleList = 0x82991810
Debug session time: Sun Mar 13 18:20:10.626 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:41.577
Loading Kernel Symbols
................................................
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
..Missing image name, possible paged-out or corrupt data.
.......Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {d, 0, 0, 0}

Probably caused by : ntkrpamp.exe ( nt!PoIdle+538 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 828ce79d to 8c8e4bb6

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
8296fc98 828ce79d 86104848 8297c280 82972c00 0x8c8e4bb6
8296fd20 828b114d 00000000 0000000e 00000000 nt!PoIdle+0x538
8296fd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PoIdle+538
828ce79d f70588e8978200800000 test dword ptr [nt!PerfGlobalGroupMask+0x8 (8297e888)],offset <Unloaded_Unknown_Module_0000000a>+0x7ff6 (00008000)

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PoIdle+538

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc78ed4

FAILURE_BUCKET_ID:  0x7f_d_nt!PoIdle+538

BUCKET_ID:  0x7f_d_nt!PoIdle+538

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

Drivers:

start    end        module name
8823b000 88283000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
88200000 88209000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
88360000 88369000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
88369000 8838c000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
82e4a000 82e52000   BOOTVID  BOOTVID.dll  unavailable (00000000)
82e94000 82f3f000   CI       CI.dll       unavailable (00000000)
887a3000 887c8000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
82e52000 82e94000   CLFS     CLFS.SYS     unavailable (00000000)
88596000 885f3000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
88792000 887a3000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
88209000 8821a000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
82fbe000 82ff2000   fltmgr   fltmgr.sys   unavailable (00000000)
8840e000 88417000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
88760000 88792000   fvevol   fvevol.sys   Mon Jul 13 19:13:01 2009 (4A5BBF7D)
88979000 889aa000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
82812000 82849000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
88758000 88760000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
80b9a000 80ba2000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
88583000 88596000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
88723000 88748000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
82e2e000 82e39000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll unavailable (00000000)
8834a000 88360000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8828c000 88294000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
88558000 88583000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
88748000 88758000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8862e000 886e5000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
886e5000 88723000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
82849000 82c59000   nt       ntkrpamp.exe Tue Oct 26 22:30:44 2010 (4CC78ED4)
88429000 88558000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8838c000 883b1000   nvstor   nvstor.sys   Wed May 20 02:44:09 2009 (4A13A6B9)
882c9000 882da000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
88294000 882be000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
88335000 8833c000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
8833c000 8834a000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
88400000 8840e000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
82e39000 82e4a000   PSHED    PSHED.dll    unavailable (00000000)
88800000 8882d000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
889f2000 889fa000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
883b1000 883f8000   storport storport.sys Mon Jul 13 19:45:58 2009 (4A5BC736)
88830000 88979000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
000e000e 01d36f7e   Unknown_Module_000e000e Unknown_Module_000e000e unavailable (00000000)
882be000 882c9000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
889aa000 889b2380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
882da000 882ea000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
882ea000 88335000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
889b3000 889f2000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
82f3f000 82fb0000   Wdf01000 Wdf01000.sys unavailable (00000000)
82fb0000 82fbe000   WDFLDR   WDFLDR.SYS   unavailable (00000000)
88283000 8828c000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
Missing image name, possible paged-out or corrupt data.

Unloaded modules:
206c6564 2220712f   Unknown_Module_206c6564
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  01B40BCB
01eacb20 206c6564   Unknown_Module_01eacb20
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  1E819A44
Missing image name, possible paged-out or corrupt data.
31383262 64312d36   Unknown_Module_31383262
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  32F8FAD4
0000000a 01eacebc   Unknown_Module_0000000a
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  01EACEB2
0000000a 01ea30c8   Unknown_Module_0000000a
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  01EA30BE
636f7270 33737365   Unknown_Module_636f7270
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  D00400F5
0000058d 0000316c   Ā×ĀçȀùĀĶȀ
䖋褜
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00002BDF
0000316a 0000000a   Unknown_Module_0000316a
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  FFFFCEA0
0000000a 00000000   Unknown_Module_0000000a
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  FFFFFFF6
Missing image name, possible paged-out or corrupt data.
00003164 00000001   Unknown_Module_00003164
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  FFFFCE9D
00000000 7465735c   Unknown_Module_00000000
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  7465735C
Missing image name, possible paged-out or corrupt data.
31207075 6578652e   Unknown_Module_31207075
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  3457F4B9
00000000 2e637263   Unknown_Module_00000000
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  2E637263
74666f73 65726177   Unknown_Module_74666f73
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  F10BF204

 

[manojr]

Hi there,
Just an update.
After endless hours of changing DRAM settings on my DDR2 667 I couldnt get it to work.
Got a set of DDr2 800 from my friend and tried endless DRAM settings the problem still presists

FSBRAM ratio fluctuates from CPU/4 to CPU/7 at times and the the DRAM frequency fluctuates likewise in CPUZ
I dont know why this is happening. I tried setting /5 setting on my BIOS but still doesnt work.
All I can now do is get a new system as this is too much hassle for me.

Have you got any ideas at all?

regards,
ManojR

 

[cybercore]

Have you got any ideas at all?

You probably got some setting in the bios wrong. If RAM sticks are rated 800mhz they should be set 800Mhz, not 667. If this was my PC I would load setup/optimized bios defaults. I would also test the sticks each individually and in different slots.

The 0x124 errors you've been getting can also be cased by faulty CPU.

 

[manojr]

Hi there,
I have changed few settings in the bios with regards to CPU voltage.
I am performing prime95 test at the moment and its been running for just over an hour, so far all the test have passed ( 5 done so far )

I have got CPU z running in the back ground as well and the DRAM frequency doesnt go over 368.4 Mhz with a setting of 5-5-5-15 23 where as at that setting it should be running at 400 Mhz. I will leave the test for rest of the afternoon.

Of all the settings i've tried so far, nothing has really bumped by DRAM frequency to 400 Mhz. Which is very strange.
I Will update you again about this.

 

[cybercore]

Stop 0x124:

- wrong bios setup
- bad bios version
- over or underclocking
- overheating
- hardware incompatibility
- faulty hardware
- rarely there is 3rd party driver offset with the stop 0x124, but this is not your case

Memtest86+ - Advanced Memory Diagnostic Tool

Prime95 - Overclock.net - Overclocking.net

Ram is set slightly wrong - 630Mhz while it's rated 667Mhz 5-5-5-15 1.8v.
The 0x124 errors you've been getting can also be cased by faulty CPU.

Stop 0x124 - what it means and what to try - Windows 7 Forums


Good luck.