Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Looking for merciful soul that would help me analyze few BSOD minidumps :)

I have updated the BIOS, have latest NVIDIA drivers and all works OK even under load testing. But from time to time (1-3h) a BSOD with random message will appear.

System info Windows 7 x64 RTM

AMD Phenom II X4 820
8GB of DDR3 RAM(4 x 2) Kingston
Gainward GTS 250 512MB DDR3
HDD1: Samsung SATA 320GB
HDD2: Samsung SATA 1TB
MOBO: Gigabyte MA770T-UD3P

Memory diagnostic does not show any problems...

You can get the memory dumps (link is dead now)

Any suggestion on how to trouble shoot this further?


WinDbg !analyze:

Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )

Blame MS? :) I guess Ill start swapping RAM in and out.

More details:

An exception happened while executing a system service routine.
Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002c8894b, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800b148bc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.


memtest86+ showed an error with overnight testing - time to swap out the rams :) hopefully its them not the mobo or cpu.

Thank you for your imputs!

share|improve this question
pls, specify your BSOD error – MicTech Aug 22 '09 at 16:29
Done, I didn't specify it earlier as I was getting a new each time, now it seems I get the SYSTEM_SERVICE_EXCEPTION for last few times. – Kamil Zadora Aug 22 '09 at 16:41
up vote 8 down vote accepted

082309-14742-01.dmp indicates that you have faulty hardware:

CONTEXT:  fffff88008876fc0 -- (.cxr 0xfffff88008876fc0)
rax=0000000000000001 rbx=fffffa800953ec20 rcx=0000000000000001
rdx=f7fff880009ea868 rsi=00000000000014e0 rdi=fffff880009e7180
fffff800`02cd094b 488b42f8        mov     rax,qword ptr [rdx-8] ds:002b:f7fff880`009ea860=????????????????

Note that rdx=f7fff880009ea868. That's a non-canonical x64 kernel mode address. Valid x64 kernel mode addresses range from 0xffff800000000000 to 0xffffffffffffffff. The '7' digit looks like a single bit error. All of the other dumps display the same stuck bit. I'd try swapping out your RAM first and running Memtest86+, but it could be the motherboard or CPU as well.

Also, the crash associated with 082309-24663-01.dmp occurred while executing VirtualBox.exe, but I think that's a red herring. Nonetheless, virtualization software is worth mentioning when posting about a bugcheck.

share|improve this answer
Thanks, VirtualBox was one of many BSODs :) – Kamil Zadora Aug 22 '09 at 20:19
Yup, after a night of testing with memtest86+ - error found... – Kamil Zadora Aug 23 '09 at 6:15

BlueScreenView from NirSoft might help you determine which files caused the BSOD.

It is compatible with Windows 7 and 64bit.

share|improve this answer

Load it up in WinDbg, do '!analyze' look for the module with the star next to it and blame them.

share|improve this answer

The best way to debug this issue is to strip the motherboard down to the minimum components that allow the install, then swap components out one-by-one with known good components which were tested on another system first until the issue goes away. Start from the minimum baseline, then make changes one at a time.

This may not be the most fun way to find the offending component/driver, but it is very effective.

share|improve this answer
I tried without the second hdd and dvd-drive - all else I can strip are DDR3 modules. – Kamil Zadora Aug 22 '09 at 20:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .