Several crashes (BSoD) urgent help

juFo · 04-01-2009, 06:13 AM

Dear,

I'm having some BSoD for some months now. I really don't know what's causing the bluescreens.

I have removed VGA, did memtest86+ on both RAM, tested them together and also one by one, but they didn't gave any errors (I runned it a whole night). Installed brand new Vista 64bit with SP1 Business edition english.

Bluescreens that I have had:
MEMORY_MANAGEMENT 0x0000001A

IRQL_NOT_LESS_OR_EQUAL 0x0000000A (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xFFFFF80001E95D25)

PFN_LIST_CORRUPT 0x0000004E (0x000000000000009A, 0x0000000000000000, 0x0000000000000002, 0x0000000000000000)

The most time I have had the 0x1A and 0xA BSoD. The memtest86+ didn't find any errors so it's strange that I have memory BSoD's.
BIOS reset also didn't work, disabling HD Audio in BIOS also not.

FYI:

Sometimes I can work 1 or 2 weeks with my pc without bluescreens and othertimes I have 2 or 3 bluescreens in 30minutes. Really strange.

PSU: AOpen Model NO.: Z400-08FC (400W PEAK)

I really hope somebody could tell me what's going on.

Many thanks already that you want to look at my problem and I hope it will get fixed.

juFo · 04-01-2009, 02:09 PM

anybody who had already a look?

**jcgriff2** · 04-01-2009, 03:35 PM

Hi -

Ran 14 dumps. Bugchecks -

Code:


