Random BSOD

Discussion in 'Windows 7 Help and Support' started by noobiesnack, Sep 22, 2011.

  1. noobiesnack

    noobiesnack New Member

    Joined:
    Sep 22, 2011
    Messages:
    16
    Likes Received:
    0
    Random BSOD + System Hangs Even After 3 reinstalls

    I should probably start off with the history of all this. I built the computer myself in February of this year. I accidentally installed x86 version and it ran perfectly fine. Since I didnt really care at the time, I just left it. Then in May, I decided it was time to go to x64 and also upgraded my RAM from 4GB (2x2GB) to 12GB (2x2GB + 2x4GB). Early July I decided a SSD looked good, installed Windows to it and it ran fine until August.

    Sometime in August I started playing a game called APB Reloaded and had crashing issues with the game. Around the same time, I suddenly started getting random BSODs for MEMORY_MANAGEMENT. I ran diagnostics on it and good ol Google. It seemed as though it was just random at the time.

    Jump forward a little more (a good 10 BSODs later) and the beginning of September. I started getting annoyed with the BSODs and started trying to solve the problem. Initially, it was looking as if the problem was pointing at AVAST Anti-Virus. So, naturally I got rid of it and tried MSE. About a day later, I get another BSOD pointing to audio. I updated the Audio. 2 days later I get another BSOD that pointed to faulty Drivers in Windows. I attempted to recover and went another few days dealing with random BSODs. I tried to see if I could recreate them. Failed horribly to recreate.

    I then found a post suggesting to use verifier to overload the windows drives. I attempted it and I immediately crashed before windows loaded. I found out that there was a very old driver in windows and immediately removed it. Tried to see what would happen after that, after I turned off verifier, and got another BSOD. Tried verifier again and got to desktop only for it to crash for page_fault_in_nonpaged_area pointing at the audio drives. Tried to uninstall the audio drives, and ran it again. Still got BSOD for MEMORY_MANAGEMENT.

    Then I seriously thought it might be my memory. I turned the memory diagnostics on, all night on all settings. The results: 19 passes No Errors Detected. I then went to the SSD as the possible cause. Ran every possible HDD utility possible under windows (including a Disk Monitor program) and found 0 Errors. Tried running sfc /scannow, nothing but registry errors that fixed and immediately came back with 0 errors. I then tried to reset all bios settings back to their defaults. I also found, at the time, that I had the onboard graphics enabled and a floppy drive that didnt exist. Also upped my mem speed from 1333 to 1600 during this and pulled the 2x2GB sticks of RAM out. I noticed a huge increase in the speed of the computer (when it was running properly). Gave up at trying when windows decided to BSOD for a random error upon loading firefox.

    At that point I said to hell with it and reinstalled windows (This time using Win 7 Pro x64 with SP1) and had hellva time trying to get it to install. I had to force close the install and then install it to get it to install without closing the disk boot. That was yesterday. Today, everything was running perfectly fine. I was installing all my programs and got all the basic stuff down and everything was stable. I got up to go do some homework on my laptop, which is just a few feet away from my desktop, while windows was rebooting from update installation. I turned and looked and it was on the login screen. I said whatever and continued working on my work.

    About 15 minutes later, the computer suddenly goes blue and I see it out of the corner of my eye... SYSTEM_SERVICE_EXCEPTION. ofc, I went straight to google and started the debugging tools. Since I was on the login screen, there really wasnt too many drivers loaded and no programs running. The debugging tool has IMAGE_NAME: memory_corruption... Google found to be of little help so now I am here...

    Here is the results of the debug tool...

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff80002fe5305, fffff880077f5e30, 0}
    
    Probably caused by : memory_corruption ( nt!MiInsertVadCharges+265 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80002fe5305, Address of the instruction which caused the bugcheck
    Arg3: fffff880077f5e30, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!MiInsertVadCharges+265
    fffff800`02fe5305 480fab02        bts     qword ptr [rdx],rax
    
    CONTEXT:  fffff880077f5e30 -- (.cxr 0xfffff880077f5e30)
    rax=00000000003ff7ea rbx=000007fefd50b000 rcx=0000000000000001
    rdx=fffff70001000000 rsi=0000000000000003 rdi=000007fefd4a0000
    rip=fffff80002fe5305 rsp=fffff880077f6810 rbp=00000000003ff7ea
     r8=00000000000000ef  r9=0000000000000003 r10=fffff70001080078
    r11=fffff880077f6800 r12=0000000000000000 r13=000000000000000f
    r14=0000000000000001 r15=fffffa8009d63b30
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nt!MiInsertVadCharges+0x265:
    fffff800`02fe5305 480fab02        bts     qword ptr [rdx],rax ds:002b:fffff700`01000000=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002fe5305
    
    STACK_TEXT:  
    fffff880`077f6810 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiInsertVadCharges+0x265
    
    
    FOLLOWUP_IP: 
    nt!MiInsertVadCharges+265
    fffff800`02fe5305 480fab02        bts     qword ptr [rdx],rax
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!MiInsertVadCharges+265
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    STACK_COMMAND:  .cxr 0xfffff880077f5e30 ; kb
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x3B_nt!MiInsertVadCharges+265
    
    BUCKET_ID:  X64_0x3B_nt!MiInsertVadCharges+265
    
    Followup: MachineOwner
    
    
    If anything else happens, I will update... If anyone has any thoughts, please share?

    PS. heres the specs:
    Gigabyte 880GMA-UD2H rv 2.2 (built in VGA disabled)
    AMD II x4 645 3.1GHz
    2x2GB Corsair DDR3 and 2x4GB Corsair DDR3 with native 1600 support and same timings
    NVIDIA 430GT with no OC (running Beta driver WQL 285.27) and all 3d support turned off.
    1x40GB Intel SSD with OS
    1x500GB WD Green HDD
    1x256GB Seagate HDD
    1x1TB WD External HDD

    also have 2 old drives (DVD ROM and DVD-RW) that I pulled from an old system.

    Case has plenty of cooling (1 400mm top mounted, 2 120mm HDD fans, and 120mm rear fan) Highest CPU records approx 40C and highest GPU records 59C (when playing EvE Online in station which is GPU intensive)


    Update 1: I managed to get the whole system to lockup from a random error. I could move the mouse around but no programs would respond, including task manager and explorer.exe. I waited a few minutes then just forced it to shut down. I am going to rollback to before I updated and see what happens.


    Update 2: After rolling back and confirming that the system is at least stable, attempted to update selected windows updates. went fine. I then updated to IE9 and upon restart:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41287, 30, 0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46585 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041287, The subtype of the bugcheck.
    Arg2: 0000000000000030
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_41287
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  runonce.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff880083a26e0 -- (.trap 0xfffff880083a26e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002
    rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002f64e85 rsp=fffff880083a2870 rbp=fffff880083a28c0
     r8=fffff80002e0a000  r9=0000000000000001 r10=0000058000000000
    r11=0000000fffffffff r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz ac po nc
    nt!MiResolvePageFileFault+0x1115:
    fffff800`02f64e85 8b4830          mov     ecx,dword ptr [rax+30h] ds:dc4d:00000000`00000030=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002e1d62e to fffff80002e8a640
    
    STACK_TEXT:  
    fffff880`083a2578 fffff800`02e1d62e : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : nt!KeBugCheckEx
    fffff880`083a2580 fffff800`02e8876e : 00000000`00000000 00000000`00000030 00000000`00000000 00000000`80000000 : nt! ?? ::FNODOBFM::`string'+0x46585
    fffff880`083a26e0 fffff800`02f64e85 : 00000000`0022ed56 00000000`00000000 fffff8a0`00004df0 fffff800`02ef3964 : nt!KiPageFault+0x16e
    fffff880`083a2870 fffff800`02efb530 : 000007fe`ff7570b8 fffff683`ff7fbab8 fffffa80`0e85ca58 fffffa80`0c896811 : nt!MiResolvePageFileFault+0x1115
    fffff880`083a29b0 fffff800`02e97979 : fffff880`083a2ae8 ffffffff`ffffffff 00000000`00000100 00000000`00740072 : nt! ?? ::FNODOBFM::`string'+0x399d4
    fffff880`083a2ac0 fffff800`02e8876e : 00000000`00000000 000007fe`ff7570b8 fffff900`c2f2ea01 00000000`00000000 : nt!MmAccessFault+0x359
    fffff880`083a2c20 000007fe`ff6eecf8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`000def70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff6eecf8
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+46585
    fffff800`02e1d62e cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+46585
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a
    
    FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46585
    
    BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46585
    
    Followup: MachineOwner
    
    
    Update 3: Rolled back with success. Installed IE9 again with no problems this time (no changes to install method which further questions wtf is going on). Changed Bios features DRAM to Dual-Channel mode and pulled the 2x2GB sticks out. Seems to be running fine right now, but this issue is so unpredictable... Also doubled checked all connectors to make sure everything is secure in the case.
     
    #1 noobiesnack, Sep 22, 2011
    Last edited: Sep 23, 2011
  2. MikeHawthorne

    MikeHawthorne Essential Member
    Microsoft Community Contributor

    Joined:
    May 25, 2009
    Messages:
    6,051
    Likes Received:
    302
    Hi

    This isn't really my kind of thing but it sounds like some kind of hardware problem to me.

    All I can suggest it that you turn off all start up items that are not essential, unplug all of your USB devices except the mouse and key board.

    I'd even disconnect the CD DVD drives.

    Boot Windows with only the mouse and keyboard and see if it will stay running.

    If you still get the Blue screen then I'd try removing half of the ram, and try it.

    If it crashes take out that half and put in the ones that weren't in last time.

    I don't think this is software related unless you have some really bad drivers for something and that doesn't seem likely.

    I know this isn't a very definitive answer, but it's all I can think of.

    If nothing works then I'd try sticking in any other hard drive you have laying around and see if your hard drive is some how the problem.

    I don't know much about SSDs but I have seen a lot of posts from people having strange problems with them.

    Mike

    Check out this post on another forum.

    http://forums.pcper.com/showthread.php?t=447852
     
    #2 MikeHawthorne, Sep 23, 2011
    Last edited: Sep 23, 2011
  3. noobiesnack

    noobiesnack New Member

    Joined:
    Sep 22, 2011
    Messages:
    16
    Likes Received:
    0
    Thank you for the reply,

    The problem is the issue is random... It will pop out of no where. I have attempted to recreate the same things that were going on when the crash occurred with no luck. I even left my computer on for 24 hours straight with 2 high end games running and nothing. (only to get one 10 minutes after I get back, shut down 1 game and start playing the other)

    Right now, I am trying your idea of just 2 memory sticks. Now I get to play the waiting game to see what happens while I still try and install more stuff...

    And yeah, I would think it was a SSD problem, but according to SMART data, there are no recorded errors anywhere in the system. I have, however, had windows somehow go corrupt and start trying to recover (Saying that there is inconsistencies in the drive only to find 0 problems)

    Also, it doesnt help that this problem began slowly. Windows runs perfectly fine on fresh install, but it seems when I try to update things go bad. Also, I forgot to add, the reason why I got the SSD in the first place was because of an issue I was having where windows refused to start after a rogue driver got installed and I said F it and got the SSD. It hasnt had any actual file problems when it comes to read/write but windows is throwing random stuff at me.

    If it happens again, I will probably try the 2GB sticks and see what happens... after that, idk...
     
  4. MikeHawthorne

    MikeHawthorne Essential Member
    Microsoft Community Contributor

    Joined:
    May 25, 2009
    Messages:
    6,051
    Likes Received:
    302
    Have you check component temperatures.

    There's a free program called HWMonitor that I use.
    gives temps fans speed etc.

    I remember a post from someone whose SSD was getting to 200 degrees or something like that and causing crashes.

    Mike

    CPUID - System & hardware benchmark, monitoring, reporting
     
  5. noobiesnack

    noobiesnack New Member

    Joined:
    Sep 22, 2011
    Messages:
    16
    Likes Received:
    0
    All temps are good. the highest I get is 58C (about 140) on my GPU when running at max, all disks keep cool temps, CPU never gets above 45C
     
  6. MikeHawthorne

    MikeHawthorne Essential Member
    Microsoft Community Contributor

    Joined:
    May 25, 2009
    Messages:
    6,051
    Likes Received:
    302
    Hi again.

    I don't have any other ideas, I'm sure this is hardware related some how, but I don't have a clue what it is.

    There's no reason that you should have problems with a fresh install of Windows 7 unless there is some kind of hardware issue.

    I beat my computer to death, run everything imaginable, install and uninstall software endlessly and Windows 7 always keeps working. It's really pretty resistant to damage.

    Maybe someone else here has a suggestion but I've run out of ideas, I'm not really a hardware guy, I don't build my own computers like a lot of the people here.

    I'm a big fan of Falcon Northwest I let them worry about the hardware and testing. LOL

    Mike

    Check out this link, I'm not sure if this has anything you can use or not but it's worth a look...

    http://www.tomshardware.com/forum/236623-45-windows-constant-blue-screens
     
    #6 MikeHawthorne, Sep 23, 2011
    Last edited: Sep 23, 2011
  7. noobiesnack

    noobiesnack New Member

    Joined:
    Sep 22, 2011
    Messages:
    16
    Likes Received:
    0
    Update: not sure what happened, but after running windows update, Windows got to the login screen, I attempted to log in, and it went into a system hang and refused to respond at that point. I tried to restart, windows failed to load. I forced shut down the computer and booted cold, windows loaded perfectly fine with no problems. At this point I am pretty sure my problem is hardware related that triggers when something in Windows Update attempts to load a drive, but where? Memory? GPU? Mobo (Bad Bios settings?) ? Hard Drives? Disk Drives?

    List of updates that were installed before problem occurred (this time):
    KB2507618
    KB2518869
    KB2532531
    KB2536276
    KB2570947

    Driver installed: Microsoft Bluetooth (I dont have a bluetooth adapter???)

    Please note: No BSODs since memory pulled but did have the system hang mentioned above.

    PS. I also seem to have both Skype.exe and Trillian.exe become non-loadable after doing a windows update when I simply restart for the update. It goes to running fine after I restart the system with a cold boot. Could this be a sign pointing to either the HDD, Mobo, or Memory?


    Also, I had forgot to mention: the only thing that truely runs on the SSD are the required drives for windows. All App Data folders, all User folders, and all program files are stored in D: Drive which is the 500GB Internal WD Green. Active@ montitor shows Health at 97% and SSD shows health at 100% (aka no read/write errors in SMART data) Shouldnt having 0 read/write errors mean there is no problems with the HDD itself?

    Anyway... I have thought about trying to run drive verifier in an attempt to see what happens. Which I think I might just do for the hell of it
     
    #7 noobiesnack, Sep 23, 2011
    Last edited: Sep 23, 2011
  8. noobiesnack

    noobiesnack New Member

    Joined:
    Sep 22, 2011
    Messages:
    16
    Likes Received:
    0
    Yeah, I was thinking the same thing but where lies the problem is what I cannot figure out. Windows on a fresh install runs perfectly fine up until the point I try to install windows updates. Almost everytime I try to update, something goes wrong somewhere along the line and windows gets pissed at me and either starts to BSOD or get random hangs. At this point, I have thought about just using the System Image I created before I installed the first Windows Update and then never update windows and see what happens. I am still at a loss.

    Thank you for the attempt at helping, I am mostly looking for an outside opinion on what else to try.
     
  9. MikeHawthorne

    MikeHawthorne Essential Member
    Microsoft Community Contributor

    Joined:
    May 25, 2009
    Messages:
    6,051
    Likes Received:
    302
    This is a long shot but could you make a system image of your laptop with all the updates and load it on your PC.
    Are they running the same version of Windows?

    Mike
     
  10. noobiesnack

    noobiesnack New Member

    Joined:
    Sep 22, 2011
    Messages:
    16
    Likes Received:
    0
    Sadly, no. the laptop is running Win 7 HP 32 bit while the desktop is running Win 7 Pro 64 bit.

    At this point, I cannot get IE9 to even launch and when I try to roll back, I get a 'Failure to uninstall'


    Update: I decided to re-image the system back to before I installed any updates. I am going to install all my programs and all utilities that are no longer going to be installed. After I confirm that its running stable at that point, I think I am going to try windows update. If I start having problems after that, well then idk.
     
    #10 noobiesnack, Sep 23, 2011
    Last edited: Sep 23, 2011
  11. noobiesnack

    noobiesnack New Member

    Joined:
    Sep 22, 2011
    Messages:
    16
    Likes Received:
    0
    /sigh... even though I used it twice already, I got the following upon trying to install Microsoft Security Essentials after re-imaging the system....
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {5003, fffff70001080000, 2d, 2f00000052}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+398d6 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005003, The subtype of the bugcheck.
    Arg2: fffff70001080000
    Arg3: 000000000000002d
    Arg4: 0000002f00000052
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_5003
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  WerFault.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002d01436 to fffff80002c90640
    
    STACK_TEXT:  
    fffff880`0896a9a8 fffff800`02d01436 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`0000002d : nt!KeBugCheckEx
    fffff880`0896a9b0 fffff800`02c9d979 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`00000000 : nt! ?? ::FNODOBFM::`string'+0x398d6
    fffff880`0896aac0 fffff800`02c8e76e : 00000000`00000000 000007ff`fffb0000 00000000`00000001 00000000`0015f4f0 : nt!MmAccessFault+0x359
    fffff880`0896ac20 00000000`779a2f80 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`0015f2b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779a2f80
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+398d6
    fffff800`02d01436 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+398d6
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a
    
    FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+398d6
    
    BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+398d6
    
    Followup: MachineOwner
    
    
    Followed by a successful boot and no problems installing the same thing agian...
     
  12. noobiesnack

    noobiesnack New Member

    Joined:
    Sep 22, 2011
    Messages:
    16
    Likes Received:
    0
    Little bit of good/bad news. I ran a benchmark utility. On the first run using RAM+CPU+GPU+DISKS+SOUND the system locked up after 14 seconds. The second run, I ran CPU at 95% stress and made 10 passes with no problems. I then moved onto the RAM where after just 2 passes I got 350 errors for 'Memory written does not match memory read' (aka, bad memory slot). After that, I decided I might as well check graphics after that. System locked up upon trying so i rebooted. tried again,
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff880045affe7, fffff88004fcb518, fffff88004fcad70}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS::GetProcessCommitedState+13 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff880045affe7, The address that the exception occurred at
    Arg3: fffff88004fcb518, Exception Record Address
    Arg4: fffff88004fcad70, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    dxgmms1!VIDMM_PROCESS::GetProcessCommitedState+13
    fffff880`045affe7 488b1cd0        mov     rbx,qword ptr [rax+rdx*8]
    
    EXCEPTION_RECORD:  fffff88004fcb518 -- (.exr 0xfffff88004fcb518)
    ExceptionAddress: fffff880045affe7 (dxgmms1!VIDMM_PROCESS::GetProcessCommitedState+0x0000000000000013)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff88004fcad70 -- (.cxr 0xfffff88004fcad70)
    rax=f0fffff8a016d941 rbx=fffff8a016ed3430 rcx=fffff8a0169df241
    rdx=0000000000000000 rsi=fffff8800459c5c8 rdi=0000000000000002
    rip=fffff880045affe7 rsp=fffff88004fcb750 rbp=fffffa8008e2e000
     r8=0000000000000002  r9=fffff8a0169df241 r10=fffff8a0169df241
    r11=fffff8a016ed3430 r12=fffffa8008e2e000 r13=fffff8a016ed3430
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    dxgmms1!VIDMM_PROCESS::GetProcessCommitedState+0x13:
    fffff880`045affe7 488b1cd0        mov     rbx,qword ptr [rax+rdx*8] ds:002b:f0fffff8`a016d941=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c30e8
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_PROCESS::GetProcessCommitedState+13
    fffff880`045affe7 488b1cd0        mov     rbx,qword ptr [rax+rdx*8]
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from fffff880045a9d57 to fffff880045affe7
    
    STACK_TEXT:  
    fffff880`04fcb750 fffff880`045a9d57 : fffff8a0`02fe6e50 fffff8a0`16ed3430 fffffa80`08e18690 fffff880`04fcb918 : dxgmms1!VIDMM_PROCESS::GetProcessCommitedState+0x13
    fffff880`04fcb780 fffff880`045a9f24 : 00000000`00000002 00000000`00000000 fffff880`04fcb918 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::GetTrimmingPriorityLimitFromPolicy+0x43
    fffff880`04fcb7b0 fffff880`045a937b : fffff8a0`16ed3430 00000000`3c190000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::AcquireGPUResourcesFromHintedBankInformation+0x124
    fffff880`04fcb850 fffff880`045a627c : 00000000`00000010 00000000`00000000 00000000`00000001 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x25f
    fffff880`04fcb910 fffff880`045c065d : 00000000`00000000 fffff8a0`16d06a60 fffffa80`00000000 fffffa80`06bdff10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x7e8
    fffff880`04fcbae0 fffff880`045c0398 : fffff800`0443d080 fffff880`045bfd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`04fcbcd0 fffff880`045bfe96 : 00000000`00000000 fffffa80`09dc6b50 00000000`00000080 fffffa80`08e082d0 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`04fcbd00 fffff800`0312fcce : 00000000`01b8e433 fffffa80`08e2d770 fffffa80`06a05b30 fffffa80`08e2d770 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`04fcbd40 fffff800`02e83fe6 : fffff800`03004e80 fffffa80`08e2d770 fffff800`03012cc0 fffff880`01218384 : nt!PspSystemThreadStartup+0x5a
    fffff880`04fcbd80 00000000`00000000 : fffff880`04fcc000 fffff880`04fc6000 fffff880`04fcb680 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS::GetProcessCommitedState+13
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
    
    STACK_COMMAND:  .cxr 0xfffff88004fcad70 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_PROCESS::GetProcessCommitedState+13
    
    BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_PROCESS::GetProcessCommitedState+13
    
    Followup: MachineOwner
    
    
    and again, a bad memory reference from a device/driver.

    Thoughts?

    Update: according the the error code sheet included with benchmark program, the error is reference to either bad RAM, CPU problems, or overheating. I have confirmed no overheating and no CPU problems with the same tool. That leaves just the RAM which I am currently testing different sticks right now.


    [POSSIBLY SOLVED]

    I think I finally got the problem located! I pulled out 1 stick of 4gb ram, ran the benchmark tool and got 250 errors just on the one stick. changed out that stick and put the other 4gb stick in. Started the computer and immediatly noticed it was moving at around 15x the speed it was before. Benchmark passed 15 passes with over 3GB being written/read during each pass to ram I think its safe to say this problem was the other 4gb stick.

    Thanks to whoever posted up the link to a benchmark site and gave me the idea to find a good tool and ran it!

    Tool: BurnInTest
     
    #12 noobiesnack, Sep 23, 2011
    Last edited: Sep 23, 2011
  13. kaos

    kaos Senior Member

    Joined:
    May 9, 2011
    Messages:
    1,747
    Likes Received:
    33
    I believe thr Dxgmms1.sys relates to direct X, Have you check for Direct X udpates/ reinstall latest version incase ther are any errors?
     

Share This Page

Loading...