Windows 7: BSOD newly built system

n9ami · 26 Sep 2010

Just built up a 6 core AMD 1075T Asus M4A89GTD PRO 4 gig or ram ddr3 corsair dominator. Using 64 bit 7 and using on board graphics. Any Ideas would really help me out.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA8002363340
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\092610-21918-01.dmp
C:\Users\N9AMI\AppData\Local\Temp\WER-952042-0.sysdata.xml

zigzag3143 · 26 Sep 2010

Quote: Originally Posted by n9ami

Just built up a 6 core AMD 1075T Asus M4A89GTD PRO 4 gig or ram ddr3 corsair dominator. Using 64 bit 7 and using on board graphics. Any Ideas would really help me out.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA8002363340
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\092610-21918-01.dmp
C:\Users\N9AMI\AppData\Local\Temp\WER-952042-0.sysdata.xml

Well this crash was caused by crucialsmbusscan.sys. the only trouble is wether that is a valid driver or a virus. Ite is report as virus in over 80 % of the time. Plus it is dated from 2007.

First I would run a thorough virus scan. Only if it comes back clean should you even try to update it. If it is not a virus you need to find out what it is and update it.

Let us know if you need help with this

Ken J

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\092610-34866-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c1a000 PsLoadedModuleList = 0xfffff800`02e57e50
Debug session time: Sun Sep 26 12:31:18.196 2010 (GMT-4)
System Uptime: 0 days 2:03:20.507
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff884079fd10c, 2, 0, fffff880079fa59f}

Unable to load image \??\C:\Windows\system32\drivers\CrucialSMBusScan.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for CrucialSMBusScan.sys
*** ERROR: Module load completed but symbols could not be loaded for CrucialSMBusScan.sys
Probably caused by : CrucialSMBusScan.sys ( CrucialSMBusScan+159f )

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

1: 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: fffff884079fd10c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880079fa59f, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec20e0
 fffff884079fd10c 

CURRENT_IRQL:  2

FAULTING_IP: 
CrucialSMBusScan+159f
fffff880`079fa59f 458b048a        mov     r8d,dword ptr [r10+rcx*4]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  CrucialScan.ex

TRAP_FRAME:  fffff8800aa857a0 -- (.trap 0xfffff8800aa857a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000008000ff00 rbx=0000000000000000 rcx=00000000ffffffff
rdx=0000000000000cf8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880079fa59f rsp=fffff8800aa85930 rbp=0000000080000000
 r8=0000000000000000  r9=0000000080010000 r10=fffff880079fd110
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
CrucialSMBusScan+0x159f:
fffff880`079fa59f 458b048a        mov     r8d,dword ptr [r10+rcx*4] ds:fffff884`079fd10c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c89ca9 to fffff80002c8a740

STACK_TEXT:  
fffff880`0aa85658 fffff800`02c89ca9 : 00000000`0000000a fffff884`079fd10c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0aa85660 fffff800`02c88920 : 00000000`00000000 00000000`00000001 00000000`000007ff 00000000`00000080 : nt!KiBugCheckDispatch+0x69
fffff880`0aa857a0 fffff880`079fa59f : 00000000`00000000 fffffa80`03600638 ffffffff`00000000 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0aa85930 00000000`00000000 : fffffa80`03600638 ffffffff`00000000 00000000`00000001 00000000`00000000 : CrucialSMBusScan+0x159f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
CrucialSMBusScan+159f
fffff880`079fa59f 458b048a        mov     r8d,dword ptr [r10+rcx*4]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  CrucialSMBusScan+159f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CrucialSMBusScan

IMAGE_NAME:  CrucialSMBusScan.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45ba2503

FAILURE_BUCKET_ID:  X64_0xD1_CrucialSMBusScan+159f

BUCKET_ID:  X64_0xD1_CrucialSMBusScan+159f

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

n9ami · 28 Sep 2010

Thanks Ken I have had a few more and now for some reason the minidump file has locked me out very odd. Anyhow I deleted the file and will post the next one when it happens again. I appreciate your help.
john

n9ami · 29 Sep 2010

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000002
BCP2: 0000000000104AB4
BCP3: 000000000011FFFF
BCP4: 0000000000000001
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

n9ami · 29 Sep 2010

never ending I tell you. I am going to get some new ram today and see what happens.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000000000000010
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002C99B7F
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Windows 7: BSOD newly built system

BSOD newly built system problems?