Been having BSOD issues, like many on here.

[Jonathan_King]

A 365MB dump is a full kernel dump. Please upload it to Rapidshare.

RapidShare: 1-CLICK Web hosting - Easy Filehosting

 

[Eternal]

Ok, that is wha ti thought but was not sure. Here is the link for it

RapidShare: 1-CLICK Web hosting - Easy Filehosting

 

[cluberti]

Question - did this start happening recently?

// PFN listed as corrupt:
3: kd> !pfn 000000000000bfce
    PFN 0000BFCE at address FFFFFA800023F6A0
    flink       0000BFD0  blink / share count 0000BFCD  pteaddress FFFFF8A0090EFFB1
    reference count 0000    used entry count  0000      Cached    color 0   Priority 1
    restore pte FA8005F3F88004C0  containing page        1259C5  Standby    MP      
    Modified Shared            

// As per the list, the previous and next PFNs:
3: kd> !pfn 000000000000bfd0  
    PFN 0000BFD0 at address FFFFFA800023F700
    flink       0000BFDA  blink / share count 0000BFCE  pteaddress FFFFF8A0090F0650
    reference count 0000    used entry count  0000      Cached    color 0   Priority 1
    restore pte FA8005F3F88004C0  containing page        0306C6  Standby     P      
      Shared            

3: kd> !pfn 000000000000bfcd
    PFN 0000BFCD at address FFFFFA800023F670
    flink       0000BFCE  blink / share count 0000BFCC  pteaddress FFFFF8A0090BC668
    reference count 0000    used entry count  0000      Cached    color 0   Priority 1
    restore pte FA800493CED004C0  containing page        12A2F7  Standby     P      
      Shared            

// This BIOS has been very recently updated:
3: kd> !sysinfo smbios
[SMBIOS Data Tables v2.4]
[DMI Version - 36]
[2.0 Calling Convention - No]
[Table Size - 2820 bytes]

[BIOS Information (Type 0) - Length 24 - Handle 0000h]
  Vendor                        Award Software International, Inc.
  BIOS Version                  F9
  BIOS Starting Address Segment e000
  BIOS Release Date             06/28/2010    // <- less than 1 month ago
  BIOS ROM Size                 100000

I ask if this started recently, because I notice that the BIOS had been updated recently. I'm not sure if you did this as a result of the problem or not, but looking at the call stack this crash is a result of deleting a PFN from the list (MiDeletePfnList) which is not seen in the stack, but it runs as a result of MiDeleteAddressesInWorkingSet (and would be seen before MiBadShareCount). In looking at the memusage command, it showed indeed 434 bad PFNs, and these spanned the active list, standby, and the zero PFN list. At this point, if it's not a BIOS issue, it's likely bad hardware (RAM likely if that's the case).

 

[Eternal]

Well it was happening more often when i hade the ram running the 1600mhz in the bios, right now its 1333mhz as my board does no support 1600mhz but does support 1666(O.C)mhz. It was happening alot the first time i posted about it so i did a fresh install changed the RAM timings and didnt have a problem untill just recently while installing a game (which iv installed many because of the format). Is there a reason why i can run memtest for 20 hours and get 0 errors? because that leads me to believe that maybe its a bad Mobo/bios. Think i should try reinstalling the bios (my board has dual bios)?

 

[cluberti]

Because memtest is in reality really only testing read/write to each block of memory - it isn't likely to catch timing issues, it won't (well, usually) catch overvoltage or undervoltage issues, and it most certainly doesn't stress the memory enough to catch controller-related issues (especially with mismatched pairs). Software memtesters aren't foolproof, unfortunately. If a stick is physically bad, it'll catch it. If the problem is BIOS timings or incompatibility with two sticks of RAM, that's a lot more likely to go undetected until an OS app, game, etc, stresses it in more real-world ways, where timing can mean the difference between a page being flushed before the OS is done with it or not.

 

[Eternal]

ok i get what you mean. Well to give some more info on it the RAM is
G.Skill DDR3-1600, i have two 2gb sticks in dual channel. Currently running at 1339.4mhz with 9,9,9,24,33 running in 1t command rate, these are within the makers specifications other then the 1T command rate which they dont specifiy which i may change to 2T because really there is no benefit to me for using a 1T rate as all this computer is mainly for is playing video games.


Another crash occured but oddly there is no dump file anywhere created from it.

 

[Eternal]

Don't mean to double post here but i was wondering with all that said my timings are right which could mean that maybe the RAM is just bad but the certain thing that is wrong can not be detected by a program such as memtest? Im just looking for an answer to my above post before i spend any money.