Category Archives: Setup

Cool down – Family Notebook

Hi, something i would like to share is the familiy notebook story. Actually the problem is that we have a family notebook with 5-7 active users and the fan was loud. So I decided to use a cpufreq governor “ondemand”, … Continue reading

Posted in IT, Notebook, Setup, ubuntu | Tagged , , , , , , | Leave a comment


So what is going to happen if you have installed everything, you are really happy about your setup and you think: “hey tomorrow i will even do a backup! Because it is really worth to preserve this!” Quite simple:

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

Loading Dump File [G:\Minidump52910-45333-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
Symbol search path is: srv*c:\cache*;

Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82a0f000 PsLoadedModuleList = 0x82b57810
Debug session time: Sat May 29 08:13:07.914 2010 (UTC + 2:00)
System Uptime: 0 days 0:08:03.802
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
0: 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: 85d51024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b6608000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

BUGCHECK_STR: 0x124_AuthenticAMD





82b32d2c 82e2df3f 00000124 00000000 85d51024 nt!KeBugCheckEx+0x1e
82b32d68 82addf04 85d425c9 85d51024 82a774d0 hal!HalBugCheckSystem+0xab
82b32d98 82e2e1f1 85d51ea8 82e3be40 00000000 nt!WheaReportHwError+0x230
82b32eac 82e2e2e3 85d51ea8 85d51ef8 00000000 hal!HalpMcaReportError+0x3b
82b32ed0 82e2e54f 00000000 85d51ef8 82b32ff0 hal!HalpMceHandler+0x8b
82b32ee0 82e245f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x3b
82b32ff0 82e21261 0000001c 801df000 00000000 hal!HalpMcaExceptionHandler+0x87
82b32ff0 00000000 0000001c 801df000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89



MODULE_NAME: hardware

IMAGE_NAME: hardware




Followup: MachineOwner

So what happened my ASROCK HDready MB with AMD 3800 X2 worked fine with Windows XP, but after some time i decided to upgrade to Windows 7 :). After doing the setup (more or less 10 hours of work, vpn – firewall – vmware – bla bla bla … ) windows 7 started to surprise with BSOD.

After contacting the Asrock support i got Bios 2.19 for testing, this even killed my XP, which was still working perfectly in parallel :). After downgrading back to 1.20 i was still facing BSOD (minidump analyse shown above).

So what was may solution:

– installing cpu-z info tool checking core voltage and memory timing

– increasing core voltage to 1.30 (from auto to 1.30v)

– correcting memory timings from (auto to given values from cpu-z info tool)

up to now i am happy again, no BSOD anymore. 🙂


bye. Continue reading

Posted in Setup | Tagged | Leave a comment

OpenSolaris NAS with WAKE-ON-LAN (WOL) – Overview – OpenSolaris is master – HOWTO

Hey as i have already written down and as everyone can ready everywhere, OpenSolaris does not support WOL up to now (@01/2010). This was a real drawback if you like to have your NAS in the basement or in an unattached setup. So i took this challenge and found the following working solution for my setup.

NAS OS – OpenSolaris
WOL OS – Linux (in my case Ubuntu 9.10)

Ok, what does that mean? Basically the problem with WOL is that the OS has to support the right shutdown procedures in order to keep the WOL device powered and configured the right way in order to receive the wake up package, so it is a little bit more than WOL=1 *SMILE*.

So Linux support for the most NIC WOL, therefore my solution is quite simple, for a NAS shutdown reboot into Linux and setup WOL there and than really shut down.

How to do:

Assuming: OpenSolaris is already running
ToDo: Install Linux with Grub in partition setup
ToDo-OpenSolaris: add you Linux lines to the OpenSolaris GRUB.
ToDo-OpenSolaris: make the Linux default for next boot (change the /rpool/boot/grub/menu.lst default entry)
ToDo-Linux: Add a script to /etc/rc.local in order to setup WOL, change back OpenSolaris-Grub boot order to normal and shutdown


Details will follow… Continue reading

Posted in Setup | Tagged , , , | Leave a comment