Random BSOD - Fresh install, fresh system

[p1tcho0]

in order to minimize potential problems it's always best to use ram qualified for your board and make sure all Bios settings are correct for voltage timings and speed.

Also just because something is new does not mean it's good I get defective parts shipped to me more than you could imagine.

there is always potential for damage when you plug in the wrong power connectors be very careful about that.

Also just because something is new does not mean it's good I get defective parts shipped to me more than you could imagine.

OKay


there is always potential for damage when you plug in the wrong power connectors be very careful about that.[/QUOTE]

Im think can be but in the board of day we got Protection about Low high voltage etc...

 

[p1tcho0]

Im not engineer ....

 

[pete256]

Heya, i think i might be able to shed some light on this one for you

How big is your page file?? if you are getting a PFN_list error, it could be pointin towards that??

Your page file should be 1.5 times the size of your ram that is one thing you could try

Im still testing the Nvidia driver your suggested, so far with the older drivers i havent had any problems

 

[computersplus]

Heya, i think i might be able to shed some light on this one for you

How big is your page file?? if you are getting a PFN_list error, it could be pointin towards that??

Your page file should be 1.5 times the size of your ram that is one thing you could try

Im still testing the Nvidia driver your suggested, so far with the older drivers i havent had any problems

as long as it's system managed it should be fine but if a custom size was set to begin with then yes have a look

 

[ManOwar2]

Can someone explain to me...

why did it go throught 5 full pass without any error, then suddenly I open my screen, on the 6th pass, test 7, error start to appear at the same time I press ESC to leave...

is my memory really faulty ? Or is it just normal or something ?

If my mobo is faulty, how can I be able to do all the things I did in one week with my computer...(intense gaming, intense download/upload, dualscreen with hdtv for many hours...) and all that without any crash ?

I dont know what to do really. sending back both the RAM and mobo as RMA is the last option I want to think about, but the sellor has to received it back before the 29th, so my deadline is to send back thoses item by expresspost next monday morning, and it will probably cost me lot !!!

Is there anything else I can do ? What are the chances my mobo is faulty anyway ?

Did the SCandisk result I posted above tell you something about what is really he problem ? (software...memory, or mobo ???)

I must admit I'm confuse and a bit mad about all this.

Thanks to your help everyone, again.

 

[Pauly]

It can sometimes take multiple passes to bring out an error its just the nature of the beast, the more memory the longer it takes.

It can be frustrating and quite time consuming, the normal procedure in this circumstance would be to test one stick at a time with multiple passes to be sure

 

[ManOwar2]

Hi. I have installed a whole new windows 7 pro x64. My new mobo an ASus p5e3 pro along with new ram pc12800 gskill 2x2 ddr3 (running in 1066mhz due to my q6600)

Everythingi s running perfectly...except some random BSOD. 4 total this week.

I have posted a pack of dump file in here, the last 4 ones are the ones that represent the 4 BSOD I had and that I cannot explain.

the others ones are for various reasons, crashes who happenned during installation but that I was able to resolve.



What is weird is that my BSOD only happenned when I was surfing explorer on when the CPU was idle at night, with utorrent running.


today mc pc got BSOD at 11:54 AM after 1 night or running perfectly. it is open since then and running perfectly again.

All the afternoon for 4 hours it loaded utorrent, I cam back from the university and started to play empire total war and lot of MW2 multiplayer.

Everything is working perfectly, no BSOD !! But I'm afraid to leave my pc open this night...when the BSOD happen I usually have to reboot manually because if it reboot by itself it lead to a DOS screen saying to select a boot device.


Help me someone... I cannot believe me G-skill memory are faulty, otherwise they would have failed in-game.

I suspect nvidia drivers 195.62 can be responsible for thoses bluescreen. The power management tool is not working properly and whatever the option I choose in the nvidia panel it will sometimes lower my frequencies and sometimes it will keep the stock one.

A strange thing also is that my CPU is lowering it's speed in a kind of power saving option, but I turned intel speedstep off so it should not do it should it ?

IS there a problem running pc12800 in 1066 mhz ? I do not want to maintain my FSB to north bridge to 400mhz all the time cause it heat my system a lot. I use that function from time to time for hard gaming sessions. (crysis for example)

PLease help !

Thanks for your help already.

Hi and welcome

these crashes were all caused by memory problems.

I would download memtestx86 and run it for 5 passes
run a system file check type cmd in search>right click and run as an admin>
sfc /scannow

If you are overclocking STOP

