BSOD win7 x64 memory management

[loppefaaret]

Hi 7forums!

lets get straight to it:
Windows 7 x64 - retail (edit: ultimate)
homebuild:
motherboard: MSI P67A-GD65 (B3) (never clocked)
cpu: intel sandy bridge i5 2500k (never clocked)
ram: kingston 4gb ddr3 1333 (never clocked)
graphics: nvidia 260 GTX (been clocked down, running stock)
hdd: samsung 500gb 16MB 7200 in raid0 on intel controller
optical: samsung SATA DVDRW+- x18
coolers: 1cpu, 1gfx, 4cabinet.

the motherboard, ram, cpu and cabinet bought less than 3 months ago
optical, hdds and graphics are passed from old system, 1-2 year+. hdd's pass SMART flawless, no corrected sectors.

Windows install is about 5 weeks old


ive had 7 BSOD's over the last 3 weeks.
but my windows 7 is not creating files in /windows/minidumps/ , rather, it creates "MEMORY.DMP" in /windows/ , wich are about 400MB each. wich has lead to loss of the first BSOD, wich indicated Intels iaStorV.sys, and the last 3 BSOD's indicated MEMORY MANAGEMENT.

i've just completed 3 passes of x86memtest, no errors.(the linux version, not MS)

if there is anything else i might have missed, please let me know


Loppefaaret

 

[zigzag3143]

Hi 7forums!

lets get straight to it:
Windows 7 x64 - retail (edit: ultimate)
homebuild:
motherboard: MSI P67A-GD65 (B3) (never clocked)
cpu: intel sandy bridge i5 2500k (never clocked)
ram: kingston 4gb ddr3 1333 (never clocked)
graphics: nvidia 260 GTX (been clocked down, running stock)
hdd: samsung 500gb 16MB 7200 in raid0 on intel controller
optical: samsung SATA DVDRW+- x18
coolers: 1cpu, 1gfx, 4cabinet.

the motherboard, ram, cpu and cabinet bought less than 3 months ago
optical, hdds and graphics are passed from old system, 1-2 year+. hdd's pass SMART flawless, no corrected sectors.

Windows install is about 5 weeks old


ive had 7 BSOD's over the last 3 weeks.
but my windows 7 is not creating files in /windows/minidumps/ , rather, it creates "MEMORY.DMP" in /windows/ , wich are about 400MB each. wich has lead to loss of the first BSOD, wich indicated Intels iaStorV.sys, and the last 3 BSOD's indicated MEMORY MANAGEMENT.

i've just completed 3 passes of x86memtest, no errors.(the linux version, not MS)

if there is anything else i might have missed, please let me know


Loppefaaret

No DMP files included in upload try this method.




To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[loppefaaret]

here we go, got the minidumps of another bsod: bad pool handler
never seen this one before

edit;
i guess u need a new complete run of the tool, the perfmon report along the new minidump, so collected it all in all.zip

 

[zigzag3143]

here we go, got the minidumps of another bsod: bad pool handler
never seen this one before

edit;
i guess u need a new complete run of the tool, the perfmon report along the new minidump, so collected it all in all.zip

BugCheck 19, {22, 800000000000000, 0, 0}

GetPointerFromAddress: unable to read from fffff80002d150e8
GetUlongFromAddress: unable to read from fffff80002c82210
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )