BSOD Restarting Randomly

[rpgfailure99]

Hi hopefully someone can help me. =)
I have experienced BSOD on Bccode 1a,4e, 50, 7f, 24, 7f, 7f.
It just restart my computer randomly.
I have a MSI Gx660R with Windows 7 64bit OEM installed.
I just got this laptop about a week ago and have reinstalled with a clean install of windows 7 once.
I have the BSOD Dump & System File Collection app & System Health Report attached in zip file.
I also have an attachment of DxDiag if that helps.
Thank you so much for helping.
I really appreciate it if you can help.

 

[zigzag3143]

Hi hopefully someone can help me. =)
I have experienced BSOD on Bccode 1a,4e, 50, 7f, 24, 7f, 7f.
It just restart my computer randomly.
I have a MSI Gx660R with Windows 7 64bit OEM installed.
I just got this laptop about a week ago and have reinstalled with a clean install of windows 7 once.
I have the BSOD Dump & System File Collection app & System Health Report attached in zip file.
I also have an attachment of DxDiag if that helps.
Thank you so much for helping.
I really appreciate it if you can help.

Most of these were directly caused by memory corruption and a yet as un-named driver.

I would

1- run a memory test to make sure there isnt a hardware problem

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.

2-run a system file check to verify your system

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

3- run driver verifier to find which driver/drivers are causing you grief

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Let us know the results from the report at the end.

Ken



