BSOD, various errors, 1000007e, 0000000a, 0000001a

[klaberte]

Hello! Several BSODs with various errors. Self built machine, recently (May, 5 months ago) wiped disk and installed Win7 Pro 32 bit.

Please let me know if you need more info than in the attached files.

 

[seth500]

Most likely cause is memory corruption please run memtest86 vis this guide:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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


Loading Dump File [C:\Users\Administrator\Downloads\Windows_NT6_BSOD_jcgriff2\091111-17187-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x82c0a000 PsLoadedModuleList = 0x82d4a250
Debug session time: Sun Sep 11 12:58:34.435 2011 (UTC - 6:00)
System Uptime: 3 days 20:21:19.263
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8aa93977, 2, 0, 82cbd31e}

Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+a4 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 8aa93977, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82cbd31e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82d69828
Unable to read MiSystemVaType memory at 82d49da0
 8aa93977 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiRelinkStandbyPage+a4
82cbd31e 0fb6500f        movzx   edx,byte ptr [eax+0Fh]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  9cca3a10 -- (.trap 0xffffffff9cca3a10)
ErrCode = 00000000
eax=8aa93968 ebx=00000005 ecx=000033f5 edx=00000005 esi=844c0980 edi=82d6a3a4
eip=82cbd31e esp=9cca3a84 ebp=9cca3a9c iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
nt!MiRelinkStandbyPage+0xa4:
82cbd31e 0fb6500f        movzx   edx,byte ptr [eax+0Fh]     ds:0023:8aa93977=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82cbd31e to 82c42c5b

STACK_TEXT:  
9cca3a10 82cbd31e badb0d00 00000005 00000000 nt!KiTrap0E+0x2cf
9cca3a9c 82c331c7 00000002 85799000 9cca3bac nt!MiRelinkStandbyPage+0xa4
9cca3ad4 82dee490 00000100 85799980 818e8122 nt!MmSetPfnListPriorities+0x167
9cca3b20 82ded8af 82e02801 818e81e2 0000004f nt!PfpPfnPrioRequest+0x61
9cca3be0 82def180 00b7f4dc 00000014 82e02801 nt!PfSetSuperfetchInformation+0x176
9cca3d20 82c3f87a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0xbdd
9cca3d20 777d70b4 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00b7d3cc 00000000 00000000 00000000 00000000 0x777d70b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+a4
82cbd31e 0fb6500f        movzx   edx,byte ptr [eax+0Fh]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02a381

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiRelinkStandbyPage+a4

BUCKET_ID:  0xA_nt!MiRelinkStandbyPage+a4

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

 

[klaberte]

memtest86 results

I ran memtest86 for 33 hours. It found 0 errors.

Any advice on what to try next?

Many thanks!

 

[seth500]

Please run driver verifier and after it blue screens resend the JCGriff BSOD Posting instructions like you did the first time this will pinpoint the guilty driver that is causing the issue.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Follow that guide the follow with this guide again:

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Thanks

Seth

 

[MvdB]

My 2 ct: Please also check your firmware. As it is you own build, you probably logged what you put in. This needs an update:

Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2011-09-11T15:20:37.828
  Event ID: 6
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Sessiun
  Description: 
Some processor performance power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware.

It does not have to be a problem but is known to cause crashes depending on your Powermanagement settings. Please check both the firmware and your Powermanagement. For the latter, I'd turn off ALL energy saving, also at device level, until proven stable.

Also, just some advice, I know your 32B system should be able to run on a 2GB RAM system. However, seeing the modules you have loaded in memory (standard) means it will be constantly swapping RAM space onto the HDD and back. It would improve in performance and maybe stability if you're able to up that to 4GB...

Also, how you use the system would help you a lot, please don't be offended but your log shows 24 open Chrome sessions totaling more than 1GB in RAM usage alone.

Next, what worries me slightly, though it could be related to the firmware prob... I don't see it often but instead of Overclocking... your system is Underclocking by 3.7% ?? Did you do anything on purpose here?

And last... I've seen problems with this old driver before:

ltmdmnt.sys   Wed Mar 08 15:23:07 2006 (440EE8CB)

Only place I know it from is a Lucent modem. Please try to find update or if you don't use the modem, delete the driver please.

 

[klaberte]

@seth

Thanks for your quick reply. I understand your instructions about verify and will run until my next BSOD, then repost as you requested.

@MvdB I know what firmware is in the abstract, but what does it mean here? Drivers? BIOS? I will turn off all power management for now.

Thanks for the suggestion on RAM. I know that 24 tabs in Chrome is excessive, but I never realized how costly it was till now. I'm not sure about adding RAM in the middle of this troubleshooting (any advice?) but will plan to upgrade once things stabilize. The honest truth is that I upgraded from WinXP to Win7 without a RAM increase...

I have made no attempt to over or underclock. Perhaps something in the BIOS? I'll check, although I think I've recently set it to restore to defaults.

I'm definitely not using an analog modem, so I can get rid of this. Is it just as simple as disabling (or uninstalling) in the device manager?

Again, thanks to all! I really appreciate your help!

Ken

 

[MvdB]

The firmware is stuff that runs on your motherboard in this case. Normally you'd update from the manufacturers' site, if available.

However, to be sure you find the root cause of your problems, as always, do one thing at a time and test. Except for the RAM, if you're willing to spend the money, I'd do that asap. Be sure to check compatibility with your mobo, before buying.

The modem: disable in Devices and then delete the driver to be sure that is not loaded on reboot anyway...

 

[klaberte]

Finally, got another BSOD

It took a couple of weeks, but finally got another BSOD. Hopefully I've followed all the directions as requested.

I am anxious to hear your feedback!

 

[klaberte]

Another BSOD

Got another BSOD. This time only had to wait a few days! Files are attached.

Many thanks!

Ken

 

[MvdB]

sorry for the delay, very busy here.
One of your errors is hardware (code 124):

Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct  3 10:00:47.603 2011 (UTC + 2:00)
System Uptime: 1 days 6:53:54.808
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x18
PROCESS_NAME:  VSSVC.exe
FAILURE_BUCKET_ID:  0x18_VRF_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWithTag+4b
Bugcheck code 00000018
Arguments 84e4ea10 89193810 00000001 00000001
BiosVersion = P1.80
BiosReleaseDate = 12/18/2007
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     1860
CurrentSpeed: 1792
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 16:47:45.984 2011 (UTC + 2:00)
System Uptime: 0 days 0:00:06.906
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000 8c6ea024 00000000 00000000

And you are still underclocking. Probably need a local HW expert to help you on that because it is kind of difficult to check at a distance.

Before we start tests to see if it is really hardware, please check this site for a newer version of your (Envy24HF.sys) drivers: VIA Vinyl Audio - VIA Technologies, Inc.

 

[klaberte]

Another crash

Had another crash before I could act on mvdb's suggestions. Perhaps it adds more light?

 

[MvdB]

Still HW errors:

Event[38]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2011-10-08T13:38:58.322
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Sessiun
  Description: 
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Bus/Interconnect Error
Processor ID: 1

The details view of this entry contains further information.

Event[39]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2011-10-08T13:38:58.322
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Sessiun
  Description: 
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Bus/Interconnect Error
Processor ID: 0

The details view of this entry contains further information.

Event[40]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2011-10-08T13:38:58.322
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Sessiun
  Description: 
A fatal hardware error has occurred.

Don't have much time now to analyse more but please check up on code 124 and what to test:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html