Blue Screen error in Windows 7, only able to use computer in Safe Mode with networking

Anonymous
2010-05-26T02:05:22+00:00

Blue Screen of Death (BSOD) is apperaing in WIN 7 too. I can only use my computer in Safe Mode with Networking. I have several minidump files but how do I use them with WinDbg utility. Also how do I load and verify the symbols. Does anyone have Microsoft support 1800 number? Thanks.

Blue Screen of Death (BSOD) is apperaing in WIN 7 too. I can only use my computer in Safe Mode with Networking.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

51 answers

Sort by: Most helpful
  1. Anonymous
    2010-06-20T18:39:03+00:00

    PowerDVD's not at fault.  This bugcheck was due to memory corruption. 

    You have the following stale drivers installed - check for updates to them or the software they came with, or uninstall /disable them.

    adfs.SYS 6/26/2008 (Adobe Drive Filesystem?)

    000.fcl 9/26/2008

    mcdbus.sys 2/24/2009 

    viahduaa.sys 5/7/2009  

    ASACPI.sys 5/13/2009 (ASUS motherboard)

    For memory corruption cases such as you seem to be experiencing, it can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out  of the dialog.

    Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot  completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

    Wait for a bugcheck to occur after enabling verifier as described, and then upload it to your SkyDrive, and provide a link.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-06-20T16:58:55+00:00

    That sucks. Now PowerDVD is the crashes. I just started WinDbg and got the following:

    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\062010-26317-01.dmp] Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*C:\Debugging Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff80003265000 PsLoadedModuleList = 0xfffff800034a2e50 Debug session time: Sun Jun 20 08:45:11.600 2010 (GMT-5) System Uptime: 2 days 14:12:45.203 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ........... ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 4E, {99, 96092, 2, 96086}Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )Followup: MachineOwner ---------0: 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: 0000000000096092, page frame number Arg3: 0000000000000002, current page state Arg4: 0000000000096086, 0Debugging Details: ------------------ BUGCHECK_STR:  0x4E_99CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULTPROCESS_NAME:  PowerDVD10.exeCURRENT_IRQL:  2LAST_CONTROL_TRANSFER:  from fffff800033652bc to fffff800032d5600STACK_TEXT:  fffff88008a8c108 fffff800033652bc : 000000000000004e 0000000000000099 0000000000096092 0000000000000002 : nt!KeBugCheckEx fffff88008a8c110 fffff80003347925 : 0000000000000000 fffff68000362708 1f90000015dee005 0000000000000001 : nt!MiBadShareCount+0x4c fffff88008a8c150 fffff800032a9b43 : fffffa80077589b0 fffff70000004810 0000007ffffffff8 fffff8a00afc34d0 : nt! ?? ::FNODOBFM::string'+0x3226c fffff88008a8c1e0 fffff800032a85a2 : fffffa80077589b0 fffffa8000000000 0000000000002efe fffff80000000000 : nt!MiDeleteAddressesInWorkingSet+0x307 fffff88008a8ca90 fffff800035bbc4f : fffff8a00548aa50 0000000000000001 0000000000000000 fffffa8006d48440 : nt!MmCleanProcessAddressSpace+0x96 fffff88008a8cae0 fffff800035936eb : 0000000000000000 0000000000000001 000000007efdb000 0000000000000000 : nt!PspExitThread+0x92f fffff88008a8cba0 fffff800032d4853 : fffffa80077589b0 0000000000000000 000000007efdb001 fffffa8006d48440 : nt!NtTerminateProcess+0x25b fffff88008a8cc20 0000000076f4017a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13 000000000008e308 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x76f4017a STACK\_COMMAND:  kbFOLLOWUP\_IP: nt!MiBadShareCount+4c fffff800033652bc cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt!MiBadShareCount+4cFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfebIMAGE_NAME:  memory_corruptionFAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4cBUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4cFollowup: MachineOwner

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-06-20T14:40:34+00:00

    Hey,

    the nightmares are back. it just crashed again with the message "PFN_LIST_CORRUPT" I have uploaded today's dump file tohttp://cid-46b814bd96174a48.office.live.com/self.aspx/Minidump%20Files/Win%207%20Dump.zip.

    Should I unistall Mcafee and let it run for two week? The BSODs are popping less freuently now....in almost two weeks. Sorry to bother you folks again.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-06-16T10:37:25+00:00

    Good to hear things have improved with your system...

    One way I saw this put recently was akin to "This is not Microsoft - these are forums supplied by Microsoft".  That is to say, one would expect a vast majority of forum participants here are not Microsoft employees. (Those that are seem to have MSFT or "Microsoft Support" after their name.)  Some are Microsoft Partners (by virtue of some apparent business agreement) and some like auggy are MVPs.

    If you're interested in openings at Microsoft, check their careers page.  As large and distributed of a company as Microsoft is, they seem always to be hiring in some fashion...

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2010-06-16T08:46:38+00:00

    Everything seems to be fine now, though I still have my fingers crossed. thank you every one. Are you folks hiring at Microsoft?

    Was this answer helpful?

    0 comments No comments