Very Random Blue screens

KeyKeeper

Member
Nov 22, 2004
73
0
0
Loading dump file C:\Windows\Minidump\Mini082607-03.DMP
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00386000
PfnDataBase 81800000
PsLoadedModuleList 805533a0
PsActiveProcessHead 80559458
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000009c
BugCheckParameter1 00000004
BugCheckParameter2 805461f0
BugCheckParameter3 b2000010
BugCheckParameter4 00010c0f
PaeEnabled 00000001
KdDebuggerDataBlock 80544ee0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00003fff
DriverListOffset 00006c10
DriverCount 00000092
StringPoolOffset 00009768
StringPoolSize 00001430
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack ad2bb000
DebuggerDataOffset 00006980
DebuggerDataSize 00000290
DataBlocksOffset 0000ab98
DataBlocksCount 00000004


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Sun Aug 26 18:54:09 2007
System Uptime: 0 days 0:04:20
start end module name
804d7000 806cd580 nt Checksum: 00200031 Timestamp: Wed Feb 28 02:
38:52 2007 (45E53F9C)

Unloaded modules:
ad76f000 ad782000 naveng.sys Timestamp: unavailable (00000000)
ad782000 ad854000 navex15.sys Timestamp: unavailable (00000000)
ae0e2000 ae0f5000 naveng.sys Timestamp: unavailable (00000000)
ae0f5000 ae1c7000 navex15.sys Timestamp: unavailable (00000000)
b5492000 b5497000 Cdaudio.SYS Timestamp: unavailable (00000000)
b0b1d000 b0b20000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check



Loading dump file C:\Windows\Minidump\Mini090707-01.DMP
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00386000
PfnDataBase 81800000
PsLoadedModuleList 805533a0
PsActiveProcessHead 80559458
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000009c
BugCheckParameter1 00000004
BugCheckParameter2 805461f0
BugCheckParameter3 b2000010
BugCheckParameter4 00010c0f
PaeEnabled 00000001
KdDebuggerDataBlock 80544ee0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00003000
DriverListOffset 00005c10
DriverCount 00000086
StringPoolOffset 000083d8
StringPoolSize 00001278
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack 80546300
DebuggerDataOffset 00005980
DebuggerDataSize 00000290
DataBlocksOffset 00009650
DataBlocksCount 00000004


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Fri Sep 07 16:54:26 2007
System Uptime: 0 days 18:32:03
start end module name
804d7000 806cd580 nt Checksum: 00200031 Timestamp: Wed Feb 28 02
38:52 2007 (45E53F9C)

Unloaded modules:
a57b8000 a57e3000 kmixer.sys Timestamp: unavailable (00000000)
a362e000 a3651000 aec.sys Timestamp: unavailable (00000000)
a360c000 a362f000 aec.sys Timestamp: unavailable (00000000)
a57b8000 a57e3000 kmixer.sys Timestamp: unavailable (00000000)
a57b8000 a57e3000 kmixer.sys Timestamp: unavailable (00000000)
a57b8000 a57e3000 kmixer.sys Timestamp: unavailable (00000000)
a57b8000 a57e3000 kmixer.sys Timestamp: unavailable (00000000)
a57b8000 a57e3000 kmixer.sys Timestamp: unavailable (00000000)
a7076000 a70a1000 kmixer.sys Timestamp: unavailable (00000000)
baefc000 baefd000 drmkaud.sys Timestamp: unavailable (00000000)
b0a29000 b0a36000 DMusic.sys Timestamp: unavailable (00000000)
a7231000 a723f000 swmidi.sys Timestamp: unavailable (00000000)
a70a1000 a70c4000 aec.sys Timestamp: unavailable (00000000)
badc4000 badc6000 splitter.sys Timestamp: unavailable (00000000)
a72e1000 a72f4000 naveng.sys Timestamp: unavailable (00000000)
a72f4000 a73c6000 navex15.sys Timestamp: unavailable (00000000)
a72e1000 a72f4000 naveng.sys Timestamp: unavailable (00000000)
a72f4000 a73c6000 navex15.sys Timestamp: unavailable (00000000)
a7c04000 a7c17000 naveng.sys Timestamp: unavailable (00000000)
a7c17000 a7ce9000 navex15.sys Timestamp: unavailable (00000000)
aa858000 aa863000 imapi.sys Timestamp: unavailable (00000000)
aa868000 aa877000 redbook.sys Timestamp: unavailable (00000000)
aa7a7000 aa7ac000 Cdaudio.SYS Timestamp: unavailable (00000000)
aa888000 aa895000 cdrom.sys Timestamp: unavailable (00000000)
aa81d000 aa820000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check


BSOD are very random, once every 10 min or sometimes after a couple days of runtime. Machine will do this when sitting idle with next to nothing running in background. Im suspecting psu since it sounds like the fans change pitch every few seconds or maybe mobo. Mobo is little over 2 years old and psu is little over 1 year old.

ASUS A8N SLI DELUXE
2 gig ddr 400 (factory speeds)
Athlon FX 55
XFX 7800gt
STF60 psu
three hdd (all sata, no raid)

Any ideas?
 

KeyKeeper

Member
Nov 22, 2004
73
0
0
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000004
Arg2: 805461f0
Arg3: b2000010
Arg4: 00010c0f

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

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000000000000000000001000000000000000000010000110000001111


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL



Concatenated Error Code:
--------------------------
_VAL_UC_EN_PCC_BUSCONNERR_F

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_AuthenticAMD

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 806d38df to 804f8aef