010910-19328-01.dmp    1/9/2010 7:16:18 AM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    ataport.SYS    ataport.SYS+15580                    x64        C:\Users\K\Desktop\New folder (3)\010910-19328-01.dmp    4    15    7600    
011110-15818-01.dmp    1/11/2010 11:43:11 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00000403    fffff680`00015b90    86400000`b5b9a82d    fffff8a0`0a34fb22    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (3)\011110-15818-01.dmp    4    15    7600    
011210-17674-01.dmp    1/12/2010 10:44:11 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00000403    fffff680`0001eb90    a9400000`32f45867    fffff680`000504ea    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (3)\011210-17674-01.dmp    4    15    7600    
010910-14336-01.dmp    1/9/2010 7:29:54 AM    NTFS_FILE_SYSTEM    0x00000024    00000000`001904fb    fffff880`061cfff8    fffff880`061cf850    fffff800`026ea9ba    Ntfs.sys    Ntfs.sys+213d8                    x64        C:\Users\K\Desktop\New folder (3)\010910-14336-01.dmp    4    15    7600    
010810-19936-01.dmp    1/8/2010 11:00:11 PM    PFN_LIST_CORRUPT    0x0000004e    00000000`00000099    00000000`00062850    00000000`00000002    00000000`0006284f    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (3)\010810-19936-01.dmp    4    15    7600    
011410-14679-01.dmp    1/14/2010 11:09:45 AM    PFN_LIST_CORRUPT    0x0000004e    00000000`00000007    00000000`000ba2fb    00000000`000b8aa4    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (3)\011410-14679-01.dmp    4    15    7600    
011510-16426-01.dmp    1/15/2010 11:54:28 AM    PFN_LIST_CORRUPT    0x0000004e    00000000`00000099    00000000`0003adb4    00000000`00000002    00000000`0003adaf    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (3)\011510-16426-01.dmp    4    15    7600    
010910-10686-01.dmp    1/9/2010 6:40:07 AM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`02682105    fffff880`0475d000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder (3)\010910-10686-01.dmp    4    15    7600

Let us know the results


Ken J+

Can you please interpret my scandisk information... I must know.

I'm now clueless about what to do. I'm afraid of the possiblity my mobo may be broken...but people in general around me told me it is rare such thing happen even with the weird situation that happenned during the installation (misplugged a pci express in the 4-pin lol)


Please help. I switch my ram to slot 2 and 4 and I will test, If I find error again, then it is mostly my ram I guess.




NOTE : Memtest86 v 3.5 would not work for some reaons. In single core version, it would constantly reboot my cpu after the test 0.

In multicore (experimental) it would kinda freeze at test 1.

Version 3.4 did work...thought at some points when testing memory it wrote down : pass 104%.... the memtest was analyzing a memory range that I do not have ! (from 4096 to 4884)

IS it normal ? mobo or ram problem ?

 

[ManOwar2]

I have run now the memtest86+ 4.0

I did switch the two 2x2 gig to the slot 2 and 4 (using 1 and 3 before)

I found that this test is much more faster. It also found 8 error at first pass, test 5.

My ram is faulty right ?

 

[ickymay]

I have run now the memtest86+ 4.0

I did switch the two 2x2 gig to the slot 2 and 4 (using 1 and 3 before)

I found that this test is much more faster. It also found 8 error at first pass, test 5.

My ram is faulty right ?

Difficult to be sure from a distance but I would say yes your RAM is bad

you can damage ram with static when you fit it but in this case the fact that the RAM isnt listed as being compatible with this mobo is another clue that it's causing your issues

your first minidumps of 4 days ago showed as being caused by memory errors and there has been nothing since to suggest any different

 

[ManOwar2]

I have run now the memtest86+ 4.0

I did switch the two 2x2 gig to the slot 2 and 4 (using 1 and 3 before)

I found that this test is much more faster. It also found 8 error at first pass, test 5.

My ram is faulty right ?

Difficult to be sure from a distance but I would say yes your RAM is bad

you can damage ram with static when you fit it but in this case the fact that the RAM isnt listed as being compatible with this mobo is another clue that it's causing your issues

your first minidumps of 4 days ago showed as being caused by memory errors and there has been nothing since to suggest any different

SO you do not think my mobo is faulty right ? What are the chances that would happen ? You think my little misplug's experience with my bro might have damaged the board ?

I guess probably not, and I'm now convinced my memory is faulty. But I'm still in doubt at some point about the motherboard.


Thanks for all your help. All of you are great people, helping others like that for free is something awesome. Hope you all get some rewards for that !!!

I already placed an RMA with newegg where I got the ram and they wont charge me restocking fee.

I will also buy a QVL listed ram, even thought is cost more, it has better timming and since it is QVL I can expect it to work properly I guess !


Do you think it can be a problem for me to have a 2x2 gig of 1600mhz memory running in 1066 mhz (because of my q6600) ? I've been told it is ok to do that since most rams are configured like that, but I'm never sure enough.

 

[ickymay]

But I'm still in doubt at some point about the motherboard.

Thanks for all your help. All of you are great people, helping others like that for free is something awesome. Hope you all get some rewards for that !!!

I already placed an RMA with newegg where I got the ram and they wont charge me restocking fee.

I will also buy a QVL listed ram, even thought is cost more, it has better timming and since it is QVL I can expect it to work properly I guess !


Do you think it can be a problem for me to have a 2x2 gig of 1600mhz memory running in 1066 mhz (because of my q6600) ? I've been told it is ok to do that since most rams are configured like that, but I'm never sure enough.

when you get your new ram if you still get the same errors and bsod then you can start thinking you may have a mobo problem

always try to buy listed ram if you can , it's another small guarantee in an unsure world

There is no reason why you shouldn't run 2x2gig ram, but buy it all at the same time from the same firm, as the cost of metals change so components get built to different tolerances and ram can vary :huh:

 

[ManOwar2]

But I'm still in doubt at some point about the motherboard.

Thanks for all your help. All of you are great people, helping others like that for free is something awesome. Hope you all get some rewards for that !!!

I already placed an RMA with newegg where I got the ram and they wont charge me restocking fee.

I will also buy a QVL listed ram, even thought is cost more, it has better timming and since it is QVL I can expect it to work properly I guess !


Do you think it can be a problem for me to have a 2x2 gig of 1600mhz memory running in 1066 mhz (because of my q6600) ? I've been told it is ok to do that since most rams are configured like that, but I'm never sure enough.

when you get your new ram if you still get the same errors and bsod then you can start thinking you may have a mobo problem

always try to buy listed ram if you can , it's another small guarantee in an unsure world

There is no reason why you shouldn't run 2x2gig ram, but buy it all at the same time from the same firm, as the cost of metals change so components get built to different tolerances and ram can vary :huh:

I'm buying a package of 2x2 so it's not a problem.

However, this is 1600mhz ram, I want to run in in 1066, is it a problem ?

Thanks.

Here is also my dump file for this morning BSOD...IRQ_Not less than equal...what is that ?

 

[zigzag3143]

But I'm still in doubt at some point about the motherboard.

Thanks for all your help. All of you are great people, helping others like that for free is something awesome. Hope you all get some rewards for that !!!

I already placed an RMA with newegg where I got the ram and they wont charge me restocking fee.

I will also buy a QVL listed ram, even thought is cost more, it has better timming and since it is QVL I can expect it to work properly I guess !


Do you think it can be a problem for me to have a 2x2 gig of 1600mhz memory running in 1066 mhz (because of my q6600) ? I've been told it is ok to do that since most rams are configured like that, but I'm never sure enough.

when you get your new ram if you still get the same errors and bsod then you can start thinking you may have a mobo problem

always try to buy listed ram if you can , it's another small guarantee in an unsure world

There is no reason why you shouldn't run 2x2gig ram, but buy it all at the same time from the same firm, as the cost of metals change so components get built to different tolerances and ram can vary :huh:

I'm buying a package of 2x2 so it's not a problem.

However, this is 1600mhz ram, I want to run in in 1066, is it a problem ?

Thanks.

Here is also my dump file for this morning BSOD...IRQ_Not less than equal...what is that ?

Hi

As before Memory corruption

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\012110-14539-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a68000 PsLoadedModuleList = 0xfffff800`02ca5e50
Debug session time: Thu Jan 21 10:36:58.572 2010 (GMT-5)
System Uptime: 0 days 0:06:42.601
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff68000106570, 0, 0, fffff80002aedae2}

Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff68000106570, memory referenced
Arg2: 0000000000000000, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002aedae2, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d100e0
 fffff68000106570 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiAgeWorkingSet+1c2
