 | |
| |
| 05 Jun 2011 | #1 |
| | BSOD on my x64 win7 system HELP PLZ currently running Windows 7 x64 ultimate and these blue screens are starting to pop up one every few days while im either playing games or watching movies or just surfing the net. memtest found no errors after running for a full 24 hours on 8gigs of ram. i dont know how to read the dump files but maybe someone can help here. |
My System Specs | |
| 06 Jun 2011 | #2 |
| | The cause is STOP 0x0000001A: MEMORY_MANAGEMENT Usual causes: Device driver, memory, kernel The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred. Did you use memtest86+? Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs. For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place. How to Post a Screenshot in Seven Forums Have you been checking your temperatures? Use Real Temp, run one of these and check the CPU temps when at idle, under load and/or testing. Let us know the minimum and maximum temps you get. Go to your BIOS and tell us what the CPU, RAM and North Bridge (NB) voltages are. Usually with more than 4GB RAM, RAM cards 2GB or larger, four RAM cards, you will need a NB memory controller voltage bump. With some information we can adjust some settings. Code: *******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff6800007df58
Arg3: 84400002bbd7d867
Arg4: 0000000000000001
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 fffff80003072406 to fffff800030cad00
STACK_TEXT:
fffff880`07e3a458 fffff800`03072406 : 00000000`0000001a 00000000`00000403 fffff680`0007df58 84400002`bbd7d867 : nt!KeBugCheckEx
fffff880`07e3a460 fffff800`030fcc27 : 00000000`00000000 fffff680`0007dff8 fffffa80`09f86b30 fffff800`03009b7f : nt! ?? ::FNODOBFM::`string'+0x330bc
fffff880`07e3a610 fffff800`030b817f : fffffa80`00000000 00000000`101a8fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`07e3a7d0 fffff800`030c9f93 : ffffffff`ffffffff fffff880`07e3aaa0 fffff880`07e3ab08 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`07e3a8d0 fffff800`030c6530 : fffff960`00125874 00000000`00000001 fffff900`c0132010 fffff900`c235e780 : nt!KiSystemServiceCopyEnd+0x13
fffff880`07e3aa68 fffff960`00125874 : 00000000`00000001 fffff900`c0132010 fffff900`c235e780 00000000`00000000 : nt!KiServiceLinkage
fffff880`07e3aa70 fffff960`00125bc4 : ffffffff`00000000 fffff880`00000000 fffff900`c235e780 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`07e3abc0 fffff960`000e67d9 : ffffffff`81050de7 fffff900`c235e780 00000000`00000de7 00000000`7efdb000 : win32k!bDeleteSurface+0x34
fffff880`07e3abf0 fffff800`030c9f93 : fffffa80`0722b540 fffff880`07e3aca0 00000000`00030340 00000000`0039edf0 : win32k!NtGdiDeleteObjectApp+0xd5
fffff880`07e3ac20 00000000`75842e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0011e928 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75842e09
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!SURFACE::bDeleteSurface+3c8
fffff960`00125874 e9b0010000 jmp win32k!SURFACE::bDeleteSurface+0x57d (fffff960`00125a29)
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: win32k!SURFACE::bDeleteSurface+3c8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d6f104c
FAILURE_BUCKET_ID: X64_0x1a_403_win32k!SURFACE::bDeleteSurface+3c8
BUCKET_ID: X64_0x1a_403_win32k!SURFACE::bDeleteSurface+3c8
Followup: MachineOwner
--------- Go to Device Manager and look for a yellow triangle in System Devices, right click it and select 'Properties' driver tab and 'Update Driver'. Code: Error Symptom: Device drivers are not installed. Cause: A driver has not been installed for this device preventing it from working properly. Details: The device driver for #UNKNOWN# has not been installed. This device will not be available until the correct device driver is installed. Resolution: 1. Try installing the drivers using Windows Update. 2. Install the drivers that are on the installation media that came with the device. 3. Check with the manufacturer for an updated driver. These are from Windows update. D/L and run Western Digital Lifeguard – Quick Test and Extended Test Code: Event[149]: Log Name: System Source: Disk Date: 2011-06-04T23:07:55.403 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Goonsac Description: The driver detected a controller error on \Device\Harddisk4\DR4. |
| My System Specs |
| 06 Jun 2011 | #3 |
| | ok dave heres the snips you requested, im going to post up after each task you asked me to do so i dont confuse myself |
| My System Specs |
| . |
| |
| 06 Jun 2011 | #4 |
| | heres idle use and how i use the computer daily with a game running and video running fullscreen |
| My System Specs |
| 06 Jun 2011 | #5 |
| | MSE was fully up to date, and i ran a full scan with no problems, as for that plug and play driver, i have no clue what its for the only usb devices i have plugged in are my keyboard, mouse, usb mic, and my cell phone charger microusb cable, every one of those has drivers installed and updated except for the usb mic because it uses the drivers windows7 provides for it, it doesnt have its own drivers. when i goto update that pnp device it says windows cant find drivers for it, so im not sure what to do there. *EDIT* so i solved the missing driver issue, seems it was the uguru on my mobo that wasnt updated, went and downloaded the last known update from 2008 and the missing driver sign disappeared Last edited by projectdwnshft; 06 Jun 2011 at 07:14 PM.. |
| My System Specs |
| 06 Jun 2011 | #6 |
| | Go to your BIOS and tell us what the CPU, RAM and North Bridge (NB) voltages are. ok so rebooted into the bios to try and find what you asked for and heres all i could find that i assumed was what u needed. CPU core voltage 1.2250V RAM DDR2 Voltage AUTO CPU VTT Voltage 1.20V MCH 1.25V Voltage AUTO ICH 1.05V Voltage 1.05V ICHIO 1.5V Voltage 1.5V i did not find anything that said NB or Northbridge anywhere in the voltage sections of the bios, also im currently running 4 sticks of Corsair XMS2 DDR2 2GB sticks of ram |
| My System Specs |
| 06 Jun 2011 | #7 |
| | just finished running WD Data Lifeguard on all 3 drives in my system running both the Quick scans on each then followed that with full scans on each drive. Every drive PASSED but i notice "The driver detected a controller error on \Device\Harddisk4\DR4." would is saying harddisk4 but theres only 3 drives on my system so what could that be reading? |
| My System Specs |
| 07 Jun 2011 | #8 |
| | Good information. When you have more info to add just use the 'Edit' button and add it to the last post you have started, this makes it easier. Your CPUZ info looks good, the frequencies are fine, with 8GB RAM, 4X2GB cards, and 4 RAM cards installed you will need to bump the voltage on the NB memory controller and maybe the RAM. Can you confirm your BIOS version" The Abit site starts with BIOS ID 10 and goes to 17, CPUZ shows 6.00 PG. Confirm if this is the right motherboard Abit IP35 Pro. The idle temps aren't bad, but not really good either. Are you using the stock Intel cooler? The stress temps are still below the recommended max of 76°C for CPU core temp. You should consider getting an aftermarket CPU cooler, it will drop those temps by 10°C. Not critical, just something to consider. 
Quote: Originally Posted by projectdwnshft  MSE was fully up to date, and i ran a full scan with no problems, as for that plug and play driver, i have no clue what its for the only usb devices i have plugged in are my keyboard, mouse, usb mic, and my cell phone charger microusb cable, every one of those has drivers installed and updated except for the usb mic because it uses the drivers windows7 provides for it, it doesnt have its own drivers. when i goto update that pnp device it says windows cant find drivers for it, so im not sure what to do there. *EDIT* so i solved the missing driver issue, seems it was the uguru on my mobo that wasnt updated, went and downloaded the last known update from 2008 and the missing driver sign disappeared
Quote: Originally Posted by projectdwnshft Go to your BIOS and tell us what the CPU, RAM and North Bridge (NB) voltages are. ok so rebooted into the bios to try and find what you asked for and heres all i could find that i assumed was what u needed. CPU core voltage 1.2250V RAM DDR2 Voltage AUTO CPU VTT Voltage 1.20V MCH 1.25V Voltage AUTO ICH 1.05V Voltage 1.05V ICHIO 1.5V Voltage 1.5V i did not find anything that said NB or Northbridge anywhere in the voltage sections of the bios, also im currently running 4 sticks of Corsair XMS2 DDR2 2GB sticks of ram Try setting them to 'Manual' or if that doesn't work increase them by the smallest amount possible and post the voltages here. Another option: Don't lower these two voltages, if you get an indication that the voltage is already higher than these recommendations, post the voltages before proceeding. Default for RAM DDR2 should be 1.80v, bump it to 1.85v Default for MCH should be 1.25v, bump it to 1.35v. Then run memtest86+ for a full 7 passes. You can stop the test if you get any errors.
Quote: Originally Posted by projectdwnshft just finished running WD Data Lifeguard on all 3 drives in my system running both the Quick scans on each then followed that with full scans on each drive. Every drive PASSED but i notice "The driver detected a controller error on \Device\Harddisk4\DR4." would is saying harddisk4 but theres only 3 drives on my system so what could that be reading? Depending on your mobo and BIOS, it could be SATA/IDE port #4, or the 4th drive in your system. This will include your CD/DVD drive. The number usually will not correspond to the disk management drive number or location.. Last edited by Dave76; 07 Jun 2011 at 08:32 AM.. |
| My System Specs |
| 07 Jun 2011 | #9 |
| | ok to answer your first question, the bios im on is version 10 i just checked. yes im currently using an aftermarket heatsink thats double the size of the oem intel one. im having some trouble understanding what your asking for here. " Quote: I need the RAM DDR2 and MCH voltages. Try setting them to 'Manual' or if that doesn't work increase them by the smallest amount possible and post the voltages here. Another option: Don't lower these two voltages, if you get an indication that the voltage is already higher than these recommendations, post the voltages before proceeding. Default for RAM DDR2 should be 1.80v, bump it to 1.85v Default for MCH should be 1.25v, bump it to 1.35v. the ddr2 was already set on 1.8v and i bumped it to 1.85v but the mch was on auto so i switched it to 1.25v but my other choices were 1.29, 1.33, 1.37, 1.41v. should i bump the mch to the 1.33 or 1.37v? as for updating the bios that is something i dont find myself comfortable with doing on my own because if anything goes wrong i could ruin my system. |
| My System Specs |
| 08 Jun 2011 | #10 |
| | Bump the MCH to 1.33v. Don't recommend flashing the BIOS unless it is obvious that it will help your issues and all other possibilities are covered. This can be saved for later, only if absolutely necessary. Just for reference. Quote: BIOS: m629b17.zip Bios Issue Date:2008/05/26 Mirror Site: ASIA Europe US BIOS ID:17 Fixed 45nm CPU compatibility and support CPU half multiplier. Fixed the Wake Up by WAKE# of PCIe function abnormality. Fixed system hang when used Intel PXE CPU series. Fixed CPU temperature abnormality when S3 return. BIOS compiled date: 05/26/2008. BIOS: m629b16.zip Bios Issue Date:2008/03/18 Mirror Site: ASIA Europe US BIOS ID:16 Update AHCI ROM version. Update CPU Micro code. Enhanced 45nm CPU compatibility. Fixed C1E function abnormality. Fixed Quick Power On Self Test function abnormality. BIOS compiled date: 03/18/2008. BIOS: m629b14.zip Bios Issue Date:2007/09/06 Mirror Site: ASIA Europe US BIOS ID:14 Fixed the POST will show CPU has been changed message when first time SAVE & EXIT BIOS menu. Enhanced the S3 compatibility with abitEQ utility. BIOS compiled date: 09/06/2007. BIOS: m629b12.zip Bios Issue Date:2007/08/15 Mirror Site: ASIA Europe US BIOS ID:12 Update CPU micro code. Support Wolfdale & Yolkfield CPU. Support the pin definition of Front Audio adjusting function. BIOS compiled date: 08/15/2007. BIOS: m629b11.zip Bios Issue Date:2007/07/09 Mirror Site: ASIA Europe US BIOS ID:11 Support CL=3. Enhanced compatibility with certain memories. Support Command Rate adjusting function. Update Jmicron BIOS to V1.06.69. BIOS compiled date: 07/09/2007 BIOS: m629b10.zip Bios Issue Date:2007/05/17 Mirror Site: ASIA Europe US BIOS ID:10 First release. BIOS compiled date: 5/17/2007 |
| My System Specs |
 |
BSOD on my x64 win7 system HELP PLZ problems?
| Thread Tools | |
| Similar help and support threads for: BSOD on my x64 win7 system HELP PLZ | ||||
| Thread | Forum | |||
 BSOD after a system restore due to a corrupted user profile on win7 | BSOD Help and Support | |||
| 5.1 system with Win7? | Sound & Audio | |||
| A fresh win7 install over a win7/vista dual boot system ? | Installation & Setup | |||
| After Win7 BSOD i cant access bios or boot the system | BSOD Help and Support | |||
| win7 bsod almost always when i leave system from RDP | BSOD Help and Support | |||
All times are GMT -5. The time now is 05:10 AM.
