Blue Screen errors in Windows 7 64 bit on custom PC
I built a gaming computer a few weeks ago and then started getting blue screen errors. Now they happen so frequently that I can only use it for 1 or 2 minutes before it resets with the messages "irql not less or equal" and "memory management." I'm not sure if this is a hardware or software problem and any help would be great. link to the dump file: https://skydrive.live.com/redir.aspx?cid=984bdf389a8152ac&resid=984BDF389A8152AC!105&authkey=ACqYTo9UPlc%24
August 5th, 2011 4:34pm

Run Windows Memory Diagnostic. Start orb > type memory and click on windows memory diagnostic at the top of the results. Jerry
Free Windows Admin Tool Kit Click here and download it now
August 5th, 2011 4:58pm

I did that but it didn't find anything.
August 5th, 2011 5:30pm

Sure looks like a memory chip problem. Some things to check. Did you load the latest chipset drivers for your motherboard? Do you have more than one memory board? If so, try running with one at a time. Did you let the memory test run for several cycles? How are your CPU temps? is the CPU fan running at full speed? Could also be a power supply issue. How big is your Power Supply? I assume you are not overclocking. Try going into the BIOS and see if there is an option to set Failsafe defaults. Jerry
Free Windows Admin Tool Kit Click here and download it now
August 5th, 2011 7:07pm

I see nothing definitive after a quick debug. I do see a driver loaded that is a known BSOD maker in W7 though, ASACPI.sys = part of some motherboard utilities (Asus PCProbe and AISuite) and it could be in Device Manager as Asus ATK0110 ACPI Utility. Update it if it occurs in DM, otherwise uninstall the utility that uses it. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, fffffa80063b4bd0, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041790, The subtype of the bugcheck. Arg2: fffffa80063b4bd0 Arg3: 000000000000ffff Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001f3ee40 to fffff80001ed0d00 STACK_TEXT: fffff880`08360628 fffff800`01f3ee40 : 00000000`0000001a 00000000`00041790 fffffa80`063b4bd0 00000000`0000ffff : nt!KeBugCheckEx fffff880`08360630 fffff800`01ebe17f : fffffa80`00000000 00000000`0140ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x36024 fffff880`083607f0 fffff800`01ecff93 : ffffffff`ffffffff fffff880`08360ac8 fffff880`08360ad8 fffff8a0`00008000 : nt!NtFreeVirtualMemory+0x61f fffff880`083608f0 fffff800`01ecc530 : fffff800`021a625a fffffa80`08620830 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 fffff880`08360a88 fffff800`021a625a : fffffa80`08620830 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage fffff880`08360a90 fffff800`021a65d5 : fffff880`00000000 fffff800`021c7c00 000007ff`fffdc000 00000000`00000000 : nt!PspExitThread+0x5ba fffff880`08360b90 fffff800`021a66dd : fffffa80`08620830 00000000`00000000 fffffa80`08620830 00000000`01167900 : nt!PspTerminateThreadByPointer+0x4d fffff880`08360be0 fffff800`01ecff93 : fffffa80`08620830 fffff880`08360ca0 00000000`00000000 00000000`00000000 : nt!NtTerminateThread+0x45 fffff880`08360c20 00000000`7727184a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0140fe18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7727184a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+36024 fffff800`01f3ee40 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36024 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024 BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024 Followup: MachineOwner ---------
August 5th, 2011 7:44pm

Checklist for whenever blue screens appear: Faulty memory module. Blue screens if not caused by software are likely to be caused by bad memory. It is not unusual that a machine works perfect with Windows XP and then starts behaving badly when upgraded to Windows 7 due to changes in memory management. Use built in Windows Memory Diagnostics (on your Windows 7 machines press F8 before Windows starts to load and choose “Windows Memory Diagnostics”) to troubleshoot the memory modules. Drivers. Bad drivers are without doubt the most common cause for blue screens. Therefore update your drivers either by going to Windows Update or the hardware manufacturer’s web site. If no Windows 7 driver exists for the hardware go with the Windows Vista driver as good as all Vista drivers work with Windows 7. BIOS. When having problems with hardware in any way and particularly blue screens I would strongly recommend a BIOS upgrade as that many times improve stability and compatibility. Also resetting the BIOS settings to the default is always a good idea. Bad hard drive. Bad hard drives are sometimes causing blue screens. I recommend using Hitachi’s Drive Fitness Test, which can scan any brand of hard drives for errors. This tool can be found at http://www.hitachigst.com/hdd/support/download.htm
Free Windows Admin Tool Kit Click here and download it now
August 6th, 2011 2:05am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics