Windows 7 Random BSOD's tried everything. please help

[SimbaTao]

Hi All,
I am having fits trying to figure out why my computer is randomly going into
bluescreens.
I have done a chkdsk /f/r (no errors), I have done 7 hours of memtest86+ (no
errors) I have swapped out my GeForce 9500GT graphics card with my onboard Nvidia
7025 graphics chip (BSOD's on either), I have updated all the drivers from my
motherboards website (BSOD's before and after), I have re-formatted and re-
installed and fully updated, (including SP1) my Windows 7 64bit (BSOD's
continued). I have checked all the connections inside and made sure it is not all
covered in dust. I have checked that it isn't overheating. I am running out of
ideas what to do, to find out what is causing me this nightmare.

I have defragged. I have switched my usb mouse for a PS/2 one (BSOD's continued).

It crashes at various times and the errors it gives have been changing from this
to that, and really haven't given me much idea as to what is the cause.

I am at wits end because it isn't that old for a computer, I have only had it for
~ a year. I really don't want to go out paying for new parts (PSU, Motherboard)
without have at least some sense of knowing what is the cause.

I can be reading email, or just starting it up and trying to open a folder when
it crashes, it could be anything, it seems, that I do, when it decides to go
bluescreen.

I am running an AMD Phenom II 955 on an M4N68T-M-ASUS motherboard. I
have 2X2 Kingston KVR 133303N9/2G 1.5v Ram and 2 western digital 500 gig hdds, one
SATA, one IDE, running in master/slave config. I am running Microsoft Security
Essentials that is up to date and also have scanned my system prior to sending
this and came back clean.

If anyone has some advice or can offer any help I would be very much appreciating
the sage from you guys.

 

[usasma]

I've seen some issues with the Asus M4 series of motherboards due to memory settings. The suggestion is to get the proper timings/settings/voltages from the Kingston website for your memory - and then set it manually in your BIOS (in other words, DON'T use the Auto setting).

Only 94 updates since SP1 - most systems have 130 - 140. Please visit Windows Update and get all available updates (may take multiple visits).

You have the 2005 version of ASACPI.sys - a known BSOD cause on Win7 systems. This is the Asus ATK0110 ACPI Utility driver - and must be updated to the 2009 version. Install the Asus AISuite or PCProbe utility - then check to ensure that the ASACPI.sys driver is dated from 2009 (it's in C:\Windows\System32\drivers). Here's the link to your motherboard download site: ASUS - Motherboards- ASUS M4N68T-M The utilities will be listed in the Utilities section there.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

ASACPI.sys Sun Mar 27 22:30:36 2005 (42476C4C)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7). Also a part of the Asus PCProbe and AISuite Utilities
Link Removed - Invalid URL

nvmf6264.sys Thu Jul 30 19:48:18 2009 (4A723142)
nVidia nForce network driver
Link Removed - Invalid URL

nvstor64.sys Tue Aug 4 20:31:07 2009 (4A78D2CB)
nVidia Storage Driver (nForce chipset driver)
Link Removed - Invalid URL

Please ensure that Driver Verifier is turned off. If the BSOD's continue, please post back for further suggestions.

Analysis:
The following is for information purposes only.

[font=lucida console]**************************Thu Sep 27 13:23:45.392 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092712-20592-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:03:06.953[/B]
BugCheck Code: [B]BugCheck D1, {0, 2, 8, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiPageFault+260 )[/B]
BugCheck Info: [B]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/B]
PROCESS_NAME: [B]svchost.exe[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
FAILURE_BUCKET_ID: [B]X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260[/B]
  BIOS Version                  0501   
  BIOS Release Date             08/03/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Sep 26 23:56:52.268 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092612-13384-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:06:48.969[/B]
BugCheck Code: [B]BugCheck 18, {0, fffffa8004a98df0, 2, ffffffffffffffff}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+49331 )[/B]
BugCheck Info: [B]REFERENCE_BY_POINTER (18)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x18
PROCESS_NAME: [B]svchost.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_+49331[/B]
  BIOS Version                  0501   
  BIOS Release Date             08/03/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Sep 26 23:48:02.695 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092612-19078-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:03:13.007[/B]
BugCheck Code: [B]BugCheck 1E, {ffffffffc000001d, fffff8000287ebd2, 2, ffffffffffffff00}[/B]
Probably caused by :[B]memory_corruption ( nt!MiDeletePteList+92 )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
BUGCHECK_STR:  0x1E_c000001d
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]csrss.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1E_c000001d_BAD_IP_nt!MiDeletePteList+92[/B]
  BIOS Version                  0501   
  BIOS Release Date             08/03/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep 25 16:09:52.686 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092512-23836-01.dmp]
