Hey,
I've recently bought a new computer and I just can't get to work right.
I've tried to install diffrent versions of Windows 7 64 bit and I keep on getting BSODs, this does not happen on any other 32 bit software I've tried like Vista and Windows 7.
The BSODs I get varey all the time, currently on last installment, i got 2 crashes: IRQL_NOT_LESS_OR_EQUAL on 0x0000000a
and BAD_POOL_HEADER on 0x00000019
any ideas ???
this are my computer parts :
OS Windows 7 Ultimate 64 bit
CPU Intel 2.33GH 4MB CORE2QUAD Q8200
Motherboard MSI G41TM-E43 HDMI
Memory 2X DBT GEIL 2GB DDR2 800MHZ
Graphics Card(s) POV Nvidia GeForce 9500GT 1GB
Sound Card O/B
Monitor(s) Displays Samsung P2350
Hard Drives Westeren Digital 500GB SATA2
PSU FPS400-60hcn 12CM FAN
Case MIDI TOWER EZCOOL
Hi Yairco...Welcome to the forums...
Navigate to c:/windows/minidump and zip up the .dmp file for analysis by a local Guru.
hey,
thanks for the super quick reply...
theres the files. just got another BSOD - SYSTEM_SERVICE_EXCEPTION
what do u say ?
cool , thanks!.
meantime I just got another one, this time its SYSTEM_THREAD_EXCEPTION_NOT_HANDLED at 0x1000007e
I added the dmp file.
It may be interesting from a forensic stand point to wait for Andre to analyze your dump files, but you may want to start backing up your files in case a re-installation is necessary...
belive me I'm ready to go..
I think its my 10th installment by now. :)
These are all errors that affect your memory - so most likely they're a device driver/system service issue. But, numerous different error messages frequently seem to point to hardware issues.
The only thing of note that I can see is your PSU - it appears to be a 400 watt unit (which is awfully anemic for today's hardware).
Beyond that I'd wait for H2SO4's advice.
Summary of the memory dumps:
Code:Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Oct 23 13:26:52.191 2009 (GMT-4) System Uptime: 0 days 0:24:04.752 BugCheck 3B, {c0000005, fffff8000288b4ec, fffff8800876bfe0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: iexplore.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Oct 23 13:02:20.983 2009 (GMT-4) System Uptime: 0 days 1:11:52.544 BugCheck A, {0, 2, 1, fffff800028a4c3a} Probably caused by : ntkrnlmp.exe ( nt!AlpcpQueueIoCompletionPort+1aa ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: iexplore.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Oct 23 16:17:16.417 2009 (GMT-4) System Uptime: 0 days 2:49:47.352 BugCheck 1000007E, {ffffffffc0000005, fffff8800418affb, fffff8800593c658, fffff8800593beb0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab ) PROCESS_NAME: System DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Oct 23 11:09:09.176 2009 (GMT-4) System Uptime: 0 days 0:54:32.111 BugCheck 19, {3, fffff80002a0aad0, fffff80002a0aad0, fffff80002a0aed0} Probably caused by : Pool_Corruption ( nt!ExFreePool+536 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: iexplore.exe
4 very different crashes. You might want to run full memory diagnostics, if you haven't done so already. With new hardware, there's always the possibility of a hardware-level problem.
One of the crashes looks networky. I'd start by updating this NIC driver, if possible:
Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
Timestamp: Thu Feb 26 20:04:13 2009 (49A65B0D)
Another of the crashes indicates a condition known as pool corruption. To try to catch the culprit at the point where it does the damage, on an elevated (run as admin) CMD prompt:
VERIFIER /FLAGS 1 /ALL
<reboot>
Please upload any minidumps from subsequent crashes for analysis.
Afterwards, when this is all over, go back to default settings by running:
VERIFIER /RESET
Quote