BugCheck 4E, {9a, 0, 2, 0}
Probably caused by : memory_corruption
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {0, 2, 1, fffff80001e95d25}
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+45 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1A, {8884, fffffa8000d1a3f0, fffffa8000d1e950, 300}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+a2 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1A, {8886, fffffa8000d1a3f0, fffffa8000d1a5d0, 200}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+9078 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1A, {8884, fffffa8000d1a3f0, fffffa8000d1a4b0, 405}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+a2 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+119 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {fffffa85b7dc301a, 2, 1, fffff80001ca08eb}
Probably caused by : memory_corruption ( nt!MiDeleteSegmentPages+14b )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {fffffa901a1b601a, 2, 1, fffff80001c948eb}
Probably caused by : memory_corruption ( nt!MiDeleteSegmentPages+14b )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {fffffa85fd6b281b, 2, 0, fffff80001c6f393}
Probably caused by : memory_corruption ( nt!MiUpdatePfnPriorityByPte+11b )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {fffffa8e8a41801b, 2, 0, fffff80001c8532c}
Probably caused by : volsnap.sys ( volsnap!VspOptimizeDiffAreaFileLocation+400 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {fffffa9006eed01a, 2, 0, fffff80001cbc44f}
Probably caused by : memory_corruption ( nt!MiFlushSectionInternal+2df )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {fffffa91581a701a, 2, 1, fffff80001caa8eb}
Probably caused by : memory_corruption ( nt!MiDeleteSegmentPages+14b )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {fffffa912bf1801a, 2, 0, fffff80001cbf44f}
Probably caused by : memory_corruption ( nt!MiFlushSectionInternal+2df )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {fffffa7fffffffd0, 2, 0, fffff80001cf7cf2}
Probably caused by : memory_corruption ( nt!MiRemoveStandbyPage+82 )

.

0x4e = corrupt page fram number list. 1st parm 0x9a = driver tried to free locked page

0X1a = severe memory mgt issue. 1 dump shows 1st parm 0x41287 = internal memeory management structures are corrupted

0xa = kernel mode driver access paged memory when it should not have (IRQL too high)

Your system is Core 2 Quad - w/ 2GB RAM

Code:

Processor	Intel(R) Core(TM)2 Quad CPU    Q6600  
@ 2.40GHz, 2394 Mhz, 4 Core(s), 4 Logical Processor(s)

You need to run memtest86+, 1 stick at a time, alternate slots. I really would put 4GB RAM in x64 system.
http://www.memtest.org/

Run chkdsk /r on HDD

You can run driver verifier & see if anything there, but I'm not too optomistic as I see this as hardware failure. Although, I do see McAfee running - a problematic child that can cause BSODs all on its own. Verifier -
START | type cmd.exe | right-click on cmd.exe uptop under programs | Run as Administrator | type verifier & hit enter - the Verifier screen will appear | do the following:

Code:


1. Select 2nd option - Create custom settings (for code developers)
2. Select 2nd option - Select individual settings from a full list.
3. Check the boxes• Special Pool 
• Pool Tracking 
• Force IRQL checking
• Deadlock Detection4. Select last option - Select driver names from a list 
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where Microsoft is not the Provider
7. Click on Finish 
8. Re-boot

If the Driver Verifier (DV) finds a violation, it will result in a BSOD. You may have to boot into SAFEMODE (select Last Known Good Configuration) or perform a system recovery to log back on. To see the status of Verifier - type verifier - select the last option on the first screen - "Display information about the currently verified drivers..". To turn Driver Verifier off - verifier /reset then re-boot.

If you get a BSOD, get the Verifier-enabled Vista dump file, attach to post and I'll take a look at it.

This driver interests me - best I can find out is that it belongs to Office - but I have Office 2007 on this x64 system and don't have this driver. So I am unsure what it is for. I have no indication from dumps that it played a role in BSODs, either.

Code:

osaio.sys    Wed Feb 14 04:20:09 2007 (45D2D449)

More detailed bugcheck summary below; dbug logs attached.

Regards. . .

jcgriff2

.

EDIT:

Quote:

Originally Posted by juFo

PSU: AOpen Model NO.: Z400-08FC (400W PEAK)

.

Does this mean you have a 400w PSU? If so, you are underpowered.

JC

.

.

bugcheck summary

Code:


Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Tue Mar 31 11:45:42.648 2009 (GMT-4)
System Uptime: 0 days 0:22:57.497
BugCheck 4E, {9a, 0, 2, 0}
Probably caused by : memory_corruption
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Tue Mar 31 11:19:47.769 2009 (GMT-4)
System Uptime: 0 days 0:09:57.492
BugCheck A, {0, 2, 1, fffff80001e95d25}
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+45 )
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Tue Mar 31 10:03:22.473 2009 (GMT-4)
System Uptime: 0 days 6:36:31.573
BugCheck 1A, {8884, fffffa8000d1a3f0, fffffa8000d1e950, 300}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+a2 )
PROCESS_NAME:  logon.scr
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Thu Mar 26 16:10:04.511 2009 (GMT-4)
System Uptime: 0 days 2:10:16.280
BugCheck 1A, {8886, fffffa8000d1a3f0, fffffa8000d1a5d0, 200}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+9078 )
PROCESS_NAME:  audiodg.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Thu Mar 26 06:59:20.829 2009 (GMT-4)
System Uptime: 0 days 0:21:12.630
BugCheck 1A, {8884, fffffa8000d1a3f0, fffffa8000d1a4b0, 405}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+a2 )
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Wed Mar 18 07:51:40.827 2009 (GMT-4)
System Uptime: 0 days 2:31:32.046
BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+119 )
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Tue Mar 17 13:58:20.983 2009 (GMT-4)
System Uptime: 0 days 0:07:02.771
BugCheck A, {fffffa85b7dc301a, 2, 1, fffff80001ca08eb}
Probably caused by : memory_corruption ( nt!MiDeleteSegmentPages+14b )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Tue Mar 17 13:37:12.438 2009 (GMT-4)
System Uptime: 0 days 0:05:57.223
BugCheck A, {fffffa901a1b601a, 2, 1, fffff80001c948eb}
Probably caused by : memory_corruption ( nt!MiDeleteSegmentPages+14b )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Tue Mar 17 13:30:33.072 2009 (GMT-4)
System Uptime: 0 days 3:55:44.881
BugCheck A, {fffffa85fd6b281b, 2, 0, fffff80001c6f393}
Probably caused by : memory_corruption ( nt!MiUpdatePfnPriorityByPte+11b )
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Tue Mar 17 09:34:01.634 2009 (GMT-4)
System Uptime: 0 days 3:34:26.555
BugCheck A, {fffffa8e8a41801b, 2, 0, fffff80001c8532c}
Probably caused by : volsnap.sys ( volsnap!VspOptimizeDiffAreaFileLocation+400 )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Wed Mar 11 07:04:47.439 2009 (GMT-4)
System Uptime: 0 days 1:32:42.146
BugCheck A, {fffffa9006eed01a, 2, 0, fffff80001cbc44f}
Probably caused by : memory_corruption ( nt!MiFlushSectionInternal+2df )
PROCESS_NAME:  DfrgNtfs.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Tue Mar 10 12:34:30.779 2009 (GMT-4)
System Uptime: 0 days 3:14:13.753
BugCheck A, {fffffa91581a701a, 2, 1, fffff80001caa8eb}
Probably caused by : memory_corruption ( nt!MiDeleteSegmentPages+14b )
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Tue Mar 10 09:19:22.229 2009 (GMT-4)
System Uptime: 0 days 0:42:28.077
BugCheck A, {fffffa912bf1801a, 2, 0, fffff80001cbf44f}
Probably caused by : memory_corruption ( nt!MiFlushSectionInternal+2df )
PROCESS_NAME:  VSSVC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Tue Mar 10 06:24:07.295 2009 (GMT-4)
System Uptime: 0 days 1:05:05.041
BugCheck A, {fffffa7fffffffd0, 2, 0, fffff80001cf7cf2}
Probably caused by : memory_corruption ( nt!MiRemoveStandbyPage+82 )
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


