[MacCybex]

Hi!
I receive non-constant BSODs and hang-ups on my computer. Mostly when I play Counter Strike Source or when I play HD
video. Sometimes when just play video or audio (non-HD) or copy files.
Here is the information about my system (tell if you need more).
I have tested RAM with Memtest86+ and Memory diagnostic from Microsoft and none have showed anything. I am pretty
much sure it is software problem just can't find which one. Also I had a similar thing started some time ago on my
second PC, but it wasn't modified physically at all. Maybe it is DirectX 9.0c or ForceWare, but I have tried many
ForceWare versions and also have tried another Windows XP SP2 (integrated) and the result was same.
Systems specifications:
AMD Athlon 4400+
Abit KN9 Ultra (Latest BIOS)
2GB RAM DDR2-800MHz Apacer AM1
MSI GeForce 7600GT (heatpipes+ 8 cm cooler) (Latest BIOS)
Seagate Barracuda 7200.10, 400GB, 16MB, SATAII
Fortron Blue Storm II 500W, 24pin, 12cm FAN
Nec 2500A IDE DVD-RW
Logitech 3200 combo (mouse + keyboard)
Temperatures (min-max):
System: 30-32 C
CPU: 35-45 C
Video: 48-65 C
HDD: 32-34 C
Installed software:
Windows XP ServicePack2 (separately installed)(build 2600)
For MB
Ethernet Driver MCP55 (v55.21) "WHQL"
Network Management Tools MCP55 (v55.23)
SMBus Driver (v4.52) "WHQL"
Installer (v5.05)
WinXP IDE SataRAID Driver (v6.54) "WHQL"
WinXP IDE SataIDE Driver (v6.54) "WHQL"
WinXP RAIDTOOL Application (v6.54)
For videocard:
ForceWare 91.47
Auido:
Realtek High Definition Audio System Software Ver:R1.72
Mouse and Keyboard
Logitech SetPoint 4.00.121
DirectX 9.0c (was with Nero 7)

I have posted the dump files below.

[MacCybex]

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

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: C:\WINDOWS
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Aug 10 23:47:56.468 2007 (GMT+3)
System Uptime: 0 days 0:07:35.171
WARNING: Process directory table base 0A4B8020 doesn't match CR3 00732000
WARNING: Process directory table base 0A4B8020 doesn't match CR3 00732000
Loading Kernel Symbols
.................................................. .................................................. ......................
Loading User Symbols
Loading unloaded module list
................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, bab38d70, 0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+d0 )
Followup: MachineOwner
---------
1: 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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: bab38d70
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------

BUGCHECK_STR: 0x7f_8
TSS: 00000028 -- (.tss 28)
eax=00000000 ebx=bacdd0d4 ecx=ba52b3ac edx=89845008 esi=bacdf950 edi=89e3fcdc
eip=8051ead2 esp=bacdd000 ebp=bacdd014 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!MmAccessFault+0x2:
8051ead2 55 push ebp
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
TRAP_FRAME: bacdd29c -- (.trap ffffffffbacdd29c)
ErrCode = 00000009
eax=89e3fc98 ebx=bacdd434 ecx=ba52b3ac edx=89845008 esi=bacdf950 edi=89e3fcdc
eip=8051eae5 esp=bacdd310 ebp=bacdd35c 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!MmAccessFault+0x15:
8051eae5 8b4044 mov eax,dword ptr [eax+44h] ds:0023:89e3fcdc=89e40830
Resetting default scope
LAST_CONTROL_TRANSFER: from 80543568 to 8051ead2
STACK_TEXT:
bacdcffc 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x2
bacdcffc 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdd0d4 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdd0d4 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdd1ac 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdd1ac 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdd284 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdd284 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdd35c 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdd35c 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdd434 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdd434 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdd50c 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdd50c 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdd5e4 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdd5e4 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdd6bc 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdd6bc 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdd794 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdd794 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdd86c 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdd86c 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdd944 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdd944 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdda1c 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdda1c 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacddaf4 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacddaf4 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacddbcc 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacddbcc 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacddca4 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacddca4 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacddd7c 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacddd7c 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdde54 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdde54 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacddf2c 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacddf2c 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde004 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde004 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde0dc 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde0dc 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde1b4 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde1b4 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde28c 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde28c 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde364 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde364 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde43c 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde43c 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde514 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde514 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde5ec 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde5ec 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde6c4 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde6c4 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde79c 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde79c 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde874 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde874 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacde94c 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacde94c 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdea24 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdea24 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdeafc 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdeafc 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdebd4 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdebd4 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdecac 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdecac 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacded84 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacded84 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdee5c 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15
bacdee5c 8051eae5 00000000 89e3fcdc 00000000 nt!KiTrap0E+0xd0
bacdef34 80543568 00000000 89e3fcdc 00000000 nt!MmAccessFault+0x15