STACK_TEXT:
805461c8 806d38df 0000009c 00000004 805461f0 nt!KeBugCheckEx+0x1b
805462f4 806cec2e 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
805462f4 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x46


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x9C_AuthenticAMD_ANALYSIS_INCONCLUSIVE

BUCKET_ID: 0x9C_AuthenticAMD_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner


" Concatenated Error Code:
--------------------------
_VAL_UC_EN_PCC_BUSCONNERR_F"

taking that this is the meat n potatoes of the bug report.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
That tells me you need to tell your hardware manufacturer you have a hardware problem and get a replacement machine. Do all the dumps say the same thing?
 

JustaGeek

Platinum Member
Jan 27, 2007
2,827
0
71
@dclive,

Off the topic - I've been trying to access your website using the above link, but am getting the message:

Internet Explorer cannot display the webpage

Most likely causes:
You are not connected to the Internet.
The website is encountering problems.
There might be a typing error in the address.

What you can try:
Diagnose Connection Problems



Any particular reason for that...?

Thanks.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Grab another browser. Ensure you say yes to any certificate out-of-date prompts. Can you still not get in?
 

JustaGeek

Platinum Member
Jan 27, 2007
2,827
0
71
I'm on my Vista laptop.

Let me try my XP machine.

BTW, I've tried before, the browser would just always act like the website was inaccessible.


UPDATE: Still no dice, Vista or XP, waiting for the website to answer, and then the white screen.

As if the website was off line.

BTW, the "Reporting tool" download link works fine.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
It works for others, since the OP was clearly able to get there and learn how to analyze things....Can the OP confirm he was able to get to the website?

Troubleshoot it - what happens when you ping it? When you tracert it? When you go to an internet-based ping tool website and try to ping it? What's your DNS pointed to? Troubleshoot it and let us know what you find...
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Bear in mind when you update an already posted reply, no one will see the update, so it's quite easy to completely miss any updates.

Please post full output of the PING command, the TRACERT command to that site, and type 'nslookup' and then key in that website and post the output.

 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
By that I mean there is no e-mail notification that you've updated anything.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Go to your PC.
Type Start\Run and type CMD and press enter.
Type 'ping bluescreens.livenode.com' and press enter. Paste the output into here.
Type 'nslookup bluescreens.livenode.com' and press enter. Paste the output here.
Type 'tracert bluescreens.livenode.com' and press enter. Paste the output here.
Thanks.
 

JustaGeek

Platinum Member
Jan 27, 2007
2,827
0
71
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\>ping bluescreens.livenode.com
Ping request could not find host bluescreens.livenode.com. Please check the name
and try again.

C:\>nslookup bluescreens.livenode.com
Server: UnKnown
Address: 00000000000

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\>tracert bluescreens.livenode.com
Unable to resolve target system name bluescreens.livenode.com.

C:\>


That's all I could get...
 

JustaGeek

Platinum Member
Jan 27, 2007
2,827
0
71
Thanks, dclive.

Don't worry about it for now - I was just curious, but again, it would be an educational experience for me.

If you find a solution, please PM me, so I don't have to go off-topic in another thread - it's a little unfair to the OP.

Thanks again!
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
I'd suggest asking your ISP, or examining what internet filtering software you're running, as many others can get to the site without issue or incident. Can you call up your ISP and see if they can ping the site? If you boot in safe mode with networking can you ping the site? Etc... do a bit of troubleshooting and let us know what you find.
 

KeyKeeper

Member
Nov 22, 2004
73
0
0
Originally posted by: dclive
Do all the dumps say the same thing?


Yes they are all the same. I built the machine 3 years ago so Im kind of out of luck on getting any hardware support. Im about ready to move to intel anyway so new build is in the mix already.

 

JustaGeek

Platinum Member
Jan 27, 2007
2,827
0
71
Originally posted by: dclive
I'd suggest asking your ISP, or examining what internet filtering software you're running, as many others can get to the site without issue or incident. Can you call up your ISP and see if they can ping the site? If you boot in safe mode with networking can you ping the site? Etc... do a bit of troubleshooting and let us know what you find.

It just occurred to me:

Are you sure it is not on your end? Are your website's security settings allowing anyone to access the site?

This is the only site that I can't access... as far as I know.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
I'd asked the OP to confirm he can get to it, but you're the first I've heard of that can't get to the site, so to me that suggests the problem is on your end, not here. If the OP or someone else would confirm they can get to the site, that would be most helpful, but so far there have been no other complaints in getting to the site, and others clearly are able to do so since they report back the required steps after looking at the site. A friend with another ISP than mine was able to connect to the site recently, as well, which again suggests a problem on your end.

If the OP could confirm he could get to the site, that would be most helpful.
 

JustaGeek

Platinum Member
Jan 27, 2007
2,827
0
71
Perhaps your site requires port 113 of the remote computer NOT to be in the stealth mode...?
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
It isn't a site issue. Your DNS cannot resolve it. The only question is if anyone else's DNS can resolve it. So far, the answer to that question has been yes (I really do wish the OP would chime in...), hence my suggestion that you call your ISP and figure out why they can't resolve that entry in DNS.
 

JustaGeek

Platinum Member
Jan 27, 2007
2,827
0
71
Originally posted by: KeyKeeper
I have no issues getting to the site with either browser.

Is your computer "pingable"...? Do you play games on line?

Is your port 113 open...?

Sorry to ask these questions in your thread, I thought the answers would be simpler... and shorter.