by       jcgriff2

juFo · 04-02-2009, 01:59 AM

first of all: thanks already!!
I'll check everything.

Quote:

This driver interests me - best I can find out is that it belongs to Office - but I have Office 2007 on this x64 system and don't have this driver. So I am unsure what it is for. I have no indication from dumps that it played a role in BSODs, either.

I don't have any office installed

Quote:

I do see McAfee running - a problematic child that can cause BSODs all on its own.

without mcafee I had it also after a complete format

Quote:

Does this mean you have a 400w PSU? If so, you are underpowered.

Why can I use my pc for 1 week without BSoD, playing battlefield-heroes, watching a 720p blueray movie etc. (sometimes it fails but sometimes I can use it 1 week or little bit more without a bluescreen).
This is my current PSU: http://www.obcs.nl/sitemap/Aopen_PSU...04400_A310.php
What do you recommend as PSU (how many Watt)?

What should I do with osaio.sys ?

EDIT:
Is my RAM type ok for my motherboard?
I have 2x 1GB UNB PC2-6400 CL5 Apacer

Lots of questions, I hope I don't disturb you that much

Thanks

**jenae** · 04-02-2009, 02:25 AM

Hi, upgrade your ram to 4gb AND most definitely get the best power supply you can over 50% of problems can be slated home to PS problems. 400 is most likely only 300 at the moment, it is one of the most underrated hardware issues in a computer. I would not have anything less then a true 650 W or better for ANY vista .

juFo · 04-02-2009, 05:47 AM

Quote:

Originally Posted by jcgriff2

This driver interests me - best I can find out is that it belongs to Office - but I have Office 2007 on this x64 system and don't have this driver. So I am unsure what it is for. I have no indication from dumps that it played a role in BSODs, either.

Code:

osaio.sys    Wed Feb 14 04:20:09 2007 (45D2D449)

I found in C:\Program Files (x86)\Intel\Intel Desktop Utilities the following osaiodll.dll
and in C:\Windows\System32\drivers i found osaio.sys
It's probably for the intel desktop utilities (used to check my mobo temperature and voltage)

http://www.spywaredata.com/spyware/m...awtray.exe.php
http://lus.tallemu.com/oasis2/file/o...aio_sys/101516

chkdsk /r ran without problems.

Verifier is active now..

**jcgriff2** · 04-02-2009, 08:22 AM

