BSOD and Window's Product ID lost...

Hello,

I've been having a few issues with a new home-built computer (start up occurred on 11/25/2010), specifically BSOD's. Initially, the computer would crash due coming out of hibernation. This has been solved by turning off this feature, for now. In addition, a new problem cropped up yesterday. But first, a bit about the computer:

Computer background info:
-OS: Windows 7 Home Premium 64 bit
-OEM version, purchased from Fry's Electronics.
-Motherboard: Gigabyte P55A-UD3
-Chipset: Intel i5-760
-RAM: 8gig Corsair XMS3 1600, matched latency
-HD: Seagate Barracuda 1 Tb 7200 rpm 32 Mb cache
-Video Card: NVidia GTX 460 768 MB

As window's updates have been installed the BSOD occurrence has slowed down until yesterday. Here is a chronological list of what happened:

-Computer was turned on, after being turned off since 12/18 as owner was on travel.
- During the first 15 minutes, two BSOD's occurred.
- After the second BSOD, the virus software registration files had become corrupted and required re-install (Kaspersky).
- After the Kaspersky registration files had been uploaded and the computer restarted, the Windows Product ID had been lost and had to be re-entered.
- Once the ID had been re-entered and accepted, Adobe Premiere fails to open fully: it will open to the main screen, but any further commands results in a software hang and the software has to be closed. This is new and had not occurred prior to the second BSOD on 12/31. Also, Window's media viewer will freeze occasionally while watching videos. Again, this is new and had not occurred prior to the second BSOD on 12/31.

Since this issue has cropped up as of 12/31, windows memory tests have been run to verify RAM and no issues have been detected. Temperature of the CPU is within acceptable limits.

I have attached the mini-dump files that have been generated in the the last month and hope that someone can read them and explain to me how to fix my problems.

Thank you in advance
Joe

CycloneJoe67 said:

Hello,

I've been having a few issues with a new home-built computer (start up occurred on 11/25/2010), specifically BSOD's. Initially, the computer would crash due coming out of hibernation. This has been solved by turning off this feature, for now. In addition, a new problem cropped up yesterday. But first, a bit about the computer:

Computer background info:
-OS: Windows 7 Home Premium 64 bit
-OEM version, purchased from Fry's Electronics.
-Motherboard: Gigabyte P55A-UD3
-Chipset: Intel i5-760
-RAM: 8gig Corsair XMS3 1600, matched latency
-HD: Seagate Barracuda 1 Tb 7200 rpm 32 Mb cache
-Video Card: NVidia GTX 460 768 MB

As window's updates have been installed the BSOD occurrence has slowed down until yesterday. Here is a chronological list of what happened:

-Computer was turned on, after being turned off since 12/18 as owner was on travel.
- During the first 15 minutes, two BSOD's occurred.
- After the second BSOD, the virus software registration files had become corrupted and required re-install (Kaspersky).
- After the Kaspersky registration files had been uploaded and the computer restarted, the Windows Product ID had been lost and had to be re-entered.
- Once the ID had been re-entered and accepted, Adobe Premiere fails to open fully: it will open to the main screen, but any further commands results in a software hang and the software has to be closed. This is new and had not occurred prior to the second BSOD on 12/31. Also, Window's media viewer will freeze occasionally while watching videos. Again, this is new and had not occurred prior to the second BSOD on 12/31.

Since this issue has cropped up as of 12/31, windows memory tests have been run to verify RAM and no issues have been detected. Temperature of the CPU is within acceptable limits.

I have attached the mini-dump files that have been generated in the the last month and hope that someone can read them and explain to me how to fix my problems.

Thank you in advance
Joe

Hi Joe and welcome

these were all caused by memory corruption probably because of Kaspersky

I would
1-Remove Kaspersky and replace with Miclsoft Security essentials.

http://support.kaspersky.com/downloa...vremover10.zip

http://www.microsoft.com/security_essentials/

2- run memtest to test your memory

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

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\New folder\123110-25240-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e66000 PsLoadedModuleList = 0xfffff800`030a3e50
Debug session time: Fri Dec 31 18:41:38.605 2010 (GMT-5)
System Uptime: 0 days 0:06:40.796
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 0, 0, 0}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000000000, page frame number
Arg3: 0000000000000000, current page state
Arg4: 0000000000000000, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f6638c to fffff80002ed6740

STACK_TEXT:  
fffff880`05f3d3a8 fffff800`02f6638c : 00000000`0000004e 00000000`00000099 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`05f3d3b0 fffff800`02ec0ac4 : 00000000`00000000 fffffa80`01b4f380 00000000`00002001 80000000`91a68882 : nt!MiBadShareCount+0x4c
fffff880`05f3d3f0 fffff800`031c760f : fffffa80`0a482e40 00000000`00000000 fffffa80`0a482e40 00000000`00002001 : nt!MiDeleteSegmentPages+0x404
fffff880`05f3d4a0 fffff800`02edb8b4 : 00000000`00000000 00000000`00000001 fffffa80`06729a30 fffffa80`06729a30 : nt!MiSegmentDelete+0x7b
fffff880`05f3d4e0 fffff960`000c5550 : 00000000`00000001 fffffa80`08d88270 fffff900`c1fadcd0 00000000`000005a6 : nt!ObfDereferenceObject+0xd4
fffff880`05f3d540 00000000`00000001 : fffffa80`08d88270 fffff900`c1fadcd0 00000000`000005a6 00000000`00000005 : win32k+0xc5550
fffff880`05f3d548 fffffa80`08d88270 : fffff900`c1fadcd0 00000000`000005a6 00000000`00000005 00000000`00000000 : 0x1
fffff880`05f3d550 fffff900`c1fadcd0 : 00000000`000005a6 00000000`00000005 00000000`00000000 00000000`00000000 : 0xfffffa80`08d88270
fffff880`05f3d558 00000000`000005a6 : 00000000`00000005 00000000`00000000 00000000`00000000 fffff8a0`024e2990 : 0xfffff900`c1fadcd0
fffff880`05f3d560 00000000`00000005 : 00000000`00000000 00000000`00000000 fffff8a0`024e2990 00000000`00000000 : 0x5a6
fffff880`05f3d568 00000000`00000000 : 00000000`00000000 fffff8a0`024e2990 00000000`00000000 00000000`00000000 : 0x5


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02f6638c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

Thank you, I'll try it and get back to you.

Joe

I have run Memtest as requested. After running 9 passes all night long, no issues were detected. I ran it once more and again no issues. I have removed Kasperskey, with no changes as a result.

I have attached the latest mini-dump files since my last message.

Also, Window's firewall no longer starts, and internet connections with the computer are not possible. I have tracked the issue thus far down to the base filtering engine failing to start, but thats as far as I've made it.

Could these issues be connected thus far?

I'm interested to see what the latest mini-dump files reveal, if anything.

Thanks
Joe

Any thoughts, anyone?

After doing all of the items stated by the form support, plus doing a repair install of Windows 7 (which corrected the Windows registry errors), I was still getting BSOD's. I investigated the RAM further, wondering if there isnt some flaw with its settings.

Come to find out, the BIOS voltage setting for the RAM was set at 1.5V. According to Corsair's website, the voltage should be increased until the system is stable, or you exceed 1.65V. Corsair's explaination is that the memory voltage controller needs extra voltage when all of the DIM slots are being used. After reading others posts regarding increasing the voltage I figured I should give it a go. Voila! No more BSOD's. Also, the RAM speed was originally being set at 1333 MHz by the BIOS, which I changed to 1600 MHz. The system has been stable and without issue.

Please mark this thread as closed.

Thank you
Joe