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: BSOD'ing with multiple BCCodes.

01 Apr 2012   #1
Calamity

Windows 7 ultimate 64-bit
 
 
BSOD'ing with multiple BCCodes.

I've had my computer for over 2 years now, experiencing not that many problems. The last 2 weeks or so have been very hectic however.

Started having problems with a bunch of different BCCodes.
So I decided to format my computer. It seems like it's gotten progressively worse and am now at the same point I was at before the format.

I thought the format would fix it, so i didn't write down the codes. But from what I can remember, and from what I have now I'm mostly just getting B3's. I've also had atleast 1 d1 and 1 1e.

2 of the times I got b3's I noticed that 5 minutes prior to the BSOD my desktop window manager crashed.

I'm running windows 7 ultimate 64-bit SP 1.

Edit: When I don't have cd-rom as first boot device, then it says BOOTMGR is missing and I have to restart... Holy **** this has become a mess.


My System SpecsSystem Spec
.
01 Apr 2012   #2
Calamity

Windows 7 ultimate 64-bit
 
 

Had yet another crash after trying to play total war shogun 2.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 50
BCP1: FFFFD80002F8617E
BCP2: 0000000000000008
BCP3: FFFFD80002F8617E
BCP4: 0000000000000007
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1


I'll try running a memtest since that seems pretty standard.
My System SpecsSystem Spec
01 Apr 2012   #3
writhziden

Windows 7 Home Premium 64 Bit
 
 

Security Software: ??? Install one of these two sets of security, update it, and run a full scan of your system for viruses/malware:

You only have 26 updates installed since Service Pack 1. Please install the remaining updates including all optional updates and excluding driver updates through Windows Update (driver updates should be obtained through the manufacturers).


Out of date driver:
Code:
yk62x64	fffff880`04856000	fffff880`048b9000	Mon Feb 23 08:02:27 2009 (49a2ba83)	0006049b		yk62x64.sys
Marvell Yukon Driver Support -> Part Number: 88E8053 -> Windows Setup Installer (32- and 64-bit) for Yukon Controllers