Windows 7 Kernel Version [B]7600 [/B]MP (4 procs) Free x64
Built by: [B]7600[/B].17017.amd64fre.win7_gdr.120503-2030
System Uptime:[B]1 days 7:20:35.982[/B]
BugCheck Code: [B]BugCheck C4, {91, 2, fffffa800452fb60, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4894 )[/B]
BugCheck Info: [B]DRIVER_VERIFIER_DETECTED_VIOLATION (c4)[/B]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_91
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]Steam.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4894[/B]
  BIOS Version                  0501   
  BIOS Release Date             08/03/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Sep 24 07:47:24.272 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092412-20108-01.dmp]
Windows 7 Kernel Version [B]7600 [/B]MP (4 procs) Free x64
Built by: [B]7600[/B].17017.amd64fre.win7_gdr.120503-2030
System Uptime:[B]0 days 0:45:35.051[/B]
BugCheck Code: [B]BugCheck D1, {1, 2, 8, 1}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiPageFault+260 )[/B]
BugCheck Info: [B]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/B]
PROCESS_NAME: [B]System[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
FAILURE_BUCKET_ID: [B]X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Sep 24 05:17:30.769 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092412-22526-01.dmp]
Windows 7 Kernel Version [B]7600 [/B]MP (4 procs) Free x64
Built by: [B]7600[/B].17017.amd64fre.win7_gdr.120503-2030
System Uptime:[B]0 days 8:21:21.533[/B]
BugCheck Code: [B]BugCheck D1, {1, 2, 8, 1}[/B]
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by :[B]ntkrnlmp.exe ( nt!KiPageFault+260 )[/B]
BugCheck Info: [B]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/B]
PROCESS_NAME: [B]System[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
FAILURE_BUCKET_ID: [B]X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260[/B]
  BIOS Version                  0501   
  BIOS Release Date             08/03/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep 27 13:23:45.392 2012 (UTC - 4:00)**************************
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Thu Sep 27 13:23:45.392 2012 (UTC - 4:00)**************************
[COLOR=RED][B]ASACPI.sys                  Sun Mar 27 22:30:36 2005 (42476C4C)[/B][/COLOR]
nvmf6264.sys                Thu Jul 30 19:48:18 2009 (4A723142)
nvstor64.sys                Tue Aug  4 20:31:07 2009 (4A78D2CB)
viahduaa.sys                Mon Jan 11 05:05:18 2010 (4B4AF7DE)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvstor.sys                  Fri Mar 19 16:45:11 2010 (4BA3E257)
MpFilter.sys                Thu Aug 23 19:03:14 2012 (5036B6B2)
nvlddmkm.sys                Thu Aug 30 11:50:16 2012 (503F8BB8)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Sep 26 23:56:52.268 2012 (UTC - 4:00)**************************
MpFilter.sys                Fri Mar  9 06:05:26 2012 (4F59E3F6)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Sep 25 16:09:52.686 2012 (UTC - 4:00)**************************
[COLOR=RED][B]amdxata.sys                 Tue May 19 13:56:59 2009 (4A12F2EB)[/B][/COLOR]
[COLOR=RED][B]nvstor.sys                  Wed May 20 02:45:37 2009 (4A13A711)[/B][/COLOR]
nvmf6264.sys                Thu Aug 12 07:46:06 2010 (4C63DEFE)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Sep 24 05:17:30.769 2012 (UTC - 4:00)**************************
[COLOR=RED][B]nvlddmkm.sys                Thu May 14 16:48:07 2009 (4A0C8387)[/B][/COLOR]
[/font]

Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed

 

[SimbaTao]

Thanks, I will go take a look at those and get it as you request. I also need to add that this is all from after my re-install of Windows 7, I had a previous one running before the 24 of Sept. when these BSoD's (there were 7 minidumps then and at that point, and I erroneously deleted them with the re-format) had started, and at that time I did, in fact have those along with PCprobe installed and it happened anyway. My Windows at that time was updated probably more than 130 times too! In any case I will do these updates and get back to you as soon as it is done, I cannot express my gratitude to you all for your help!

Edit 1: I have tried to do a windows update and I get this response:
Link Removed

I am not sure how to proceed with getting more windows updates?

 

[usasma]

If it says there aren't any more updates, then there must not be any more updates!
Don't worry about it as long as you've checked.

Once we rule out all of these 3rd party driver things, then we'll move on to hardware diagnostics (which, from your description, is where I suspect that the problem lies). I'll ask you to start with these free diagnostics: Link Removed - Invalid URL

 

[SimbaTao]

I figured that , I just wanted to keep you in the loop about what I am doing.

I am re-downloading the chipset driver (I have installed the same one yesterday) and also grabbing nForce 630a drivers, and while I wait I went to Kingston to look up the memory timing thing you spoke of. I, for the life of me cannot find anything that pertains to my ram nevermind what the best timing settings would be, again I am not sure how to proceed? Thanks again for your help and any you can give!

Edit: I have updated the drivers that came from this page, It seems that Nvidia's drivers match for the same chips as the chipset drivers I had gotten from Asus, yesterday, so I am wondering if I should leave it like it is or look for more?

. The Nvidia drivers had uninstalled what I had and replaced them (It seems, anyway, it had to reboot 3 times and asked me if I wanted to remove the old, so I am guessing it did)


I included the updated driver list from W7f Diagnostic Tool/DRIVER LIST button to see if I got those right? If you need any other files to check, let me know. I am not sure if you want me to sit on what we've done so far, and see if I get another blue screen? Or go ahead now and start with the Hardware Diagnostics? Again you have my deep appreciation for your time and assistance, so thank you!

Edit 2: I have found the pdf for my ram and I have attached it here in case it's any help to you or anyone else looking for it. After reading it, I really didn't know what I was supposed to change in the BIOS. So what I did was go into the BIOS and see what I could do. The settings available were:
Memclock Mode: (Manual/Auto) I set to 'Manual'
Memclock Value: (Came up after I set the above to Manual) various voltage choices, I set to '667Mhz'
DRAM Timing (Auto/DCT0/DCT1/Both) I didn't know what this meant so left it at 'Auto'
memory over Voltage: (Auto/ Or type in value) I also didn't know what to set this at, so left it at 'Auto'

I hope I got this right as I am no guru when it comes to RAM, although I wonder after this war with my machine I will end up being one
Thanks again for your time and for reading this post!

Edit 3: Hardware Diagnostics; Memtest86+ I have ran a 7 hour test with this last night. No errors found. I am going to try the next on the list. Thanks!

 

[usasma]

Right now I'd suggest posting in the hardware forums for advice about the memory settings: Link Removed due to 404 Error

Those are the most recent drivers for your chipset - so go ahead and install them anyway (in case there's corruption in the currently installed drivers). But note that the drivers were issues just after SP1 came out - and haven't been updated since.

Now we wait for further BSOD's
If there's still 3rd party driver issues, we'll work on them.
If there isn't - we move on to the hardware diagnostics. If you have some spare time you can start the hardware diagnostics now in order to get a head start on them.

Good luck!

 

[SimbaTao]

Okay, thanks usasma, I'll try that. So far so good b.t.w. but it's gone about this long before and crashed so we'll see (knocking wood). Again the memory ran for a long time on the test and passed. I will leave it like it is, go see if I can find something about the timing, and hope. Otherwise if anything goes ka-put I will let you know. Again, I can't thank you enough for your time and effort to help!
EDIT 1: New Attachment: Oh well that wasn't long. I was on steam and BAM then I did the report, and while I was trying to type this before BAM! so I am trying again. Here's the report.

 

[usasma]

Looks like hardware to me.
Please run all of the diagnostics here: Link Removed - Invalid URL
If that doesn't find anything, then start with the hardware stripdown: Link Removed

Have you ever flashed the BIOS on your motherboard? I ask because it's version 0501 - but it dates from August 3, 2010
The date of the 0501 version on the Asus website is December 31, 2009
Are you confident in your ability to perform a BIOS update or two on your motherboard? If done incorrectly you can destroy your motherboard. It's fairly safe if done according to the directions, but it is very unforgiving of any mistakes!.

There are 6 different updates available - I'd suggest (at a minimum) doing the 3rd (0804) and then the 6th one (1301).

At some point we may be looking at a clean Windows install - so please be prepared for that. Instructions on a CLEAN install are here: Link Removed - Invalid URL We can do that at any time after you finish the first set of diagnostics, please let us know what you want to do.

Analysis:
The following is for information purposes only.

[font=lucida console]**************************Fri Sep 28 15:45:20.694 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092812-15724-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:07:07.255[/B]
BugCheck Code: [B]BugCheck A, {20, 2, 0, fffff8000288e12e}[/B]
*** ERROR: Module load completed but symbols could not be loaded for ndiswan.sys
*** ERROR: Module load completed but symbols could not be loaded for raspppoe.sys
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by :[B]ndiswan.sys ( ndiswan+16ebc )[/B]
BugCheck Info: [B]IRQL_NOT_LESS_OR_EQUAL (a)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME: [B]iexplore.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xA_ndiswan+16ebc[/B]
  BIOS Version                  0501   
  BIOS Release Date             08/03/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep 28 15:29:24.144 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092812-14991-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:15:26.315[/B]
BugCheck Code: [B]BugCheck C2, {7, 109b, 0, fffffa8007292570}[/B]
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264 )[/B]
BugCheck Info: [B]BAD_POOL_CALLER (c2)[/B]
BUGCHECK_STR:  0xc2_7_Ntfx
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]Torchlight2.ex[/B]
FAILURE_BUCKET_ID: [B]X64_0xc2_7_Ntfx_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264[/B]
  BIOS Version                  0501   
  BIOS Release Date             08/03/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep 28 15:06:06.069 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092812-17721-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 16:00:38.630[/B]
