Random Blue Screens on a Fresh Clean install

sujasali · 25 Oct 2009

PCs that are low on memory can decrease performance and leave you frustrated. Windows 7 reduces memory and processor utilization by running fewer background services, reducing the operating system's memory needs when idle, and reducing graphics memory requirements to launch and switch between windows.

And it contains several features and it will be the Most Popular Micorsoft operating system after Windows XP..

More than that all new technologies of microsoft WPF, WCF, Silverlight etc are totally enter into the market and we can cover all obstacles connected with all these technologies using Windows 7.

Really it is the POWER OF SIMPLICITY.

Sujas
Aabasoft

zigzag3143 · 25 Oct 2009

Yane said:

DocBrown said:

Mismatched memory sticks ?

Are all from same manufacturer ? Bought at the same time ?

Doc,

They are not matched. Do you think that is the problem? Two of them are 1 gig each and 2 are 2 gigs.

Thank you again, Doc and Ken

Yane

You can find out if they are mis matched with an app like cpu-z. you can also see if you BSOD with 1 pair out. those dimps are all over the map.

ken

DocBrown · 25 Oct 2009

CPU-z Freeware at MajorGeeks

Yane · 26 Oct 2009

zigzag3143 said:

Yane said:

DocBrown said:

Mismatched memory sticks ?

Are all from same manufacturer ? Bought at the same time ?

Doc,

They are not matched. Do you think that is the problem? Two of them are 1 gig each and 2 are 2 gigs.

Thank you again, Doc and Ken

Yane

You can find out if they are mis matched with an app like cpu-z. you can also see if you BSOD with 1 pair out. those dimps are all over the map.

ken

Hello Ken and Doc,

The memory sticks are not from the same company if that is what you mean by mismatched. I will download and run that program when I get home.

I ran Memtest as requested overnight and it did find errors. Over the course of the night it found 56 of them but it seemed to be repeating the tests so there might be some duplicates.

I am going to try and take out some of the ram and see if that helps. Thank you guys again for all your help,

Yane

Yane · 27 Oct 2009

Memtest running overnight returned a few errors.

Okay, took out two of the memory sticks (the 1 gig ones) and I have not had any blue screens happen today!

I have been running Prime95 and having it stress test the PC tonight and so far, no issues.

I am going to let it run overnight and will let you guys know if it is working.

Thank you again to Ken and Doc for your help, I could not have done it without you,

Yane

usasma · 27 Oct 2009

The sysinfo stuff shows your graphics card as a problem device (NVIDIA GeForce 8800 GT). Please visit the nVidia website and update the drivers to the latest version.

Check you motherboard manufacturer's website for BIOS updates. My son's 8800 required a BIOS flash when I installed it (Asus M2V...)

Your AVG is having problems - this is usually from corruption or malware. I'd suggest downloading a fresh copy of AVG, uninstalling the current copy, then installing and updating the fresh copy. Then perform a scan to be sure that you're clean.

Running 15 memory dumps, will BRB with the results (don't hold your breath, I've got a water leak in the house and the plumber is due any minute).

usasma · 27 Oct 2009

An interesting STOP 0x34 error amidst the rest of the more common bugchecks.
More info on the bugcheck here: BSOD Index

There's a bunch different stuff going on here - so my first idea is to suspect a hardware problem. I can't decide between your memory or your hard drive. But, noticing the results on CPU-Z, I'd have to give the nod to memory issues.

Please run a memory diagnostic on the system. There's a free one here: Memory Diagnostics If you've alread removed some of the sticks you may not see an error - but I'd try it anyway to make sure.