STACK_COMMAND: .tss 0x28 ; kb
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
FOLLOWUP_NAME: MachineOwner
DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0d
FOLLOWUP_IP:
nt!KiTrap0E+d0
80543568 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiTrap0E+d0
FAILURE_BUCKET_ID: TRAP_FRAME_RECURSION
BUCKET_ID: TRAP_FRAME_RECURSION
Followup: MachineOwner
---------
1: kd> lmvm nt
start end module name
804d7000 806e2000 nt (pdb symbols) C:\WINDOWS\Symbols\exe\ntkrpamp.pdb
Loaded symbol image file: ntkrpamp.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Wed Aug 04 08:58:37 2004 (41107B0D)
CheckSum: 001F22D9
ImageSize: 0020B000
File version: 5.1.2600.2180
Product version: 5.1.2600.2180
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 5.1.2600.2180
FileVersion: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.

[MacCybex]

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

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: C:\WINDOWS
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Aug 11 10:33:03.015 2007 (GMT+3)
System Uptime: 0 days 0:08:02.581
WARNING: Process directory table base 0A4B83C0 doesn't match CR3 00732000
WARNING: Process directory table base 0A4B83C0 doesn't match CR3 00732000
Loading Kernel Symbols
.................................................. .................................................. ........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
Loading unloaded module list
..............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, bab38d70, 0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiTrap08+48 )
Followup: MachineOwner
---------
1: 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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: bab38d70
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------

BUGCHECK_STR: 0x7f_8
TSS: 00000028 -- (.tss 28)
eax=0cdc0010 ebx=00000020 ecx=24462954 edx=0cdbd000 esi=24462954 edi=00000020
eip=25095a30 esp=0012df20 ebp=00000020 iopl=0 nv up ei pl nz ac pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00210217
001b:25095a30 ?? ???
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: hl2.exe
LAST_CONTROL_TRANSFER: from 25095a30 to 80542541
STACK_TEXT:
00000000 25095a30 00000000 00000000 00000000 nt!KiTrap08+0x48
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000020 00000000 00000000 00000000 00000000 0x25095a30

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap08+48
80542541 ebee jmp nt!KiTrap08+0x38 (80542531)
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiTrap08+48
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0d
FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+48
BUCKET_ID: 0x7f_8_nt!KiTrap08+48
Followup: MachineOwner
---------
1: kd> lmvm nt
start end module name
804d7000 806e2000 nt (pdb symbols) C:\WINDOWS\Symbols\exe\ntkrpamp.pdb
Loaded symbol image file: ntkrpamp.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Wed Aug 04 08:58:37 2004 (41107B0D)
CheckSum: 001F22D9
ImageSize: 0020B000
File version: 5.1.2600.2180
Product version: 5.1.2600.2180
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 5.1.2600.2180
FileVersion: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.

[temeteus82]

Hi there and welcome to DriverHeaven.

I got quick questions for you. What AV software you are running? I've heard that if you are using older Norton Anti-virus it may cause this BSOD.

[MacCybex]

You mean anti virus?
I use none of them, only WinXP built-in firewall.
So it is not the problem in my case.

[Tipstaff]

As soon as I saw these two listings, 0x00000008 Double Fault, and UNEXPECTED_KERNEL_MODE_TRAP, my immediate thought is you are having hardware failure. The first one I mentioned, 0x00000008, points to some sort of hardware falilure, usually bad ram in 90% of the cases.

Let's break this down:

- I would assume that you are running with 2 sticks of 1GB DDR2 (based on the type of ram you mentioned you have. If that's the case you may want to try pulling one stick out, and see if crashes again. If it does, try the other stick. If it doesn't, again, try the other stick. Even though Memtest came back with an all clear, the ram may still be a problem.

- Are you overclocking, or pushing the timings on your ram? If so you should bring the system back down to it's default settings, or at the very least relax some of the timings on the ram. However, if you aren't overclocking you should check the bios to see if the board itself is pushing the ram timings. You may need to set the timings manually to what the manufacturer has set it for. If memory serves that particular ram has a CAS latency of CL5 (most likely 5-5-5-15 or 18), and runs at 1.8v. Check the bios to see if the board is setting the ram at the same timings, and not something faster.

- How is your pagefile setup? Sometimes that 0x00000008 stop error can occur if the pagefile is corrupt, but not because of Windows itself, but do to a bad hard drive. You may want to reset the pagefile to let Windows manage the size, as well as scan your hard drive for errors.

[MacCybex]

Yes, I have 2 x 1 GB DDR2 800 MHz memory sticks in a DualChannel mode. Timings are like these Auto-5-5-18 and voltage is 1.80.
I have not overclocked any of the components and the cooling of the system is very good.
I dont think this is a hardware problem because during the tests and installation of Windows everything is always ok, and I had similar thins started with my second PC after it has been working flawlesly for few years.
But I think I will try with the separate sticks as I have tried so many things and got tired of it all.
About the pagefile: I have tried few Windows versions and the result was the same.

[Dyre Straits]

How long did you allow MemTest86+ to run? Sometimes it needs to run overnight or while you're away at work to actually get any errors. It won't always generate errors within a few minutes.

[MacCybex]

I had like an 8 passes of Memtest86+ and about as much or more of Microsoft Diagnostic tool.
I tried to work with one memory stck and to change their positions, but it doesn't help to solve the problem.
I still think it is the software problem (driver or a programm).
I get BSOD and hang-ups more often when I play videos (with different players and different codecs, like xvid, h264).

[MacCybex]

Here is the last dump I got after the BSOD:
//////////////////////////////////////////////////////////////////////////////////////////////

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

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: C:\WINDOWS
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Aug 14 19:49:32.359 2007 (GMT+3)
System Uptime: 0 days 2:41:12.935
Loading Kernel Symbols
.................................................. .................................................. ......................
Loading User Symbols
Loading unloaded module list
.....................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 0}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for NVNRM.SYS -
Probably caused by : NVNRM.SYS ( NVNRM!DllInitialize+49bf )
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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory
Debugging Details:
------------------