Hi -

No such thing as too many questions in my book. That is how we learn - from those who have been there before. If I can't answer your questions, I'll certainly do my best to try and find someone that can.

I see the driver is in an Intel folder and based on your statement, I'm sure it is just fine. The name was unknown to me and I tend to look for older drivers in the dump logs. It looked out of place, so I looked it up and found conflicting information. Many of the search hits I read said it was a Microsoft Office driver, but then a check here found nothing so I asked about it. Its location and purpose seem credible. If there are any major problems with it, the driver verifier should flag it. But I believe it is OK. To reiterate - nothing in the dump pointed at that driver as a contributing factor to BSODs. Just my curiosity.

You can let the verifier run its course if you would like, but as I mentioned and jenae from our Hardware Forum confirmed, you are indeed in need of a new PSU. jenae is the hardware expert here, not I. I am unable to offer an opinion as to the type of PSU you should get - but I would advise following jenae's advice on the wattage.

As for the RAM - how many slots do you have? I would think a 2 x 2GB configuration is OK, and with x64 you may want to go higher if the finances are in place to do so.

As far as the time lapse between BSODs, this is what I found in the dumps -

Code:


 Date of     Number of     System Up-time 
  DATE         BSODs      Low         High  
——————————————————————————————————————————————————————
March 10        3       42 min      3.25 hours
March 11        1       1.5 hours       --      
March 17        4       6 min       7.01 hours
March 18        1       2.5 hours       --
March 26        3       21 min      3.6 hours    
March 31        4       9 min       9.9 hours

Very, very few BSODs follow patterns and are usually seemingly random. It may at times appear that a certain game, app or activity causes a BSOD. Usually I see such when directly related to a single driver that starts in sequence (like a boot driver causing BSODs every time at 40 seconds after power-up) or possibly a specific device that you turn on or plug in and results in a BDOS. Vista has > 50 processes running at any given time and when the system is either idle or resources free up, Vista's Task Scheduler will begin running house keeping activities that may use the Internet. So one never really knows exactly what is going on in the background. The system is NEVER "idle". Like the Perfect Storm, when all is aligned just right (or wrong) a BSOD is imminent.

In your case, the fact that you had hours of BSOD free time may have been due to the fact that you were using the system and it could not perform some intensive scheduled activity. There simply is no formula. The varying bugchecks and lack of a 3rd party driver named as the probable cause points to unknown hardware failure. The dumps are unable in most cases to tell us the exact piece of hardware that is failing.

Lastly - Mcafee. If you have the McAfee firewall, I would seriously think about getting rid of the product. 3rd party firewalls are a prime BSOD-causing candidate. They interfere with Vista system services by blocking local ports and many times escape detection after a crash. McAfee may very well be responsible for the 0xa and 0x4e BSODs. But I rarely see 0x1a caused by these Internet Security packages. Even the 0xa and 0x4e are more indicative of hardware than software. I would suggest that you use Windows Firewall, Windows Defender (or similar spyware product) and 1 anti-virus product. In have no issues with McAfee anti-virus - just its firewall.

Please let me know how things turn out. Feel free to post back with any questions.

I would ask that any Hardware specialists seeing this to make recommendations on the type of RAM you should purchase for your system. I can only tell you it should be at least 4GB and matched.

Regards. . .

jcgriff2

.

**simpswr** · 04-02-2009, 10:55 AM

What brand and model is this pc?

Do you have SP1 installed?

Your Power supply looks to be seriously underpowered . . See this for how to select a good one

Power Supply Information and Selection

For your memory, as cheap is it is these days, I would replace the two sticks of "no-name" you have now with a quility set like this:

http://www.newegg.com/Product/Produc...82E16820148160

juFo · 04-03-2009, 02:44 AM

my pc is not a brand pc, I bought all parts myself. In the .NFO document you can find the specifications (and it has vista x64 business english with SP1)

I guess I will order a new PSU and new memory (2x 2GB) but I might need some help.