Code:
  1. Loading Dump File [D:\Kingston\BSODDmpFiles\Calamity\Windows_NT6_BSOD_jcgriff2\040112-28345-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02c14000 PsLoadedModuleList = 0xfffff800`02e58650 Debug session time: Sun Apr 1 10:52:48.895 2012 (UTC - 6:00) System Uptime: 0 days 0:23:48.785 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffd80002f8617e, 8, ffffd80002f8617e, 7} Could not read faulting driver name Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43cc1 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffd80002f8617e, memory referenced. Arg2: 0000000000000008, value 0 = read operation, 1 = write operation. Arg3: ffffd80002f8617e, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000007, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec2100 ffffd80002f8617e FAULTING_IP: +3462663135316566 ffffd800`02f8617e ?? ??? MM_INTERNAL_CODE: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: Shogun2.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800cad4a20 -- (.trap 0xfffff8800cad4a20) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=ffffd80002f8617e rsp=fffff8800cad4bb0 rbp=fffff8800cad4ca0 r8=fffffa80080640e8 r9=0000000000000000 r10=fffffffffffffffb r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc ffffd800`02f8617e ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c3bba7 to fffff80002c90d40 STACK_TEXT: fffff880`0cad48b8 fffff800`02c3bba7 : 00000000`00000050 ffffd800`02f8617e 00000000`00000008 fffff880`0cad4a20 : nt!KeBugCheckEx fffff880`0cad48c0 fffff800`02c8ee6e : 00000000`00000008 ffffd800`02f8617e 0000000b`00000000 fffffa80`04534540 : nt! ?? ::FNODOBFM::`string'+0x43cc1 fffff880`0cad4a20 ffffd800`02f8617e : 00000000`fff1ff00 fffff880`00000006 00000000`00000001 fffff800`02f79d00 : nt!KiPageFault+0x16e fffff880`0cad4bb0 00000000`fff1ff00 : fffff880`00000006 00000000`00000001 fffff800`02f79d00 fffff880`02f63180 : 0xffffd800`02f8617e fffff880`0cad4bb8 fffff880`00000006 : 00000000`00000001 fffff800`02f79d00 fffff880`02f63180 fffff880`0cad4c38 : 0xfff1ff00 fffff880`0cad4bc0 00000000`00000001 : fffff800`02f79d00 fffff880`02f63180 fffff880`0cad4c38 00000000`00000000 : 0xfffff880`00000006 fffff880`0cad4bc8 fffff800`02f79d00 : fffff880`02f63180 fffff880`0cad4c38 00000000`00000000 fffff800`02c93d01 : 0x1 fffff880`0cad4bd0 00000000`ffe3d000 : 00000000`00000000 fffff800`02c8ffd3 fffffa80`07268060 00000000`000003c8 : nt!CcCopyBytesToUserBuffer+0x80 fffff880`0cad4c10 00000000`00000000 : fffff800`02c8ffd3 fffffa80`07268060 00000000`000003c8 00000000`00000000 : 0xffe3d000 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+43cc1 fffff800`02c3bba7 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+43cc1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2 FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+43cc1 BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+43cc1 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\Calamity\Windows_NT6_BSOD_jcgriff2\040112-26379-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e9f650 Debug session time: Sun Apr 1 07:20:00.213 2012 (UTC - 6:00) System Uptime: 0 days 0:04:40.228 Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc000001d, fffff80002d17e5d, 0, 0} Probably caused by : memory_corruption Followup: memory_corruption --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc000001d, The exception code that was not handled Arg2: fffff80002d17e5d, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. FAULTING_IP: nt!MiAddWorkingSetPage+28d fffff800`02d17e5d 44 ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. BUGCHECK_STR: 0x1E_c000001d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: WMIADAP.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002d22a08 to fffff80002cd7d40 FAILED_INSTRUCTION_ADDRESS: nt!MiAddWorkingSetPage+28d fffff800`02d17e5d 44 ??? STACK_TEXT: fffff880`0a780ee8 fffff800`02d22a08 : 00000000`0000001e ffffffff`c000001d fffff800`02d17e5d 00000000`00000000 : nt!KeBugCheckEx fffff880`0a780ef0 fffff800`02cd73c2 : fffff880`0a7816c8 00000000`00000000 fffff880`0a781770 fffff6fb`80008408 : nt! ?? ::FNODOBFM::`string'+0x48d2d fffff880`0a781590 fffff800`02cd551f : fffff880`0a781770 fffffa80`01918b00 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff880`0a781770 fffff800`02d17e5d : 00000000`00000000 00000000`00000000 fffff6fb`00002c1f 2aaaaaaa`0000001f : nt!KiInvalidOpcodeFault+0x11f fffff880`0a781900 fffff800`02ce80d7 : 80000000`242d3867 fffffa80`04df7ae8 00000000`00000002 fffffa80`04df7ae8 : nt!MiAddWorkingSetPage+0x28d fffff880`0a7819d0 fffff800`02ce460e : 00000000`00000001 00000000`00174000 fffff880`0a781c20 fffff680`00000ba0 : nt!MiResolveDemandZeroFault+0x977 fffff880`0a781ac0 fffff800`02cd5e6e : 00000000`00000001 00000000`00174000 00000000`77582501 00000000`00000000 : nt!MmAccessFault+0x5de fffff880`0a781c20 00000000`774a2f6c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`0010d7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774a2f6c STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff80002d17e5e - nt!MiAddWorkingSetPage+28e [ 8b:8f ] 1 error : !nt (fffff80002d17e5e) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption ---------
  3. Loading Dump File [D:\Kingston\BSODDmpFiles\Calamity\Windows_NT6_BSOD_jcgriff2\040112-33399-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02c4c000 PsLoadedModuleList = 0xfffff800`02e90650 Debug session time: Sun Apr 1 07:14:05.360 2012 (UTC - 6:00) System Uptime: 0 days 4:08:22.250 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {ffffda80057b8ea8, 2, 0, fffff880014fb0f9} Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+ea ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: ffffda80057b8ea8, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff880014fb0f9, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa100 ffffda80057b8ea8 CURRENT_IRQL: 2 FAULTING_IP: NETIO!RtlGetNextExpiredTimerWheelEntry+ea fffff880`014fb0f9 8b4210 mov eax,dword ptr [rdx+10h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: opera.exe TRAP_FRAME: fffff80003ff3580 -- (.trap 0xfffff80003ff3580) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa80057b8e98 rbx=0000000000000000 rcx=fffffa80057b8e98 rdx=ffffda80057b8e98 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880014fb0f9 rsp=fffff80003ff3718 rbp=00000000000001f4 r8=0000000000e35f44 r9=fffffa80057b7000 r10=0000000000000000 r11=000000000000003c r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc NETIO!RtlGetNextExpiredTimerWheelEntry+0xea: fffff880`014fb0f9 8b4210 mov eax,dword ptr [rdx+10h] ds:3770:ffffda80`057b8ea8=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002cc82e9 to fffff80002cc8d40 STACK_TEXT: fffff800`03ff3438 fffff800`02cc82e9 : 00000000`0000000a ffffda80`057b8ea8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff800`03ff3440 fffff800`02cc6f60 : fffffa80`054943a0 00000000`00000000 fffff800`02e3de80 00000000`00e36316 : nt!KiBugCheckDispatch+0x69 fffff800`03ff3580 fffff880`014fb0f9 : fffff880`03c230cc 00000000`00e363ea 00000000`00000000 00000000`000003e8 : nt!KiPageFault+0x260 fffff800`03ff3718 fffff880`03c230cc : 00000000`00e363ea 00000000`00000000 00000000`000003e8 00000000`00000000 : NETIO!RtlGetNextExpiredTimerWheelEntry+0xea fffff800`03ff3720 fffff800`02cd3a6c : fffff800`03ff3848 00000000`0000ffff 00000000`00000001 00000000`00000000 : afd!AfdTimerWheelHandler+0xbc fffff800`03ff37a0 fffff800`02cd3906 : fffffa80`04ee5868 fffffa80`04ee5868 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c fffff800`03ff3810 fffff800`02cd37ee : 00000022`b26ef226 fffff800`03ff3e88 00000000`000e9382 fffff800`02e412c8 : nt!KiProcessExpiredTimerList+0xc6 fffff800`03ff3e60 fffff800`02cd35d7 : fffff800`02e3dec4 fffffa80`000e9382 fffffa80`0598dd40 00000000`00000082 : nt!KiTimerExpiration+0x1be fffff800`03ff3f00 fffff800`02ccbf15 : 00000000`00000000 fffffa80`076e1b60 00000000`00000000 fffff880`0593252c : nt!KiRetireDpcList+0x277 fffff800`03ff3fb0 fffff800`02ccbd2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5 fffff880`0b2949c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: NETIO!RtlGetNextExpiredTimerWheelEntry+ea fffff880`014fb0f9 8b4210 mov eax,dword ptr [rdx+10h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: NETIO!RtlGetNextExpiredTimerWheelEntry+ea FOLLOWUP_NAME: MachineOwner MODULE_NAME: NETIO IMAGE_NAME: NETIO.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79381 FAILURE_BUCKET_ID: X64_0xD1_NETIO!RtlGetNextExpiredTimerWheelEntry+ea BUCKET_ID: X64_0xD1_NETIO!RtlGetNextExpiredTimerWheelEntry+ea Followup: MachineOwner ---------
  1. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Antivirus Software... Drivers...
  2. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
    Thanks to JMH for helping with my understanding of this crash.
  3. Points to your out of date network adapter driver.
Do the steps above the .dmp file code from WinDbg and see if it resolves the problem first. Also, since you started the memory testing already:
  • If you are overclocking any hardware, please stop.

  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
    Once these steps have been followed, it is safe to remove and replace components within your computer.
My System SpecsSystem Spec
.

Reply

 BSOD'ing with multiple BCCodes.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Various BCCodes 1a, d1, 24, 7e, 3b
My nephews gaming computer. A little background; several weeks ago video output quit so nephew called me and I too found NO signal output from any PCI slot (no on board vid) regardless of what video card I tried. Dead pci, called Asus, sent them the card, they sent me a new one. Now I have video...
BSOD Help and Support
Two BSOD in one day. BCCodes: 3b and d1
When I played the sims late last year I started getting the 3b code. I don't use my desktop very often, but since I recently moved I have began to use it more. The other day it crashed while I was gone for less than a minute and then today it crashed twice within a couple of hours. A couple of...
BSOD Help and Support
BSOD Playing Warthunder, BCCodes 116 and D1 have been reported.
I have had Crashing issues with my computer as of two days ago while playing Warthunder. the original Crash report was a BCCode 116. I uninstalled warthunder then re-installed. re-installed my Graphics card Driver and disconnecting my second screen. After doing all that i started it up again...
BSOD Help and Support
Brand new build, BSoD with bccodes F4 and 7A
Hey all, this is my first time posting on the forums, so don't mind any bad etiquette. About 3 weeks ago I built myself a new computer for the first time. The installation went smoothly and everything worked perfectly fine. For the first two weeks, no errors in sight. I was playing games such as...
BSOD Help and Support
BSOD During Diablo 3. BCCodes such as "124, 50, 3b".
Hey guys. I'm running a new build I got about a month ago. I wanted to buy a new computer for D3 (needed a new one anyways), but I wasn't confident to build a computer by myself. So the company I bought it off allowed me to choose the parts and they would build it and test it for me provided I paid...
BSOD Help and Support
Multiple BSODs, multiple BCCodes, does not happen in safe mode.
Last couple weeks i've been having a large amount of bluescreens, including but not limited to bccodes 116, d1, 4e, 1a, 50 and 7a. Last night it also froze two or 3 times with no bluescreen. I recently upgraded my Phenom 9550, Biostar A770E and 6GB of DDR2-800 with an i5-2500k, an MSi P67S-C43 and...
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 23:23.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App