BugCheck Code: [B]BugCheck 50, {fffff88007718064, 1, fffff8000288c7d3, 0}[/B]
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by :[B]ntkrnlmp.exe ( nt!KiScanReadyQueues+197 )[/B]
BugCheck Info: [B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: [B]SearchIndexer.[/B]
FAILURE_BUCKET_ID: [B]X64_0x50_nt!KiScanReadyQueues+197[/B]
  BIOS Version                  0501   
  BIOS Release Date             08/03/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Sep 28 15:45:20.694 2012 (UTC - 4:00)**************************
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Fri Sep 28 15:45:20.694 2012 (UTC - 4:00)**************************
[COLOR=RED][B]AsUpIO.sys                  Sun Jul  5 22:21:38 2009 (4A515FB2)[/B][/COLOR]
ASACPI.sys                  Wed Jul 15 23:31:29 2009 (4A5E9F11)
nvmf6264.sys                Thu Jul 30 19:48:18 2009 (4A723142)
nvstor64.sys                Tue Aug  4 20:31:07 2009 (4A78D2CB)
viahduaa.sys                Mon Jan 11 05:05:18 2010 (4B4AF7DE)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvstor.sys                  Fri Mar 19 16:45:11 2010 (4BA3E257)
AsIO.sys                    Thu Apr 22 07:18:03 2010 (4BD0306B)
MpFilter.sys                Thu Aug 23 19:03:14 2012 (5036B6B2)
nvlddmkm.sys                Thu Aug 30 11:50:16 2012 (503F8BB8)
[/font]

Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed

 

[SimbaTao]

I have flashed a BIOS before, but when I did it was on a Packard Bell with 300 Cyrix cpu and an Award BIOS, running Windows 98 SE
I really haven't needed to since then, so I have an idea about the basics, or what I learned then.

I don't have a floppy drive or a USB drive, though, so if I do flash it, I will need to probably make a Fat 32 partition or use a cd? Can I use a DVD/RW for it? I am not sure if there's a way to do it right off my HDD? I am nervous and unsure which is the best way without those?

What I have read (and I have been reading a lot since this started), is that there is some problems using a BIOS-rom from NTFS. I have also got the original cd for the motherboard, I hope it has something to set itself back if something happens.

I need to add some things I stated in the first post so we are caught up together about what I have tested on my hardware so far. I have switched from USB to a ps/2 mouse, and I may also go get a ps/2 keyboard from somewhere to check if there's anything on the USB connection.

I have also switched from the onboard graphics chip to the GPU on the PCIe card. In either of those cases, it did the same blue screen thing.

I think because of that, that the issue isn't with the video card, maybe I am wrong but it's seems as a control test it says anything burning my video card would.

I also tested the ram for 7 hours straight on memtest86+ and it gave no errors. I'll test it again, of course, but at this point, I think I should try other stuff first, if that makes sense?

I have read up on the carona site about what is entailed in a hard drive diagnostic here, and from my Link Removed, I realize that I may lose what's on my hard drive, I will disconnect the IDE drive before I start, and leave it off to see if it blue screens or not without it.

As for installing Windows goes I have been doing it since Windows 95, and it was easier back then with simple tricks like /fdisk and /sys C: .

I only went through the process with Windows 7 once, I did Vista, once, as well & I also have done Windows XP more than a few times on my last rig.

I will try and run the test I found Link Removed: for my hard drive.
I wonder if I can't use the cd test on a dvd/r or preferrably a dvd/rw, as I have no blank CD's around?
I'd also like to know if the Windows test on that site would be enough either?

If I lose my data I can re-install Windows 7, according to Link Removed - Invalid URL instructions and see if it helps.

If you, or anyone knows anything about flashing this motherboard they can add some more sage about what I should be careful of. Thanks again for all your time and help!

 

[usasma]

I'm late for work right now, but wanted to add some comments first

Read the BIOS instructions at the Asus website. Recently (the last year or two) I've been doing Asus BIOS flashes with their Asus Update utility from within Windows. And, knock on wood, I'm very lucky to have never experienced a problem with flashing a BIOS - but I still get nervous each and every time!

I've never lost data with a hard drive test and have been doing it many times a week for the last 6 years.
I do not like the Western Digital Data Lifeguard Test (although I am a fan of their hard drives). If the test acts up on you, try the Seagate SeaTools test. If that gives problems, then try the Hitachi Drive Fitness Test (the last one works best on IDE drives).

We use DVD's at work (because CD's are getting harder and harder to find). As long as you have a burning program that'll do it, DVD's will work (we use Roxio at work).

