getting BSODs on Windows 7 64 bit

[yairco]

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 ???

 

[yairco]

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

 

[Tews]

Hi Yairco...Welcome to the forums...

Navigate to c:/windows/minidump and zip up the .dmp file for analysis by a local Guru.

 

[yairco]

hey,

thanks for the super quick reply...

theres the files. just got another BSOD - SYSTEM_SERVICE_EXCEPTION

what do u say ?

 

[Tews]

We save the analysis for H204. He's the expert in BSOD examination...

 

[yairco]

cool , thanks!.

meantime I just got another one, this time its SYSTEM_THREAD_EXCEPTION_NOT_HANDLED at 0x1000007e

I added the dmp file.

 

[Tews]

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...

 

[yairco]

belive me I'm ready to go..
I think its my 10th installment by now.

 

[usasma]

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:

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

 

[H2SO4]

belive me I'm ready to go..
I think its my 10th installment by now.

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

 

[yairco]

thanks a lot. got some work to do now..
meanwhile I'm adding here another late BSOD, this one was CACHE_MANAGER at 0x00000034, file's attached.

just another thing to be sure, when u said

"You might want to run full memory diagnostics, if you haven't done so already."

with which software you would reccomende using for that ?

 

[yairco]

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).

would you reccomend on changing it ?
what difficulties can come from low power ?


this forum is awesome btw

 

[H2SO4]

thanks a lot. got some work to do now..

No problem

meanwhile I'm adding here another late BSOD, this one was CACHE_MANAGER at 0x00000034, file's attached.

That one looks distinctly more hardware-ish than the others. Minidumps are not a good way to pinpoint the exact component which is defective - if any - but in this case the crash suggests memory unreliability.

just another thing to be sure, when u said

"You might want to run full memory diagnostics, if you haven't done so already."

with which software you would reccomende using for that ?

The in-built memtest/mdsched (same thing done in a different way) has a subtle advantage over the (very popular) memtest86 that's not easy to explain succinctly. It doesn't really matter which one you choose right now though - both will perform the same task.

As a word of caution, not finding anything wrong on the first few passes doesn't by itself prove much. It can take hours or days for some types of memory abnormalities to manifest themselves during normal operation, so there's no guarantee that a memory tester will expose and isolate a problem straight away.

 

[yairco]

ok, so meanwhile I've updated the NIC driver and also the O/B sound card driver..

got another BSOD on the way - another SYSTEM_SERVICE_EXCEPTION on 0x0000003b, file's attached..

I'm gonna do the VERIFIER /FLAGS 1 /ALL cmd now.

 

[yairco]

I did the verifier cmd, I attached a screen shot of what it said,
at restart I got another BSOD - BAD_POOL_HEADER at 0x00000019.

I'm going to run the memtest now.

 

[yairco]

did the memtest - no errors.

in your point of view at the moment, would you reckon its a software or hardware problem ?

 

[H2SO4]

did the memtest - no errors.

in your point of view at the moment, would you reckon its a software or hardware problem ?

I'm relatively confident it's hardware.

I see (from the latest dumps) that you've updated the NIC driver. There's comparatively little in terms of 3rd-party drivers on your machine, and despite the "special pool" setting the latest crash fingers the kernel as being a pool corruptor. That usually means hardware.

A few minutes of memtesting is frequently not enough. Try running the diagnostics overnight.

 

[yairco]

I did another memtest, this time I used the memtest86 and took the long check. didn't find any errors.

since the last BSOD - BAD_POOL_HEADER , I didn't recive any other BSOD.
I hope that it'll remain stable.

I havent did the reviever /reset cmd - is it importent ? maybe it has something to do with the BSODs stop appearing ?

I really appreciate ur work on this forum - thanks a lot guys !

 

[usasma]

Don't do the /reset command until you're finished generating BSOD's.
The purpose of the /FLAGS 1 /ALL command is to make the system crash - hopefully naming the faulty driver when it does.

When you run the /reset command, the system will no longer stress the drivers - making a BSOD much less likely. Normally you'll see a small bit of a performance increase when doing this (depending on the settings and your system's specifications).

 

[yairco]

hey guys,

after a few days of quiet those damn BSODS came back!
I got quiet a few SYSTEM_SERVICE_EXCEPTION , CACHE_MANAGER and MEMORY_MANAGEMENT. I attached the minidumps here.

theres one dump that I know that I got over, had to do with a beta NVIDIA driver so I changed back to the latest. (I did learn something from you guys!)

also , when u reviewed my system you suggested that my power(450W) unit was too anaemic for a present computer, should I change it ?