Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD for the pass 3 months

13 Sep 2010   #1

Windows 7 Professional 32-bit (6.1, Build 7600)
 
 
Random BSOD for the pass 3 months

Hi all,

I am posting on behalf of my friend. He started getting random bsod soon after he bought the new PC (Its a diy PC).

Problem:

- Random bsod

- Pressing the play button of a media player from stream side like YouTube will also cause bsod.

- Recently, sometimes when exiting game(eg. Warcraft 3) or alt-tabbing out from the game will cause bsod too.


Specifications:

- Windows 7 Professional
- 32-bit
- Downloaded it for free as student; I think its considered a full version
- Age of hardware is about 3 months
- Installed the OS once only

My friend and I appreciate everyone's help. Thanks!

My System SpecsSystem Spec
.

14 Sep 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by cwd90 View Post
Hi all,

I am posting on behalf of my friend. He started getting random bsod soon after he bought the new PC (Its a diy PC).

Problem:

- Random bsod

- Pressing the play button of a media player from stream side like YouTube will also cause bsod.

- Recently, sometimes when exiting game(eg. Warcraft 3) or alt-tabbing out from the game will cause bsod too.


Specifications:

- Windows 7 Professional
- 32-bit
- Downloaded it for free as student; I think its considered a full version
- Age of hardware is about 3 months
- Installed the OS once only

My friend and I appreciate everyone's help. Thanks!


Both of these were caused by memory management. Your friends Image of win 7 I think is suspect as that standard MS symbols are wrong for the critical system files.

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.

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\Windows_NT6_BSOD_jcgriff2\091310-16567-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: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c1c000 PsLoadedModuleList = 0x82d64810
Debug session time: Mon Sep 13 09:08:56.975 2010 (GMT-4)
System Uptime: 0 days 1:46:56.333
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: 67fc1b94, Virtual address for the attempted write.
Arg2: 2d2c9005, PTE contents.
Arg3: a086bba4, (reserved)
Arg4: 0000000a, (reserved)

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 82c1c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82c62638 to 82ca1903

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
a086bb8c 82c62638 00000001 67fc1b94 00000000 nt!MmDisableModifiedWriteOfSection+0x15f0
a086bbb0 82c83a92 a086bbd8 a086bc0c 00000000 nt!Kei386EoiHelper+0x27e0
a086bc3c 82ca84df 000101fc 87abb9f8 000000fc nt!KiDispatchInterrupt+0xe2
a086bca0 82ca38ff 000000fc 00000002 0a746000 nt!KeRevertToUserGroupAffinityThread+0xa62
a086bd1c 82c62638 00000001 0a746000 00000001 nt!MmDisableModifiedWriteOfSection+0x35ec
a086bd34 77044805 badb0d00 00000002 00000000 nt!Kei386EoiHelper+0x27e0
a086bd38 badb0d00 00000002 00000000 00000000 0x77044805
a086bd3c 00000000 00000000 00000000 00000000 0xbadb0d00


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmDisableModifiedWriteOfSection+15f0
82ca1903 cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmDisableModifiedWriteOfSection+15f0

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  memory_corruption

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------
My System SpecsSystem Spec
14 Sep 2010   #3

Windows 7 Professional 32-bit (6.1, Build 7600)
 
 

Hi zigzag3143,

Thanks for the reply, I will let you know the result again after he had done the test.
My System SpecsSystem Spec
.


15 Sep 2010   #4

Windows 7 Professional 32-bit (6.1, Build 7600)
 
 

Hi zigzag3143,

My friend has gotten 5 passes for the test
My System SpecsSystem Spec
Reply

 Random BSOD for the pass 3 months




Thread Tools



Similar help and support threads for2: Random BSOD for the pass 3 months
Thread Forum
Random BSODs been happening every 2-3 days or so, for 6 months. BSOD Help and Support
Random BSOD over last few months, tried debug on my own w/o luck BSOD Help and Support
Been getting random BSOD for months BSOD Help and Support
Random BSOD about a four months now BSOD Help and Support
Two Months of random, yet consistent, BSOD's BSOD Help and Support
Random [BSOD] for a few months BSOD Help and Support
Solved random BSOD, restarts for the past 2 months BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:23 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33