The best advice about BIOS flashing that I've seen is to sit on your hands during the flash. That way you won't be tempted to press a key to see if things are working. Beyond that, do it at a time of day when it's least likely to have a power failure. Keep animals and small children out of the room when doing the flash. Don't move around or do anything - just sit still. For example, if you get up and trip over the power cord - that's not good!

But once it's over the testing (of the flash) is easy - if it boots, you're successful. As I said before, it's not a hard procedure - it's just that it's unforgiving of any mistakes.

Good luck!

 

[SimbaTao]

Thanks for the advice ususma! I am going to try the windows one then, if you have had luck with it maybe I can

lo' and behold, however, all this time I have the model number of my motherboard wrong. (just a bit!) It seems my motherboard is M4N68T-M V2 and I have been using the downloads for M4N68T-M ..oops?

I am looking at the drivers there, and they are mostly all slightly newer versions. I am going to uninstall what I have so far and replace them with everything on the V2 page (exception the nForce drivers, I got those right off nVidia's website). Is this a good idea?

The audio drivers are newer as are some of the utility downloads.

My main question is that there are different BIOS here, no 804 (yikes huh?) I would like to know what you think the best choice to update the BIOS to, 702, 901, or 1001? ... and when I do this, do I have to go in 2 steps like ..to '804 then to1301'? I am really sorry for messing this up, it was right in front of me when I look at cpu-z read out.

If it's any prize, I have used the stuff on the non- V2 page for over a year, until recently, without any problems, maybe I was just lucky up until now.

As always, any help you give on this is extremely appreciated, so thank you!

 

[usasma]

It's been recommended to me to go in steps of 2 or 3 when updating BIOS.
I'd say that going straight to 1001 would be your best bet

There is no 1301 on the v2 page.
Make darned sure that you have the right model before attempting the flash! (it's possible that flashing with the wrong model number can damage your motherboard!
Look at the motherboard and physically write down the model number.

Good luck!

 

[SimbaTao]

I am sorry for being such a bonehead.. it really did work for over a year with what I downloaded at that page... I guess the reason I figured it out this time, is you are recommending that I flash my BIOS to see if it's the problem, that's sage too! I knew there were updates for it a long time ago, but wisdom told me not to update unless I had to, since we are running out of things it could be, I am gonna do it, but I understand the weight of it too... I think because that, I was double checking everything before I got started, and there it was.. pays to be sure, right?
anyway, thanks for the wishes and even more thanks for the time you give, I will let you know how it goes.. I just got Torchlight II last week, and it's hard not to play it

 

[usasma]

We all make mistakes - don't worry about it!
Just FYI - I usually recommend triple-checking anything to do with BIOS flashing (it comes from my medical training of counting prescriptions out 3 times).

 

[SimbaTao]

So I had some really nasty bumps today. I lost what was on the SATA drive, and maybe (haven't put it back in yet) what was on the IDE. I am now also running my old version of Windows XP 32bit. I have managed to get the graphics card back in and it seems to work, though I haven't had time to try or even install any games yet. I have XP updated until it won't anymore with SP3.

I have MSE installed updated and did a scan and it seems ok as well. I have updated my chip set drivers but it was tricky, I suppose, because it feels kind of scary right now that it's gonna ka-pow at any given second.

I had to install XP because I was getting blue screens from Windows 7 during the install... My mother board flashed itself once off a reboot, to the default BIOS on the cd that came with it.

At one point I was going to boot with an old DOS disk I made with Windows 98 and do /fdisk partition on the hard drive, as I couldn't seem to do that right with Windows 7.. got stuff to learn there still methinks?

I want to eventually get a partition on it (or if it's the culprit for all that has happened, a new one) with FAT32. Maybe I can store the BIOS there if things go south like they did today. I never did get a chance to flash the BIOS yet, though, so the only flash for it today is the CD one.

It seems to have passed by my being here to type this I guess?

It's been a long day, with it at least able to get online at this point, I am mildly relieved, though I have much to do still, to get it back like it was.

I am thinking to leave the XP installed and try for a Windows 7 64 bit on the same drive, on a different partition, make it dual boot so if one goes down I can switch it while I am trying to get mess back together.

I need to gather some resources for making the partitions I want. I haven't done it for a while so I need to freshen up. Once I have 2 good partions (maybe 3, one FAT32, if I can pull it off), I will then try and re-install Windows 7 on a separate partition.

I guess because that means until then, I am now a Windows XP user & this doesn't belong here. I will get back here as soon as I get all the above (or a reasonable attempt to get Windows 7) and let you know how it goes.

In summation though, maybe XP will help me find what is causing all this ruckus. Thanks again for all you have done and your time usasma. I am really glad I found this place!

 

[usasma]

BSOD's during install are usually a sign that either the hardware is bad - or the installation media (DVD/USB) is bad.

Motherboards aren't supposed to flash themselves - so I have to wonder about the motherboard. Since we were looking at hardware problems, it's possible that they were caused by the motherboard.

But, it's a bit confusing if XP is working OK - so I'd be cautious. Don't just go out and replace the motherboard - but keep it in mind if the XP install doesn't work over the long run. Installing a dual boot with Win7 might be the best option right now.

Good luck!

 

[SimbaTao]

Thanks again for all your help John! Sorry for the thread necrology, it took me this long to get what I thought I needed, a new Link Removed - Invalid URL.
It's only been 5 days, but it seems to be okay now. I have my Windows 7 64 bit re-installed, with that partition I was wanting and will also add a version of Win XP later just in case. I had a bsod problem a while back and the way the crashes were happening was a lot like then, that time it was my ram, so I suppose if I learned anything from this (besides hating asus now) it's that ram crashes are very similar to mobo crashes... either way I am happy (so far) with this newer board and I hope this will be the end of my troubles for now.
Again, I can't thank you enough for all the time you invest in helping people here!