fffff800`02aedae2 488b19          mov     rbx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  SearchIndexer.

TRAP_FRAME:  fffff880033167a0 -- (.trap 0xfffff880033167a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff68000106570
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aedae2 rsp=fffff88003316930 rbp=0000000000106570
 r8=0000000000000001  r9=fffffa800685d958 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiAgeWorkingSet+0x1c2:
fffff800`02aedae2 488b19          mov     rbx,qword ptr [rcx] ds:fffff680`00106570=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ad9469 to fffff80002ad9f00

STACK_TEXT:  
fffff880`03316658 fffff800`02ad9469 : 00000000`0000000a fffff680`00106570 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03316660 fffff800`02ad80e0 : 00000000`00000000 00000980`00000000 00000000`00001000 fffff800`02c0cbfe : nt!KiBugCheckDispatch+0x69
fffff880`033167a0 fffff800`02aedae2 : 00000003`00000000 4e000000`ae04e867 00000000`00000000 00000000`00000ce0 : nt!KiPageFault+0x260
fffff880`03316930 fffff800`02b5aa0e : fffffa80`0685d958 fffff880`00000001 00000000`00000001 fffff880`03316bb0 : nt!MiAgeWorkingSet+0x1c2
fffff880`03316ae0 fffff800`02aee6e2 : 00000000`00000193 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03316b80 fffff800`02aee96f : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316bd0 fffff800`02d7d166 : fffffa80`039ecb60 00000000`00000080 fffffa80`0396d9e0 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316d40 fffff800`02ab8486 : fffff880`02f63180 fffffa80`039ecb60 fffff880`02f6dfc0 00200008`80000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03316d80 00000000`00000000 : fffff880`03317000 fffff880`03311000 fffff880`03316710 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+1c2
fffff800`02aedae2 488b19          mov     rbx,qword ptr [rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+1c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1c2

BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1c2

Followup: MachineOwner
---------

 

[Pauly]

Nothing new in that dump 0xA blames memory corruption

 

[ManOwar2]

This mean my memory is faulty I guess. I'm in process of RMA. I'm also buying new QVL ram.

can someone just confirm again that using memory that is downclocked is not a problem ?

 

[ickymay]

This mean my memory is faulty I guess. I'm in process of RMA. I'm also buying new QVL ram.

can someone just confirm again that using memory that is downclocked is not a problem ?

yes it should be no problem

I have to say that armed with a limited amount of facts or even if i held them all I personally can't offer you the guarantees you seem to be asking for

 

[ManOwar2]

This mean my memory is faulty I guess. I'm in process of RMA. I'm also buying new QVL ram.

can someone just confirm again that using memory that is downclocked is not a problem ?

yes it should be no problem

I have to say that armed with a limited amount of facts or even if i held them all I personally can't offer you the guarantees you seem to be asking for

I got that. Thanks.

Pretty sure it isnt a problem. As soon as I get my QVL ram, I will format, clean install, and if you see another post from me with an attached files, I will be probably crying.

lol

Still, now I have a pretty good idea what to do. And it is all because of you guys.

I know it's probably my ram, it's a kind of relief in a certain way. I just hope my Mobo is not in fault. If it's the case, I'm gonna throw it away, and I'll bring back my mobo with my old OCZ ram, 3 years old ram that never had a single problem and I'll buy a whole new system in december.

It's been a pain in the ass from the beginning. Hopefully new ram will mean problem solved.

Thanks again to everyone, and sorry for always disturbing you with my many questions.

 

[computersplus]

i know people will want to lynch me for saying this but get something besides an Asus board their boards aren't that great

 

[ManOwar2]

i know people will want to lynch me for saying this but get something besides an Asus board their boards aren't that great

In december 2006, I bought a P5W DH deluxe by asus. it costed me 300$ back then.

It's the best motherboard I ever owned. I did many upgrade on it and it would take everything I thrown at it.

Never had a single blue screen in 3 years of heavy use.

Of course, it's more than the double I paid for the one I hve now...I guess it make a difference.

Next time I,ll throw in 100$ more for the mobo and I'll make sure I have a premium or a deluxe one if I buy from asus.

Still, I think my ram is faulty and I also think my Mobo dot no like that ram, even if it was not faulty.

I'm buying QVL ram in 2 days, when I receive it I'll send back the RMA one. (newegg gave me until february 20th for them to receive it) So I'm less in a panic now, this mean I wont spend 2 weeks without a computer.

I'm just afraid there is a chance my mobo is faulty and that I'll have to replace it thought. (let's hope not, some computers geek at my job told me it is unlikely that my mobo is faulty in my situation I described them)

My friends will bring some generic ddr3 ram this week end we will test it on it.

But I'm afraid my Mobo wont like it and I think I might get memtest error. Is it possible in this situation that memtest86+ 4.0 detect error but that the cause is the mobo not liking the ram ???


Wich mobo you would suggest me for my Q6600 and some ddr3 ?

I know socket 775 is disapearing...but my q6600 still rock even in heavy gaming so I do not want to change it for now.

 

[computersplus]

depends on your budget