WRITE_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
+0
00000000 ?? ???
PROCESS_NAME: Idle
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: bacd3c44 -- (.trap ffffffffbacd3c44)
ErrCode = 00000010
eax=8885a768 ebx=00000000 ecx=b9a1a7a0 edx=bb1ebc49 esi=b9a19ea0 edi=88c53964
eip=00000000 esp=bacd3cb8 ebp=bacd3cd4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 00000000 to 805436d0
STACK_TEXT:
bacd3c44 00000000 badb0d00 bb1ebc49 804fb5d3 nt!KiTrap0E+0x238
WARNING: Frame IP not in any known module. Following frames may be wrong.
bacd3cb4 b99a4125 00000000 8885a768 00000001 0x0
bacd3cd4 b99a4b2c 00000001 88c55d14 00000000 NVNRM!DllInitialize+0x49bf
bacd3d10 b99a73c0 b9a19ea0 bab38000 8055b0a0 NVNRM!DllInitialize+0x53c6
bacd3d28 80544e5f 88c55cc4 00000000 00000000 NVNRM!DllInitialize+0x7c5a
bacd3d50 80544d44 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
bacd3d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

STACK_COMMAND: kb
FOLLOWUP_IP:
NVNRM!DllInitialize+49bf
b99a4125 8b8660060000 mov eax,dword ptr [esi+660h]
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NVNRM
IMAGE_NAME: NVNRM.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4421c05b
SYMBOL_NAME: NVNRM!DllInitialize+49bf
FAILURE_BUCKET_ID: 0xD1_W_NVNRM!DllInitialize+49bf
BUCKET_ID: 0xD1_W_NVNRM!DllInitialize+49bf
Followup: MachineOwner
---------
1: kd> lmvm NVNRM
start end module name
b9997000 b9a9bf00 NVNRM (export symbols) NVNRM.SYS
Loaded symbol image file: NVNRM.SYS
Image path: \SystemRoot\system32\DRIVERS\NVNRM.SYS
Image name: NVNRM.SYS
Timestamp: Wed Mar 22 23:23:39 2006 (4421C05B)
CheckSum: 00110B22
ImageSize: 00104F00
File version: 5.0.5.5521
Product version: 5.0.5.5521
File flags: 0 (Mask 3F)
File OS: 4 Unknown Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04e2
CompanyName: NVIDIA Corporation
ProductName: NVNRM
InternalName: NVNRM
OriginalFilename: NVNRM.SYS
ProductVersion: 5.00.05.05521
FileVersion: 5.00.05.05521
FileDescription: NVIDIA Network Resource Manager.
LegalCopyright: Copyright © 2001-2007 NVIDIA Corporation

[Dyre Straits]

I know you probably don't want to, but, try loosening up the timings on the RAM. Instead of the stated: AUTO-5-5-18, try 6-6-6-18 and use 2T. In fact, if you're using 1T now, just try changing to 2T without changing the other settings.

[PangingJr]

Originally Posted by MacCybex

Blue screens of death and hang-ups (dump files are posted).

hmm, try again, try running your system hardwares at default speed and voltages, or using system BIOS default settings, but just reset it on things that are necessary for the system to continue operation from booting up, to Windows, and to shutting it down. and then run the memtest overnight again, if an error occurs or system hang/reboot by itself during the memtesting, post back. if no error occur, then perform clean install of your software system, after Windows, at first, don’t install drivers like the Logitech SetPoint, or any device drivers unless the system has a hardware issues and that it needs to be resolved by a driver. and see what happens?

[Yousaif]

This really looks like some kind of BIOS or chipset driver issue. All of the issues I have searched up on teh intarweb about this kind of problem all point back to a BIOS update that wasn't quite right.

Just out of curiosity, what kind of temps does your motherboard show for the CPU, etc?