Alright so I started having problems over a month ago, but I only ever blue screened as I was playing League of Legends. I had another thread, but it stopped getting replies and the problem has changed now.
I was just viewing youtube videos with google chrome and received a blue screen.
I attached my .dmp.
Possible causes are Memory problems... Drivers...Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\skribbz14\032012-25630-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 (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`04609000 PsLoadedModuleList = 0xfffff800`0484d650 Debug session time: Tue Mar 20 18:13:46.486 2012 (UTC - 6:00) System Uptime: 1 days 0:37:07.931 Loading Kernel Symbols ............................................................... ................................................................ ................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {403, fffff68000009188, a420000000d8c025, fffff680000804f8} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3266c ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000000403, The subtype of the bugcheck. Arg2: fffff68000009188 Arg3: a420000000d8c025 Arg4: fffff680000804f8 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_403 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8000462dc56 to fffff80004685d40 STACK_TEXT: fffff880`09113678 fffff800`0462dc56 : 00000000`0000001a 00000000`00000403 fffff680`00009188 a4200000`00d8c025 : nt!KeBugCheckEx fffff880`09113680 fffff800`046b7137 : 00000003`00000000 fffff680`00009188 fffffa80`04c794b0 a4200000`00d8c025 : nt! ?? ::FNODOBFM::`string'+0x3266c fffff880`09113830 fffff800`046b8ae9 : 00000000`00000000 00000000`01231fff fffffa80`00000000 fffff800`00000000 : nt!MiDeleteVirtualAddresses+0x41f fffff880`091139f0 fffff800`0499bf91 : fffffa80`0749e600 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`09113b10 fffff800`0499c393 : 0000007f`00000000 00000000`01230000 fffffa80`00000001 00000000`0010ea01 : nt!MiUnmapViewOfSection+0x1b1 fffff880`09113bd0 fffff800`04684fd3 : 00000000`00000001 00000000`02800100 fffffa80`04c794b0 00000000`003af130 : nt!NtUnmapViewOfSection+0x5f fffff880`09113c20 00000000`77bd15ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0010e0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bd15ba STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+3266c fffff800`0462dc56 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+3266c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2 FAILURE_BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+3266c BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+3266c Followup: MachineOwner ---------
- 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:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- 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.
- An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a. Backup your system and user filesThe idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier and in step 3, only select Standard settings. Do not select the other two settings in the red boxes.
If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
Okay thanks for the detailed response. Over the past couple days I have tried the tests you recommended.
I passed the memtest86+ 9 times. I also passed the memory diagnostic tool. I never swapped any components though.
I also have been running the Driver Verifier for the past couple of days.
Here is a zip with the crashes I have had since I have been running the verifier.
Thanks again for all your help so far. I have noticed the crashes are becoming more frequent and outside of video gaming.
Verifier enabled. Usually means antivirus software is not running as it should, network adapter drivers are out of date or corrupted, or audio drivers are out of date or corrupted. The drivers you can find on your motherboard's support site if you know the manufacturer. If you do not know the manufacturer, let us know, and we will help you find it.Code:Loading Dump File [D:\Kingston\BSODDmpFiles\skribbz14\032512-19562-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 (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`04601000 PsLoadedModuleList = 0xfffff800`04845650 Debug session time: Sun Mar 25 07:34:48.151 2012 (UTC - 6:00) System Uptime: 0 days 0:00:13.681 Loading Kernel Symbols ............................................................... ................................................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C1, {fffff98004766fb0, fffff98004766540, 654050, 23} Probably caused by : ndis.sys ( ndis!ndisWorkerThread+ba ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) Special pool has detected memory corruption. Typically the current thread's stack backtrace will reveal the guilty party. Arguments: Arg1: fffff98004766fb0, address trying to free Arg2: fffff98004766540, address where bits are corrupted Arg3: 0000000000654050, (reserved) Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted Debugging Details: ------------------ BUGCHECK_STR: 0xC1_23 SPECIAL_POOL_CORRUPTION_TYPE: 23 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8000470648a to fffff8000467dd40 STACK_TEXT: fffff880`03038ad8 fffff800`0470648a : 00000000`000000c1 fffff980`04766fb0 fffff980`04766540 00000000`00654050 : nt!KeBugCheckEx fffff880`03038ae0 fffff800`0477f0e3 : fffffa80`03c6ff60 00000000`00000005 fffff880`00000003 00000000`00000000 : nt!MiCheckSpecialPoolSlop+0x9a fffff880`03038b20 fffff800`047aa93b : fffff800`04601000 00000000`7361444e ffffffff`ffff2950 fffff980`04766fb0 : nt!MmFreeSpecialPool+0x1d3 fffff880`03038c60 fffff880`016fca2a : 00000000`00000000 00000000`00000080 fffff880`0174f110 fffff980`04766fb0 : nt!ExDeferredFreePool+0xf33 fffff880`03038d10 fffff800`04917f7a : fffffa80`053c3220 fffffa80`03cec740 fffff880`03038db0 fffffa80`053c3220 : ndis!ndisWorkerThread+0xba fffff880`03038d40 fffff800`0466e9c6 : fffff880`03164180 fffffa80`053c3220 fffff880`0316ef80 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03038d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: ndis!ndisWorkerThread+ba fffff880`016fca2a e957ffffff jmp ndis!ndisWorkerThread+0x16 (fffff880`016fc986) SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: ndis!ndisWorkerThread+ba FOLLOWUP_NAME: MachineOwner MODULE_NAME: ndis IMAGE_NAME: ndis.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79392 FAILURE_BUCKET_ID: X64_0xC1_23_VRF_ndis!ndisWorkerThread+ba BUCKET_ID: X64_0xC1_23_VRF_ndis!ndisWorkerThread+ba Followup: MachineOwner ---------
Re-install all drivers using the following steps:
- First, download the latest driver. Then do the next steps.
- Click Start Menu
- Right Click My Computer/Computer
- Click Manage
- Click Device Manager from the list on the left
- Find the device you are trying to uninstall by expanding the appropriate set of devices
- Right click the device
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer only if Windows asks you to.
- Install the latest driver for the device.
Alternatively:
- Login as an adminstrative user.
- First, download the latest driver. Then do the next steps.
- Click Start Menu
- Click Control Panel
- Click Hardware and Sound
- Click Device Manager (the last link under Devices and Printers)
- Find the device you are trying to uninstall by expanding the appropriate set of devices
- Right click the device
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer only if Windows asks you to.
- Install the latest driver for the device.
Thanks a lot. I am going to do this a little later in the night, but I went to the device manager and noticed that under "Other Devices" there is something called "Coprocessor" that has a little yellow "!" sign over it.
I don't really know what that is, but it made me think that it may be useful to let you know about that.
It may also be helpful to know that recently when I play League of Legends I haven't been running any music in the background, which I usually do through Itunes, Spotify, or Grooveshark. Since I have done this I haven't been blue screening during games.
Finally I do not know what kind of Motherboard I have. How would I go about figuring that out?
Thanks again Writhziden
Most likely, Coprocessor is a device that you need to install for the motherboard. It is usually associated with the Chipset drivers, the most important drivers needed for the system to run properly. The fact that you do not seem to have those installed could indicate why you are having problems.
Follow System Info - See Your System Specs closely to fill in your system specs on your profile. This will include your Motherboard information.
What a neat application. It says I have:
Cpu: AMD Athlon(tm) II X3 450 Processor
Motherboard: BIOSTAR Group MCP6P3 motherboard
Bios: Default System BIOS
Total Memory: 4GB
HDD: Maxtor 7 H500F0 SCSI Disk Device
Sound: (1) NVIDIA High Definition Audio (2) NVIDIA High Definition Audio (3) NVIDIA High Definition Audio (4) NVIDIA High Definition Audio (5) High Definition Audio Device
Graphics: NVIDIA GeForce GT 240
OS: Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
I'm looking up the network and audio drivers now, but how do I find where to install the coprocessor?
I got rid of the co-processor error by installing a Nvidia Chipset. I don't know if the problem is fixed, so I am going to do everything I like to do that makes my computer crash.
Once again, thanks for all our help Writhziden
You're welcome. Let us know how it goes testing stability. Best wishes!
So far no crashes, but I have noticed that my CPU usage is really high compare to normal. Even when I was running absolutely nothing it was going crazy. It's making my computer have strange lag spikes and my music cut out. I find this strange since my computer isn't even a year old and has never reached 99% on CPU usage before.
Quote