BSOD recent RAM upgrade; happens mostly at restarts

Hello,

Attached are the dump files. I am not able to generate perform report as it gives an error "The system cannot find the path specified.".

I recently added 2GB RAM to my system (about 1 month ago). BSOD started about 2 weeks ago.

I am running Windows 7 Home Premium 32bit. Original installation on the machine came with Vista. I upgraded using Microsoft upgrade disk. Windows update is set to automatic download and install.

Please help.

Thanks,
Mohit

Code:

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


Loading Dump File [F:\Kingston\BSODDmpFiles\jainmohit\Windows_NT6_BSOD_jcgriff2\020512-49327-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x8321c000 PsLoadedModuleList = 0x833654d0
Debug session time: Sun Feb  5 06:41:30.498 2012 (GMT-7)
System Uptime: 0 days 0:01:51.730
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ff630817, 1c, 8, ff630817}

Probably caused by : amdk8.sys ( amdk8!C1Halt+4 )

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: ff630817, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: ff630817, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 83385848
Unable to read MiSystemVaType memory at 83364e20
 ff630817 

CURRENT_IRQL:  1c

FAULTING_IP: 
+62c3952f0396d9f8
ff630817 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  83343ba8 -- (.trap 0xffffffff83343ba8)
ErrCode = 00000010
eax=8b63ed00 ebx=00000000 ecx=00000000 edx=000000d1 esi=eec83e87 edi=92504bb6
eip=ff630817 esp=83343c1c ebp=83343c28 iopl=0         nv up ei ng nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
ff630817 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from ff630817 to 8325d5fb

FAILED_INSTRUCTION_ADDRESS: 
+62c3952f0396d9f8
ff630817 ??              ???

STACK_TEXT:  
83343ba8 ff630817 badb0d00 000000d1 83343c14 nt!KiTrap0E+0x2cf
WARNING: Frame IP not in any known module. Following frames may be wrong.
83343c18 83630794 00000802 000000d1 83343d20 0xff630817
83343c18 92504bb6 00000802 000000d1 83343d20 hal!HalpHpetClockInterrupt+0x160
83343c98 8329c37f 886494c8 83350380 83346c00 amdk8!C1Halt+0x4
83343d20 83293e0d 00000000 0000000e 00000000 nt!PoIdle+0x524
83343d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd


STACK_COMMAND:  kb

FOLLOWUP_IP: 
amdk8!C1Halt+4
92504bb6 c3              ret

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  amdk8!C1Halt+4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: amdk8

IMAGE_NAME:  amdk8.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf07

FAILURE_BUCKET_ID:  0xD1_CODE_AV_BAD_IP_amdk8!C1Halt+4

BUCKET_ID:  0xD1_CODE_AV_BAD_IP_amdk8!C1Halt+4

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

Please fill out your system specs using System Info - See Your System Specs use steps 1-4 to get the specs and step 5 to fill them out.

If there are any BIOS updates for your system, I would suggest this first since the driver being blamed in the crash is related to your processor. Processors do not fail often, so it is best to do troubleshooting steps to determine other possible causes first. Given the age of your BIOS version,

Code:

BIOS Version/Date	Phoenix Technologies, LTD 5.05, 4/18/2007

this seems like a good place to start.

Also, do you have ZoneAlarm on your system?

Where will I find BIOS updates for this motherboard? I did google with no avail!

Thanks,
Mohit

HP doesn't have great BIOS support, unfortunately. You are stuck with your current version.

Are you running ZoneAlarm?

I checked programs and features in Control Panel, and there is no ZoneAlarm installed

Alright, just wondering because some of your crashes were crashes that often occur with that program, and I saw a driver that may have been associated with ZoneAlarm from Check Point software.

Since your problems occurred shortly after installing new RAM, run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

Hello,

I ran the Memtest86+ tool for 8+ passes and there were no errors detected.
I then ran the Windows Memory Diagnostic tool for extended tests for 5 passes, and that also came out clean. The machine hung up at the Windows boot-up and I saw the results in the Event logs and they say no errors detected.

I am still getting BSOD, more frequently so.

In safe mode, BSOD does not happen. I am hoping this is still a driver issue.

Need your help.

Thanks,
Mohit

An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

Also, upload your latest crash reports using the same method as before. :)

I tried verifier.exe but it would not even allow Windows to start. I kept getting BSOD every time Windows tried to start. It did not give me an option to go into Safe mode.
I had to restore to undo verifier.

I then removed the new RAM stick and all worked fine. I tried switching the new RAM stick with one of the original ones and it still worked fine. I then used the 4th open slot for the remaining memory stick and till now no BSOD. I guess it was the slot issue.

Don't know why Memtest86+ and Windows Memory Diag did not find this out.

Mohit

The memory tests do not always find RAM problems the first time. Sometimes they need to be run multiple times to return errors. If your blue screens happen often enough, we will recommend just swapping out memory or moving it around and running Windows normally to see if it stops the crashes. Only time will tell if it is stable. Do your normal routine for a while and post back how stability is after a few weeks. If you have any crashes before then, report back with the crash report and we will analyze your crashes again.

Best of luck it is stable!