This is the shop where I will buy my things: http://www.jaha.be/index.php I have 100euro - 120 euro to spend I guess for RAM and PSU together.

PSU:
http://www.jaha.be/index.php?cPath=3...c9fd9a399fee99
Tell me, which one will do for my pc?
(this is my current one so it needs to fit in my AOpen case: http://www.obcs.nl/sitemap/Aopen_PSU...04400_A310.php)

MEMORY:
I have the INTEL DG33FB motherboard ( manual)
on page 13 there is:

Quote:

To be fully compliant with all applicable Intel ® SDRAM memory specifications, the board should be populated with DIMMs that support the Serial Presence Detect (SPD) data structure. If your memory modules do not support SPD, you will see a notification to this effect on the screen at power up. The BIOS will attempt to configure the memory controller for normal operation. The Desktop Board supports the dual or single channel memory configurations defined below.
• Four 240-pin Double Data Rate 2 (DDR2) SDRAM Dual Inline Memory Module
(DIMM) connectors with gold-plated contacts.
• Support for:
- Unbuffered, non-registered single or double-sided DIMMs
- Non-ECC DDR2 memory
- DIMM Type and Timings listed below:

Type Timing
DDR2-800 5-5-5 or 6-6-6 only
DDR2-667 5-5-5 only

- Serial Presence Detect (SPD) memory only
- Memory configurations listed below:

• Up to 2.0 GB utilizing 256 Mb technology
• Up to 4.0 GB utilizing 512 Mb or 1 Gb technology
• Up to 8.0 GB utilizing 1 Gb technology

On page 34 in the manual there is more about memory.

But like the manual said:

Quote:

If your memory modules do not support SPD, you will see a
notification to this effect on the screen at power up. The BIOS will attempt to configure the memory controller for normal operation.

When I boot I see in the right bottom corner 2 numbers changing (the screen where you can press F2 to go into BIOS), could that be the effect described in the manual? My current RAM is: 2x 1GB UNB PC2-6400 CL5 Apacer (no idea if that supports SPD or if it's ok for my motherboard).

Now with all this in mind, what should I buy from here (2x 2GB):
http://www.jaha.be/index.php?cPath=2...c9fd9a399fee99

These 2 are in promotion now (dropped in price) but I don't know if they have the right specifications for my motherboard or if there are other better ones:
http://www.jaha.be/product_info.php?products_id=3835
and
http://www.jaha.be/product_info.php?products_id=4042

(sorry that the website is in Dutch but on the left side you find the different brands below each category. Geheugen = Memory; Voedingen = Power Supplies; )

I hope you guys can help me out for about 100-120 euro's at that shop and that I can order it this weekend and use my pc without bluescreens.

FYI:
- I have McAfee VirusScan Enterprise 8.7.0i (not the firewall)
- I did chkdsk /r
- Verifier is running but I didn't have any bluescreens till now... should I reset it again?

- Question: If I have new RAM, what should I do with my old RAM: 2x 1GB UNB PC2-6400 CL5 Apacer (2x 1GB + 2x 2GB or only 2x 2GB?) (if first option: in what channels should I place the 2GB and the 1GB)

Many thanks already for your time and help jcgriff2, jenae and simpswr !!

**simpswr** · 04-03-2009, 06:30 AM

For the Power Supply, I would choose between these:

OCZ 600 Watt GameXStream voeding
PC P&C Silencer 610 EPS12V

Both are good, I would choose the best you can afford.

For more information on Power Supply selection see this:

Power Supply Information and Selection

Quote:

Now with all this in mind, what should I buy from here (2x 2GB):
http://www.jaha.be/index.php?cPath=2...c9fd9a399fee99

These 2 are in promotion now (dropped in price) but I don't know if they have the right specifications for my motherboard or if there are other better ones:
http://www.jaha.be/product_info.php?products_id=3835
and
http://www.jaha.be/product_info.php?products_id=4042

The second memory looks the best :

http://www.jaha.be/product_info.php?products_id=3835

Mushkin is a good brand and the specs are within the motherboard specs.

Quote:

- Question: If I have new RAM, what should I do with my old RAM: 2x 1GB UNB PC2-6400 CL5 Apacer (2x 1GB + 2x 2GB or only 2x 2GB?) (if first option: in what channels should I place the 2GB and the 1GB)

I would put your existing memory in a drawer somewhere until you can verify that was the problem. The board manual should be marked which 2 memory slots are to be used first it's usually the two that are the closest to the CPU.

juFo · 04-06-2009, 02:53 AM

I ordered the suggested memory and changed the PSU into this one:
http://www.seventeam.com.tw/product_...cid=37&pid=419

Now waiting for the hardware (will get it next week normally) and installing it :)

**simpswr** · 04-06-2009, 07:22 AM

Let us know how it turns out

juFo · 04-14-2009, 03:22 AM

To keep you up2date:
I installed the new PSU and memory (4GB). Untill now I didn't have any bluescreens but with the other hardware it could take a week before receiving one.. I hope it will be fixed :)

tnx already!

x!Blade · 04-14-2009, 05:07 AM

I am to haveing A simlar problem!

Read my Post!!!!! i NEED help!!!!

http://www.techsupportforum.com/micr...-crashing.html

04-01-2009, 02:09 PM	#2 (permalink)
juFo Registered User Join Date: Apr 2009 Posts: 9 OS: Windows Vista x64 SP1 Business english	Re: Several crashes (BSoD) urgent help anybody who had already a look?

04-02-2009, 02:25 AM	#5 (permalink)
jenae Mentor Hardware Team Join Date: Jun 2008 Posts: 1,308 OS: XP & Vista	Re: Several crashes (BSoD) urgent help Hi, upgrade your ram to 4gb AND most definitely get the best power supply you can over 50% of problems can be slated home to PS problems. 400 is most likely only 300 at the moment, it is one of the most underrated hardware issues in a computer. I would not have anything less then a true 650 W or better for ANY vista . __________________

04-02-2009, 08:22 AM	#7 (permalink)
jcgriff2 Moderator, Microsoft Supp Join Date: Sep 2007 Location: The Great State of New Jersey - away from the gross corruption of the Riverside County, CA, SO office. SHAMEFUL ! Posts: 10,137 OS: Windows 7, Vista Ultimate My System	Re: Several crashes (BSoD) urgent help Hi - No such thing as too many questions in my book. That is how we learn - from those who have been there before. If I can't answer your questions, I'll certainly do my best to try and find someone that can. I see the driver is in an Intel folder and based on your statement, I'm sure it is just fine. The name was unknown to me and I tend to look for older drivers in the dump logs. It looked out of place, so I looked it up and found conflicting information. Many of the search hits I read said it was a Microsoft Office driver, but then a check here found nothing so I asked about it. Its location and purpose seem credible. If there are any major problems with it, the driver verifier should flag it. But I believe it is OK. To reiterate - nothing in the dump pointed at that driver as a contributing factor to BSODs. Just my curiosity. You can let the verifier run its course if you would like, but as I mentioned and jenae from our Hardware Forum confirmed, you are indeed in need of a new PSU. jenae is the hardware expert here, not I. I am unable to offer an opinion as to the type of PSU you should get - but I would advise following jenae's advice on the wattage. As for the RAM - how many slots do you have? I would think a 2 x 2GB configuration is OK, and with x64 you may want to go higher if the finances are in place to do so. As far as the time lapse between BSODs, this is what I found in the dumps - Code: Date of Number of System Up-time DATE BSODs Low High —————————————————————————————————————————————————————— March 10 3 42 min 3.25 hours March 11 1 1.5 hours -- March 17 4 6 min 7.01 hours March 18 1 2.5 hours -- March 26 3 21 min 3.6 hours March 31 4 9 min 9.9 hours Very, very few BSODs follow patterns and are usually seemingly random. It may at times appear that a certain game, app or activity causes a BSOD. Usually I see such when directly related to a single driver that starts in sequence (like a boot driver causing BSODs every time at 40 seconds after power-up) or possibly a specific device that you turn on or plug in and results in a BDOS. Vista has > 50 processes running at any given time and when the system is either idle or resources free up, Vista's Task Scheduler will begin running house keeping activities that may use the Internet. So one never really knows exactly what is going on in the background. The system is NEVER "idle". Like the Perfect Storm, when all is aligned just right (or wrong) a BSOD is imminent. In your case, the fact that you had hours of BSOD free time may have been due to the fact that you were using the system and it could not perform some intensive scheduled activity. There simply is no formula. The varying bugchecks and lack of a 3rd party driver named as the probable cause points to unknown hardware failure. The dumps are unable in most cases to tell us the exact piece of hardware that is failing. Lastly - Mcafee. If you have the McAfee firewall, I would seriously think about getting rid of the product. 3rd party firewalls are a prime BSOD-causing candidate. They interfere with Vista system services by blocking local ports and many times escape detection after a crash. McAfee may very well be responsible for the 0xa and 0x4e BSODs. But I rarely see 0x1a caused by these Internet Security packages. Even the 0xa and 0x4e are more indicative of hardware than software. I would suggest that you use Windows Firewall, Windows Defender (or similar spyware product) and 1 anti-virus product. In have no issues with McAfee anti-virus - just its firewall. Please let me know how things turn out. Feel free to post back with any questions. I would ask that any Hardware specialists seeing this to make recommendations on the type of RAM you should purchase for your system. I can only tell you it should be at least 4GB and matched. Regards. . . jcgriff2 . __________________ . . . . . . . . BSOD Posting Instructions B Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread Glad to be home in the Great State of New Jersey ! !

04-02-2009, 10:55 AM	#8 (permalink)
simpswr Moderator Hardware Team Join Date: May 2007 Location: Houston, Texas Posts: 12,274 OS: XP, Vista, Win 7	Re: Several crashes (BSoD) urgent help What brand and model is this pc? Do you have SP1 installed? Your Power supply looks to be seriously underpowered . . See this for how to select a good one Power Supply Information and Selection For your memory, as cheap is it is these days, I would replace the two sticks of "no-name" you have now with a quility set like this: http://www.newegg.com/Product/Produc...82E16820148160 __________________ Rich MemTest86 \| BenchTest \| Virus/Trojan/Spyware Help How to post a Screen Shot \| PC running slow? Last edited by simpswr; 04-02-2009 at 10:58 AM.

04-06-2009, 02:53 AM	#11 (permalink)
juFo Registered User Join Date: Apr 2009 Posts: 9 OS: Windows Vista x64 SP1 Business english	Re: Several crashes (BSoD) urgent help I ordered the suggested memory and changed the PSU into this one: http://www.seventeam.com.tw/product_...cid=37&pid=419 Now waiting for the hardware (will get it next week normally) and installing it :)

04-06-2009, 07:22 AM	#12 (permalink)
simpswr Moderator Hardware Team Join Date: May 2007 Location: Houston, Texas Posts: 12,274 OS: XP, Vista, Win 7	Re: Several crashes (BSoD) urgent help Let us know how it turns out __________________ Rich MemTest86 \| BenchTest \| Virus/Trojan/Spyware Help How to post a Screen Shot \| PC running slow?

04-14-2009, 03:22 AM	#13 (permalink)
juFo Registered User Join Date: Apr 2009 Posts: 9 OS: Windows Vista x64 SP1 Business english	Re: Several crashes (BSoD) urgent help To keep you up2date: I installed the new PSU and memory (4GB). Untill now I didn't have any bluescreens but with the other hardware it could take a week before receiving one.. I hope it will be fixed :) tnx already!

04-14-2009, 05:07 AM	#14 (permalink)
x!Blade Registered User Join Date: Apr 2009 Location: Rotherham Posts: 12 OS: Windows Vista Home Premium	Re: Several crashes (BSoD) urgent help I am to haveing A simlar problem! Read my Post!!!!! i NEED help!!!! http://www.techsupportforum.com/micr...-crashing.html