Summary of the memory dumps:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 02:05:41.068 2009 (GMT-4)
System Uptime: 0 days 0:00:26.237
BugCheck 24, {1904fb, fffff88007bfe128, fffff88007bfd980, fffff800028cae9c}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCachedRead+88 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 02:04:13.599 2009 (GMT-4)
System Uptime: 0 days 0:00:22.378
BugCheck 3B, {c0000005, fffff800028c0609, fffff880062e9110, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+159 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 01:27:03.653 2009 (GMT-4)
System Uptime: 0 days 0:19:49.308
BugCheck 1000007E, {ffffffffc0000005, fffff88000e1683a, fffff880031c4518, fffff880031c3d70}
Probably caused by : pci.sys ( pci!PciDevice_Remove+14a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 01:36:25.153 2009 (GMT-4)
System Uptime: 0 days 0:08:27.323
BugCheck 3B, {c0000005, fffff80002b3bfad, fffff880055024c0, 0}
Probably caused by : ntkrnlmp.exe ( nt!EtwpRundownNotifications+19 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 13:30:33.249 2009 (GMT-4)
System Uptime: 0 days 0:06:58.350
BugCheck 1E, {ffffffffc0000005, fffff80002890105, 0, ffffffffffffffff}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGCONTEXT::Initialize+818 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Wow.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 13:22:50.081 2009 (GMT-4)
System Uptime: 0 days 0:00:09.250
BugCheck 50, {fffff08006ed3bc0, 0, fffff800028e9374, 7}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+298e7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 16:22:45.711 2009 (GMT-4)
System Uptime: 0 days 0:17:48.490
BugCheck 3B, {c0000005, fffff8800108bb07, fffff88006de83f0, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltpGetStartingCallbackNode+97 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 15:50:01.437 2009 (GMT-4)
System Uptime: 0 days 0:02:07.606
BugCheck 3B, {c0000005, fffff80002c1e7e9, fffff880046c20f0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+4ee9c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 15:44:38.338 2009 (GMT-4)
System Uptime: 0 days 0:21:13.117
BugCheck A, {28, 2, 0, fffff800028b6090}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 15:46:54.830 2009 (GMT-4)
System Uptime: 0 days 0:01:06.000
BugCheck 34, {50830, fffff8800318c7d8, fffff8800318c030, fffff80002893cdf}
Probably caused by : memory_corruption ( nt!MiCheckControlArea+17f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 19:15:43.106 2009 (GMT-4)
System Uptime: 0 days 2:19:20.275
BugCheck 1000007E, {ffffffffc0000005, fffff80002c0d5b8, fffff880031fc988, fffff880031fc1e0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+17d68 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 16:51:42.847 2009 (GMT-4)
System Uptime: 0 days 0:25:52.017
BugCheck 1E, {ffffffffc0000005, fffff880010bcb07, 0, ffffffffffffffff}
Probably caused by : fltmgr.sys ( fltmgr!FltpGetStartingCallbackNode+97 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 22:07:07.497 2009 (GMT-4)
System Uptime: 0 days 2:22:03.667
BugCheck 24, {1904fb, fffff88006cf63f8, fffff88006cf5c50, fffff8800112e280}
Probably caused by : Ntfs.sys ( Ntfs!NtfsExtendedCompleteRequestInternal+110 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  chrome.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 19:43:04.344 2009 (GMT-4)
System Uptime: 0 days 0:25:39.513
BugCheck 24, {1904fb, fffff8800606c3f8, fffff8800606bc50, fffff800028be5ce}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushUserStream+92 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  VSSVC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Oct 25 14:29:12.929 2009 (GMT-4)
System Uptime: 0 days 0:23:49.098
BugCheck 24, {1904fb, fffff880076b6d38, fffff880076b6590, fffff8000288b536}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

Yane · 27 Oct 2009

usasma said:

The sysinfo stuff shows your graphics card as a problem device (NVIDIA GeForce 8800 GT). Please visit the nVidia website and update the drivers to the latest version.

Check you motherboard manufacturer's website for BIOS updates. My son's 8800 required a BIOS flash when I installed it (Asus M2V...)

Your AVG is having problems - this is usually from corruption or malware. I'd suggest downloading a fresh copy of AVG, uninstalling the current copy, then installing and updating the fresh copy. Then perform a scan to be sure that you're clean.

Running 15 memory dumps, will BRB with the results (don't hold your breath, I've got a water leak in the house and the plumber is due any minute).

Hello John and thank you for your help.

AVG is listed as having problems because Microsoft wanted me to disable all non MS services on boot. So that service was not running and that is why AVG seems to be having issues. I will re-enable the service and see if that helps that.

For the Graphics card, I uninstalled the drivers for that to see if the Video drivers were causing the issue. I was getting blue screens from the very beginning and tried to eliminate the video and sound card drivers.

I tested the computer with just the 2 most recent Ram DIMMs in there (2x2gig Kingston) and it seems to be working. No blue screens yet.

I ran a Stress test / burn in overnight (7.5 hours) using Prime95 and it returned no errors. It reported 0 errors!

It really seems like one of the Ram sticks was bad, but since I was using XP 32 bit, it never used all 6 gigs of RAM.

Thank you again for all the advice.

Yane

dlvonhelf · 06 Nov 2009

I'm definately not a tech person... I came across this thread by search engine. I was having the same problem with random bluescreens, and was receiving many similar fault bucket codes. I saw that you have AVG for anti-virus. I also have AVG. I disabled AVG using the msconfig utility. It's been two days with no bluescreen. Not sure if the current version of AVG is not yet totaly compatable?? Not sure if this is at all any help. Good luck

Random Blue Screens on a Fresh Clean install

Future of Windows 7 ?

Solved! (Hopefully)

I have the same problem....