blue screening

bbbbqq · 06 Oct 2010

Hey, I've got a computer here that's bluescreening randomly. I'm usually not around when it does it, though, so I can't see what the bluescreen message is. For some reason, eventviewer doesn't work for me, and it gives me the MMC could not create the snap-in. error. I did manage to get the minidump, though.

I was wondering if anyone could understand what is going on with this computer, and what I can do to diagnose it further and repair it.

Operating system is Windows 7 Ultimate x64
The CPU is an Intel E4300, the board is an Asus nforce based board (I forgot the actual number), 2gb of Crucial ram, and the OS drive is a 120gb Seagate IDE drive.

Thanks.

karlsnooks · 06 Oct 2010

bbbqq,

I'll let others look at your minidump file.

Here's a couple of suggestions:
1. Put your system info into system specs,
2. If the recommended Speccy program doesn't provide some of the missing info, then use MSINFO32.EXE

Speccy - System Information - Free Download

bbbbqq · 06 Oct 2010

Sure, here's the speccy output

neat program.

karlsnooks · 06 Oct 2010

I don't want the output in that form. What I suggest is that you merge that info into your System Specs.

HOW TO FILL OUT YOUR SYSTEM SPECS

In the line at the top of www.SevenForums.com you will see UserCP.
That is an abbreviation for User Control Panel.
Click on UserCP.
In the left-hand column, under Your Profile you will see Edit System Spec.
Click on Edit System Spec
You can copy and paste from the output of Speccy, Speccy - System Information - Free Download to fill out much of the info. Be sure to use the Other Info section of your System Specs for such info as your optical drive, your wireless adapter, your speakers, etc.

wish · 06 Oct 2010

bbbbqq said:

Hey, I've got a computer here that's bluescreening randomly. I'm usually not around when it does it, though, so I can't see what the bluescreen message is. For some reason, eventviewer doesn't work for me, and it gives me the MMC could not create the snap-in. error. I did manage to get the minidump, though.

I was wondering if anyone could understand what is going on with this computer, and what I can do to diagnose it further and repair it.

Operating system is Windows 7 Ultimate x64
The CPU is an Intel E4300, the board is an Asus nforce based board (I forgot the actual number), 2gb of Crucial ram, and the OS drive is a 120gb Seagate IDE drive.

Thanks.

No wonder if your Netbt crash , you need to update nVidia Ethernet Networking driver.
Remove speedfan because your version is out of date..

Code:

nvm62x64 nvm62x64.sys Fri Oct 17 14:01:06 2008 (48F8FD12)
speedfan speedfan.sys Sun Sep 24 06:26:48 2006 (45168798)

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ab, 2, 0, fffff88003ad2655}

Probably caused by : netbt.sys ( netbt!MSnodeRegCompletion+3f )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000000000ab, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003ad2655, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002abe0e0
 00000000000000ab 

CURRENT_IRQL:  2

FAULTING_IP: 
netbt!MSnodeRegCompletion+3f
fffff880`03ad2655 8a88ab000000    mov     cl,byte ptr [rax+0ABh]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c340 -- (.trap 0xfffff80000b9c340)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80041fc010
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003ad2655 rsp=fffff80000b9c4d0 rbp=0000000000000004
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
netbt!MSnodeRegCompletion+0x3f:
fffff880`03ad2655 8a88ab000000    mov     cl,byte ptr [rax+0ABh] ds:00000000`000000ab=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002887469 to fffff80002887f00

STACK_TEXT:  
fffff800`00b9c1f8 fffff800`02887469 : 00000000`0000000a 00000000`000000ab 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c200 fffff800`028860e0 : 00000001`00000070 fffffa80`041fc010 fffffa80`00000020 fffffa80`01c695c8 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c340 fffff880`03ad2655 : fffff800`02a00e80 fffff800`00b9cc58 fffffa80`03ae3060 fffff800`02a0ec40 : nt!KiPageFault+0x260
fffff800`00b9c4d0 fffff880`03abf1f7 : fffffa80`042f54b0 00000000`00000001 fffff880`03aec218 00000000`00000002 : netbt!MSnodeRegCompletion+0x3f
fffff800`00b9c540 fffff800`02893fa6 : fffff800`00b9c618 00000000`00000000 00000001`40940a00 00000000`00000002 : netbt!TimerExpiry+0x5b
fffff800`00b9c570 fffff800`02893326 : fffffa80`03ae3168 fffffa80`03ae3168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02893e7e : 00000000`192d5fa0 fffff800`00b9cc58 00000000`00000a93 fffff800`02a044e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02893697 : 00000000`0474eec3 00000000`00000a93 00000000`0474ee6a 00000000`00000093 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`028906fa : fffff800`02a00e80 fffff800`02a0ec40 00000000`00000000 fffff880`02d03588 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
netbt!MSnodeRegCompletion+3f
fffff880`03ad2655 8a88ab000000    mov     cl,byte ptr [rax+0ABh]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  netbt!MSnodeRegCompletion+3f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: netbt

IMAGE_NAME:  netbt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc178

FAILURE_BUCKET_ID:  X64_0xD1_netbt!MSnodeRegCompletion+3f

BUCKET_ID:  X64_0xD1_netbt!MSnodeRegCompletion+3f

Followup: MachineOwner

bbbbqq · 06 Oct 2010

Uninstalled and updated; Will see how that goes. I do have some other minidumps, though.

Thanks so far

karlsnooks · 06 Oct 2010

Wish,
Perhaps older versions of SpeedFan had problems, but I've never encountered any problems using SpeedFan.

wish · 06 Oct 2010

karlsnooks said:

Wish,
Perhaps older versions of SpeedFan had problems, but I've never encountered any problems using SpeedFan.

Thx for the info..

I never use speedfan so I dont know if there is a new version of speed fan.
And several minidumps that I ever look at always the older version of speedfan.sys

wish · 06 Oct 2010

bbbbqq said:

Uninstalled and updated; Will see how that goes. I do have some other minidumps, though.

Thanks so far

The dumps blame memory corruption and kernel windows corrupt..

Perform system file checker -> command prompt(as administrator) -> SFC /SCANNOW
Try windows memory diagnostics tools and memtest86 (at least 5 pass)
there is a newer version of your bios (P5N73-AM Revision 0501) -> should be (P5N73-AM BIOS 0602)
ASUSTeK Computer Inc.-Support-
Update your nVidia driver

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88003cf6306, fffff8800626ed60, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89418b5af, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 9cb599bdd34b010a, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

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

Jonathan_King · 06 Oct 2010

Wish is correct; do update your nVidia drivers.

If you need assistance with that, please follow these directions: https://www.sevenforums.com/crashes-d...tructions.html

That is the official BSOD sticky on this site.

Also, enable driver verifier: Driver Verifier - Enable and Disable

Wait for a few crashes, then follow the BSOD sticky.