Analysis

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\090910-18548-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`03053e50
Debug session time: Thu Sep  9 14:54:42.878 2010 (GMT-4)
System Uptime: 0 days 0:10:34.955
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 1027c4, 0, 102844}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

4: 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: 00000000001027c4, page frame number
Arg3: 0000000000000000, current page state
Arg4: 0000000000102844, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f1638c to fffff80002e86740

STACK_TEXT:  
fffff880`0b861f28 fffff800`02f1638c : 00000000`0000004e 00000000`00000099 00000000`001027c4 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b861f30 fffff800`02ef89f7 : 00000000`00000000 fffff680`000021c0 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0b861f70 fffff800`02e5ac23 : fffffa80`0ab66770 fffff700`00003496 0000007f`fffffff8 fffff8a0`00200868 : nt! ?? ::FNODOBFM::`string'+0x3223e
fffff880`0b862000 fffff800`02e5968a : fffffa80`0ab66770 fffffa80`00000f12 fffff8a0`00002cdc fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0b8628b0 fffff800`0316bdcf : fffff8a0`03caba70 fffff880`0b862c20 00000000`00000000 fffffa80`0a26eb60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0b862900 fffff800`03144635 : 00000000`000000ff 00000000`00000001 000007ff`fffa0000 fffffa80`05347b60 : nt!PspExitThread+0x92f
fffff880`0b8629c0 fffff800`02e631db : fffffa80`0ab66770 fffff8a0`06ce9d00 00000000`00000000 fffff800`0312ba53 : nt!PsExitSpecialApc+0x1d
fffff880`0b8629f0 fffff800`02e63620 : 00000000`01a3cd80 fffff880`0b862a70 fffff800`0314474c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0b862a70 fffff800`02e85a37 : fffffa80`0a26eb60 00000000`01a3cc68 fffff880`0b862bc8 fffff800`0319c414 : nt!KiInitiateUserApc+0x70
fffff880`0b862bb0 00000000`772e030a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`01a3cc48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772e030a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02f1638c 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
---------

 

[Jonathan_King]

I suspect ZoneAlarm is the cause here.

Event[143]:
  Log Name: System
  Source: EventLog
  Date: 2010-09-11T20:06:17.000
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: 4Christ-PC
  Description: 
The previous system shutdown at 7:54:59 PM on ?9/?11/?2010 was unexpected.

Event[144]:
  Log Name: System
  Source: Microsoft-Windows-FilterManager
  Date: 2010-09-11T20:06:09.022
  Event ID: 6
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: 4Christ-PC
  Description: 
File System Filter 'Vsdatant' (6.1, ?2010?-?05?-?09T09:28:58.000000000Z) has successfully loaded and registered with Filter Manager.

Please remove it with this tool: http://download.zonealarm.com/bin/free/support/cpes_clean.exe

Reset the Windows firewall. Open an elevated command prompt and enter netsh advfirewall reset.

 

[rpgfailure99]

Thank you guys for helping me.
I am currently about to try the memoryx86 test.
I was thinking it was a possibility of being a zone alarm, but I had BSOD before zone alarm so I don't think that is the cause.
I was thinking would it be my blue ray drive?
For some reason I think my computer thinks it is a regular optical drive.
I would run the driver verifier tomorrow.
Thanks so much for replying.

 

[rpgfailure99]

Hi for the memoryx86 test, I don't really understand it.
Do I download Pre-Compiled Bootable ISO (.zip)?
Also I have imgburn and so do I burn the entire folder that I get with the boot security catalog file and memtest iso file?
Do I use them as a root or leave the boot folder there?
Sorry I don't really understand this burn to image thing.
Also when you mean boot do you mean put cd in and boot it before windows start or just during windows.
Thanks.
Sorry for all these questions.

 

[Jonathan_King]

Here is a more detailed tutorial on Memtest. This should resolve all your questions: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

This sounds like a hardware issue, honestly.

Test temps: SpeedFan - Access temperature sensor in your computer

Test hard drive: HD Diagnostic

 

[rpgfailure99]

Thanks Johnathan King for responding.
Yea I kind of think its a hardware issue.
Well I did this run driver verifier to find which driver/drivers are causing you grief thing.
So when I restarted the computer I can't load windows now and I get this BSOD
Stop: C000021a [Fatal System Error]
The Session Manager Initialization system process terminated unexpectedly with a status of 0xc0000001 (0x00000000 0x00000000]
The system has been shut down.
So I turn on the computer and I get this windows repair thing and they say Startup Repair cannot repair this computer automatically.
Problem signature:
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknwon
Problem Signature 04: 21200764
Problem Signature 05: AutoFailover
Problem Signature 06: 2
Problem Signature 07: NoRootCause
OS Version: 6.1.7600.2.0.256.1
Local ID: 1033

Hopefully you guys can help.
Appreciate your support in getting me this far.

 

[rpgfailure99]

Alright this is confusing.
After that I got that blue screen twice, the third time I turned on my computer it disappeared.
I'm quite confused...

 

[Jonathan_King]

Now try following these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[rpgfailure99]

Thanks a lot for responding Johnathan King.
Here is the new BSOD stuff attached in zip file.
Hopefully you can help as now after the 3- run driver verifier to find which driver/drivers are causing you grief, my computer seems a little slower and the windows seven gadgets on the desktop keeps glitching.
Appreciate your responses Johnathan King.

 

[Jonathan_King]

Try removing ZoneAlarm, and see what happens.

Also, none of the latest dumps were verifier-enabled. Try enabling it again, and keep rebooting until you can log into Windows. It may take several tries, call it 7.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 20:17:35.818 2010 (UTC - 4:00)
System Uptime: 0 days 2:38:42.880
BugCheck 7F, {8, 80050031, 6f8, fffff80002e8fec0}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 14:33:31.295 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:28.341
BugCheck 1A, {41790, fffffa8001b04ce0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 19:09:22.365 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:08.442
BugCheck 1A, {41284, 26ef001, 913, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[rpgfailure99]

Alright so I tried getting rid of zone alarm and I get BSOD
Here is the thing attached.
Also I attached photo of the blue screen to show the stop code and this weird realtek media failure I get before anything starts.
My computer runs fine, but there is this screen before windows and was wondering what it meant.
I took a picture of it with my phone.
Also once again, thanks a lot for trying to help me.

 

[rpgfailure99]

Okay so I got that blue screen that I posted in the previous post once again.
Also i did the verify thing with another BSOD happening 6 or more. I lost account around then. =/
Umm it would happen write after I see the windows logo.
So I ran the BSOD.exe program again and have posted the new reports with the new perf report too.
Sorry about all this trouble.
Thank you for helping me.
For some reason I really think it is a hardware issue.

 

[Jonathan_King]

vsdatant.sys is the ZoneAlarm driver. Try running this tool again: http://download.zonealarm.com/bin/free/support/cpes_clean.exe