BSODs with clean install 32bit

I installed my new release copy of Win7 about 10 days ago and have had 4 BSODs in that time.

The first checked online and said it was probably hardware related and couldn't be more specific. I have used Vista on this HTPC for about 18 months and had many BSODs but they always gave a file name of the offending driver.

The next 3 created DMP files which I have attached, hoping someone might have time to look at them and possibly find a reason.

Thanks very much.

"0x00000000, or Divide by Zero Error, indicates that a DIV instruction is executed and the divisor is zero. Memory corruption, other hardware problems, or software failures can cause this error."

Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP

Code:

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


Loading Dump File [E:\Temp\Rar$DI06.140\110109-22573-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x81a03000 PsLoadedModuleList = 0x81b4b810
Debug session time: Sun Nov  1 01:23:05.307 2009 (GMT-5)
System Uptime: 0 days 3:22:49.119
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {0, 0, 0, 0}

Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcVSyncCookie+f8 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_0

TRAP_FRAME:  81b29ad8 -- (.trap 0xffffffff81b29ad8)
ErrCode = 00000000
eax=00004c5b ebx=00000000 ecx=00000000 edx=00000000 esi=00000004 edi=85621008
eip=81a6ef8c esp=81b29b4c ebp=81b29ba8 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!_aulldiv+0x3c:
81a6ef8c f7f3            div     eax,ebx
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 81a6ef8c to 81a4728b

STACK_TEXT:  
81b29ad8 81a6ef8c badb0d00 00000000 00000055 nt!KiTrap00+0x8b
81b29b50 8b0b8cf0 000098b7 00000000 00000001 nt!_aulldiv+0x3c
81b29ba8 8b0bb4c7 85621f80 84a04000 8561e008 dxgmms1!VidSchiProcessDpcVSyncCookie+0xf8
81b29bc0 8b0bb832 84a04000 00000001 84b7a000 dxgmms1!VidSchDdiNotifyDpcWorker+0x5b
81b29be4 8cf37bf5 84b80920 81b29c04 8cf37cc4 dxgmms1!VidSchDdiNotifyDpc+0x78
WARNING: Stack unwind information not available. Following frames may be wrong.
81b29bf0 8cf37cc4 84610890 84b80920 8cef0bd0 dxgkrnl+0x1bf5
81b29c04 8c67cb44 84b80920 84b7a000 8c67cb0f dxgkrnl+0x1cc4
81b29c18 8c67cd74 84b7a000 8c67cd3f 81b29c40 nvlddmkm+0x63b44
81b29c28 8c67d1fb 84ac58a8 84b7a000 81b2e600 nvlddmkm+0x63d74
81b29c40 8c626050 84b809d8 81b29c58 8c6d2dc7 nvlddmkm+0x641fb
81b29c4c 8c6d2dc7 8c62601f 81b29c78 8cf378c1 nvlddmkm+0xd050
81b29c58 8cf378c1 84b7a000 84b80d10 81b36304 nvlddmkm+0xb9dc7
81b29c78 81a6b3b5 84b80d10 84b80920 00000000 dxgkrnl+0x18c1
81b29cd4 81a6b218 81b2cd20 81b36280 00000000 nt!KiExecuteAllDpcs+0xf9
81b29d20 81a6b038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
81b29d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiProcessDpcVSyncCookie+f8
8b0b8cf0 8b4f50          mov     ecx,dword ptr [edi+50h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VidSchiProcessDpcVSyncCookie+f8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc265

FAILURE_BUCKET_ID:  0x7f_0_dxgmms1!VidSchiProcessDpcVSyncCookie+f8

BUCKET_ID:  0x7f_0_dxgmms1!VidSchiProcessDpcVSyncCookie+f8

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

"0xC0000005: STATUS_ACCESS_VIOLATION indicates that a memory access violation occurred."

http://msdn.microsoft.com/en-us/library/ms794023.aspx

Code:

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


Loading Dump File [E:\Temp\Rar$DI00.500\110609-18673-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x81a44000 PsLoadedModuleList = 0x81b8c810
Debug session time: Fri Nov  6 03:20:08.563 2009 (GMT-5)
System Uptime: 0 days 4:53:41.219
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 81c96968, 8efd8b1c, 0}

Probably caused by : memory_corruption ( nt!MiMapViewOfDataSection+105 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81c96968, The address that the exception occurred at
Arg3: 8efd8b1c, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP: 
nt!MiMapViewOfDataSection+105
81c96968 8b4308          mov     eax,dword ptr [ebx+8]

TRAP_FRAME:  8efd8b1c -- (.trap 0xffffffff8efd8b1c)
ErrCode = 00000000
eax=00000001 ebx=00000000 ecx=8efd8c0c edx=00000000 esi=00000000 edi=00000000
eip=81c96968 esp=8efd8b90 ebp=8efd8be4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MiMapViewOfDataSection+0x105:
81c96968 8b4308          mov     eax,dword ptr [ebx+8] ds:0023:00000008=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  ehshell.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 81cb290c to 81c96968

STACK_TEXT:  
8efd8be4 81cb290c 8467cef0 8423a440 8efd8ce4 nt!MiMapViewOfDataSection+0x105
8efd8c58 81cc31b1 8423a440 8efd8ce4 00000000 nt!MiMapViewOfSection+0x251
8efd8c88 81cc30dc 919a02a8 8423a440 8efd8ce4 nt!MmMapViewOfSection+0x2a
8efd8d04 81a8742a 0000035c ffffffff 1008fb18 nt!NtMapViewOfSection+0x204
8efd8d04 773164f4 0000035c ffffffff 1008fb18 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
1008fb04 00000000 00000000 00000000 00000000 0x773164f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiMapViewOfDataSection+105
81c96968 8b4308          mov     eax,dword ptr [ebx+8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiMapViewOfDataSection+105

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x8E_nt!MiMapViewOfDataSection+105

BUCKET_ID:  0x8E_nt!MiMapViewOfDataSection+105

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

1: kd> .trap 0xffffffff8efd8b1c
ErrCode = 00000000
eax=00000001 ebx=00000000 ecx=8efd8c0c edx=00000000 esi=00000000 edi=00000000
eip=81c96968 esp=8efd8b90 ebp=8efd8be4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MiMapViewOfDataSection+0x105:
81c96968 8b4308          mov     eax,dword ptr [ebx+8] ds:0023:00000008=????????

http://www.corsair.com/_datasheets/TWIN2X2048-6400.pdf

Your RAM VDimm (voltage) should be set to 1.9v. Currently, it is set to 1.8v if it's default. Make this change and bsod will probably go away. Ensure correct latency timings too.

Thank you torrentg for that lightning fast reply.

I have increased the RAM voltage by 0.1v in the BIOS, but not sure how I go about ensuring the latency is correct.

I have used the WIN7 facility and also Memtest and they found no memory fault though I gather this isn't infallible.

From what you say I am getting the feeling my problems are hardware related and seeing they are intermittent I'm thinking they will be hard to diagnose? It may be time for an HTPC update.

I think your problem is fixed. If you have bsod, let us know and then we could explain to you how to set memory timings correctly.

Enjoy the machine.

I hope so as I don't really want to get a new one when most of the time the current one does the job well.

Thanks again for you help.

Unfortunately another BSOD 2 hrs. or so after increasing the memory voltage. I'm not sure if the error is as before because the reliability monitor hasn't given me any information this time.

So I'm posting the dmp file again if you could please have a look at it. Thanks.

Go into bios and change the settings to this:

CAS# Latency (CL) = 5

RAS# to CAS# (Trcd) = 5

RAS# Precharge (Trp) = 5

tRAS = 18

Do this in the same place (most likely) where you set the voltage. Let us know how it goes.

My BIOS does not seem to have any of those settings. There are very few options to change the memory. Thanks again for the quick reply.

http://america.giga-byte.com/FileLis...283.3%29_e.pdf

Look at page 47 about timings. Set to option 2.

You are really going beyond the call of duty to do all this for me!

I had a look at the manual but missed that part. So I have set the BIOS to option2. Incidentally there was yet another BSOD while I was reading your last reply.

I have to leave the HTPC now and will check later if anything has changed. Thanks again