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: Win 7 Multiple, different BSOD


09 Feb 2011   #1

Window Home Premium 64 bit
 
 
Win 7 Multiple, different BSOD

I purchased a HP Pavilion dv6t customizable notebook, about a month ago, and I started to get BSOD's while playing graphic heavy games. So far, I had a 1000007e, 0x24, 0x4e, and 0x19 BSODs, most recent to older (all attached). I have made sure that all my drivers were up to date, and had run Windows Memory Diagnostic tests as well. BSOD hasn't occured anytime other than playing games, though I think might be because all my other activities are not quite as demanding on the computer.

System Information:

Window 7 Home Premium 64 bit
Intel Core i3-370M @ 2.4 GHz
Hitachi 500 GB HDD
6 GB RAM
Integrated Graphics


My System SpecsSystem Spec
.

09 Feb 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by nochgo View Post
I purchased a HP Pavilion dv6t customizable notebook, about a month ago, and I started to get BSOD's while playing graphic heavy games. So far, I had a 1000007e, 0x24, 0x4e, and 0x19 BSODs, most recent to older (all attached). I have made sure that all my drivers were up to date, and had run Windows Memory Diagnostic tests as well. BSOD hasn't occured anytime other than playing games, though I think might be because all my other activities are not quite as demanding on the computer.

System Information:

Window 7 Home Premium 64 bit
Intel Core i3-370M @ 2.4 GHz
Hitachi 500 GB HDD
6 GB RAM
Integrated Graphics
Three of 4 were caused by the directx component of your video driver I would re-install it using these directions.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Second I would remove avast and replace with micro soft security essentials

http://files.avast.com/files/eng/aswclear5.exe

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


Third-- Memory corruption. Run memtest as indicated to test yours.
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\020611-17784-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e98e50
Debug session time: Sun Feb  6 17:05:23.351 2011 (GMT-5)
System Uptime: 0 days 3:04:53.616
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, 11485d, 2, 11485b}

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: 000000000011485d, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000011485b, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  HPWA_Main.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d5b38c to fffff80002ccb740

STACK_TEXT:  
fffff880`0c058f98 fffff800`02d5b38c : 00000000`0000004e 00000000`00000099 00000000`0011485d 00000000`00000002 : nt!KeBugCheckEx
fffff880`0c058fa0 fffff800`02d3d9e5 : 00000000`00000000 fffff680`000dec20 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0c058fe0 fffff800`02c9fc23 : fffffa80`05ba6060 fffff700`00003302 0000007f`fffffff8 fffff8a0`03fbb6b0 : nt! ?? ::FNODOBFM::`string'+0x3222c
fffff880`0c059070 fffff800`02c9e68a : fffffa80`05ba6060 fffffa80`00000000 fffff8a0`00000ebe fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0c059920 fffff800`02fb0dcf : fffff8a0`046e8060 fffff880`0c059c20 00000000`00000000 fffffa80`05bf13b0 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0c059970 fffff800`02f89635 : 00000000`c0000005 00000000`c0000001 000007ff`ffefc000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`0c059a30 fffff800`02ca81db : 00000000`00000100 fffffa80`05bf1470 00000000`00000001 fffff800`02cd2b9d : nt!PsExitSpecialApc+0x1d
fffff880`0c059a60 fffff800`02ca8620 : 00000000`00000000 fffff880`0c059ae0 fffff800`02f8974c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0c059ae0 fffff800`02ccaa37 : fffffa80`05bf13b0 00000000`ffffffff 00000000`00000000 fffffa80`0b77e2b0 : nt!KiInitiateUserApc+0x70
fffff880`0c059c20 00000000`77b5fd9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`1c8dfb48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b5fd9a


STACK_COMMAND:  kb

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

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: 000000000011485d, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000011485b, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  HPWA_Main.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d5b38c to fffff80002ccb740

STACK_TEXT:  
fffff880`0c058f98 fffff800`02d5b38c : 00000000`0000004e 00000000`00000099 00000000`0011485d 00000000`00000002 : nt!KeBugCheckEx
fffff880`0c058fa0 fffff800`02d3d9e5 : 00000000`00000000 fffff680`000dec20 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0c058fe0 fffff800`02c9fc23 : fffffa80`05ba6060 fffff700`00003302 0000007f`fffffff8 fffff8a0`03fbb6b0 : nt! ?? ::FNODOBFM::`string'+0x3222c
fffff880`0c059070 fffff800`02c9e68a : fffffa80`05ba6060 fffffa80`00000000 fffff8a0`00000ebe fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0c059920 fffff800`02fb0dcf : fffff8a0`046e8060 fffff880`0c059c20 00000000`00000000 fffffa80`05bf13b0 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0c059970 fffff800`02f89635 : 00000000`c0000005 00000000`c0000001 000007ff`ffefc000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`0c059a30 fffff800`02ca81db : 00000000`00000100 fffffa80`05bf1470 00000000`00000001 fffff800`02cd2b9d : nt!PsExitSpecialApc+0x1d
fffff880`0c059a60 fffff800`02ca8620 : 00000000`00000000 fffff880`0c059ae0 fffff800`02f8974c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0c059ae0 fffff800`02ccaa37 : fffffa80`05bf13b0 00000000`ffffffff 00000000`00000000 fffffa80`0b77e2b0 : nt!KiInitiateUserApc+0x70
fffff880`0c059c20 00000000`77b5fd9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`1c8dfb48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b5fd9a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02d5b38c 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
---------
My System SpecsSystem Spec
10 Feb 2011   #3

Window Home Premium 64 bit
 
 

Thanks you for the quick reply. I'll try all the things you suggested as soon as I can, and will let you know if the problem persists.
My System SpecsSystem Spec
.


Reply

 Win 7 Multiple, different BSOD




Thread Tools



Similar help and support threads for2: Win 7 Multiple, different BSOD
Thread Forum
Multiple BSOD's with multiple errors occuring randomly BSOD Help and Support
Solved Multiple BSOD's with multiple reasons BSOD Help and Support
BSOD errors. multiple times during multiple programs BSOD Help and Support
bsod constant errors, restarting ,multiple bsod BSOD Help and Support
Multiple BSOD with multiple errors. Pls help me! BSOD Help and Support
Multiple BSOD, Multiple STOP errors BSOD Help and Support
Multiple BSOD at Random Times with Multiple Drivers Identified 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 10:10 PM.
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