Random BSODs and applications crashes on a fresh Win7 install

Page 8 of 11 FirstFirst ... 678910 ... LastLast

  1. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #71

    Find a supplier with a good return policy, get a 650 or 750w PSU.
    If it works with your 550Ti you've found the answer. If it doesn't work you can return it.

    Be sure to get a good quality brand, others can cause issues.

    Recommended brands:
    Seasonic
    Corsair
    PC Power & Cooling
    Antec
      My Computer


  2. Posts : 59
    Windows 7 home Premium 64bit
    Thread Starter
       #72

    Hi, it crashes as well with the old GS7600. Today I had problems getting into windows, 2-3 times it reported it couldn't load desktop, start some shell command, then finally I got 2 bsods in a row - I attach the zip with them.

    also MSEssentials would not start before the BSODs occured. I'll rescan the PC for virus/malware.

    Since the last post I wrote, there have been numerous app crashes, including the windows ones. So I'm afraid GPU isn't the answer here.

    It's difficult to find such a supplier here, I would say the market is painfully supplier-oriented and not client-oriented :)
      My Computer


  3. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #73

    Your last crash.
    Code:
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041284, A PTE or the working set list is corrupt.
    Arg2: 000000000470d001
    Arg3: 000000000000b4a7
    Arg4: fffff70001080000
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  MsMpEng.exe
    LAST_CONTROL_TRANSFER:  from fffff80002ee2717 to fffff80002e8bc80
    
    STACK_TEXT:  
    fffff880`0384a7d8 fffff800`02ee2717 : 00000000`0000001a 00000000`00041284 00000000`0470d001 00000000`0000b4a7 : nt!KeBugCheckEx
    fffff880`0384a7e0 fffff800`02ebd0e0 : fffff700`01080000 ca700000`305dc867 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4ac3
    fffff880`0384a820 fffff800`02e784bf : fffffa80`00000000 00000000`047e0fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x4e8
    fffff880`0384a9e0 fffff800`02e8af13 : ffffffff`ffffffff 00000000`03e4e2a0 00000000`03e4e268 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
    fffff880`0384aae0 00000000`772e14fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`03e4e1d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772e14fa
    MsMpENG is the antimalware detection engine used by Windows Defender/MSE. There is something interfering with it.
    Did you re-run the previous anti-virus un-installers?

    Just re-read the thread, at this point I would suggest replacing the PSU with a 650 or 750w PSU.
    Be sure to get a good quality one, you can check the brands supplier at this site: POWER SUPPLY REVIEW DATABASE
    Recommended brands:
    Corsair
    Seasonic
    Antec
    XFX
    PC Power & Cooling

    The OEM to look for is Seasonic, CWT.
    Last edited by Dave76; 02 May 2012 at 06:13.
      My Computer


  4. Posts : 59
    Windows 7 home Premium 64bit
    Thread Starter
       #74

    Hi Dave,
    thanks for advice. Before I decide to buy a new PSU though, I'd like to ask whether it's possible that a faulty PSU can cause memory management errors and file corruption, MSE startup errors, application crashes as well as all the other issues that I described so far? I don't doubt it can, but I'd like some more background info if possible :)
    Since last time, with the old 7600GS installed I was still getting problems, windows explorer crashing immediately on windows startup, weird desktop compositions - for example the bar with quick launch icons would get every now and then non-transparent, HWmonitor would crash before launch, etc.
    I put back the 550Ti, Windows booted up fine, I could use the PC for one day w/o problems. Then it started again, windows explorer wouldn't load, I also got 4 blue screens today.
    On Asus website I noticed they put yet another BIOS update, just 1 month after the previous one which is supposed to again "improve stability". It's marked with 1103 and dates from April. We'll see, but for me there's clearly a problem with MB as well, as when I loaded the new BIOS, windows booted up just fine and has been stable for the last couple of hours. As if system's performace was degrading after using it for some time and needed continuous reset of parameters.
    So before cashing out another 100euros for a new PSU, I'll see what their last update brings about.
    Last edited by R4ndom; 15 May 2012 at 04:57.
      My Computer


  5. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #75

    At this point the options are:
    • Faulty motherboard, BIOS update may help solve this and "improve stability" makes it worth a try
    • Faulty CPU, maybe bent pins
    • Faulty PSU

    A failing PSU will give many different kinds of errors and crashes. If the system is not getting smooth continuous voltage it can cause all issues you have described and have been experiencing.
      My Computer


  6. Posts : 59
    Windows 7 home Premium 64bit
    Thread Starter
       #76

    Hi Dave and thanks for the tips. I had another BSOD today while running prime95 in blend torture test (I think it was still running, but I'm not sure, because i was not in front of the PC when it happened, returned after some time to the room just to see the windows log in screen and then info that it had BSODed). I attach the dump file as usual, can you make anything out of it? it's the one from 17 May. So it seems yet another BIOS update for nothing, although for 2 days it ran smoothly, without any errors.

    I notice something else which seems strange to me: no matter how I distribute RAM sticks in the slots (they're black-blue and black blue) it always tells me that it runs in dual channel (CPU-Z), while it should only be in dual when put blue-blue and black-black - this is not the case. I have them now in black-blue next to each other and it still says dual channel. Possibly off-top, but it looks strange to me.

    After rebooting the PC (I ran chkdsk on c drive which again gave no errors) I was getting every 5 seconds windows explorer crash errors. Reboot again, errors gone...

    EDIT: prime95 ran for 12 hours straight all night and detected no errors, no BSOD either..., I'll start OCCT and leave it for a while to see.
    Last edited by R4ndom; 18 May 2012 at 04:49.
      My Computer


  7. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #77

    Your motherboard manual says when installing two RAM cards they should be in the Blue slots.
    Strange the it is showing dual channel when in bule-black slots.
    Programs like CPU-Z can get the wrong information on new CPUs, always a good idea to cross check with other programs like HWiNFO64.

    The last crash:
    Code:
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    PROCESS_NAME:  csrss.exe
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!TimersProc+142
    Usual causes:  System service, Device driver, graphics driver, ?memory
    This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
    What was the CPU temp during the prime95 test?

    It's good that prime95 pasted the second time.
    Let us know how the OCCT test went.
      My Computer


  8. Posts : 59
    Windows 7 home Premium 64bit
    Thread Starter
       #78

    Hi Dave,

    thanks for answering. I reset the RAMs back in blue-blue configuration today and also switched to the Corsair ones, the reason for that being another BSOD while PC was left on idle.

    CPU-Z reports as dual, but this is correct, as I put them in the configuration according to the manual. I couldn't find info about dual-single memory setting in HWinfo.

    PC had functioned perfectly for the last 3 days though with OCZ RAMs in, I did prime test for more than 12 hours without errors, during which CPU temps didn't exceed 43C, OCCT the same, no warnings, PC stable as a rock.

    I notice that the las crash from 17/05 seems to be different from previous ones, but I don't quite get what it's connected with? memory issues again?

    I attach today's crash of 20/05 - this one occured with OCZ modules and BIOS set to default, after that I decided to give the Corsairs another chance.

    CPU temps never exceeds 45C - this while playing SCII or doing OCCT, the CPU isn't overclocked and the Corsair RAM is set to its default - except for the command rate which I had to manually set at 2T, otherwise the PC won't boot.

    thanks!
      My Computer


  9. Posts : 59
    Windows 7 home Premium 64bit
    Thread Starter
       #79

    Only lasted a couple of hours, I came back to my room to see the PC reset itself, but not with a typical BSOD blue screen, the screen simply went black and shortly after I saw the BIOS POST message... and this happened 3 times today in a couple of minutes intervals.

    The only difference I see before the last BIOS update and now is that other programmes don't crash - so far... whereas windows is as unstable as it was before.

    WhoCrashed reports WHEA_UNCORRECTABLE_ERROR, would you please have a look at the two latest dumps I attach? Actually a funny thing (if it can be funny not being able to use your pc for 6months, but that's a different story). The last reboot took place out of the blue, with PC perfectly on idle, just skype and firefox running in background, actually today I never got the typical BSOD with a message "dumping memory blablabla and after reboot there was no the usual "windows has recovered after an error. blablabla". so although there were 3 BSODs today, only 2 were registered...

    thanks!
      My Computer


  10. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #80

    Did you change the BIOS voltage as suggested previously?

    Dave76 said:
    What is the RAM frequency?

    If not 1333MHz then manually set it to that.
    Manually set the RAM to manufacturers specs, 9-9-9-24 and Command Rate of 2T.
    DRAM voltage to 1.65v manually.
    Set the 'VDDNB Over Voltage' to 1.250v.

    If that's not stable, we'll bump the CPU voltage a little.
    Can you upload the CPUZ CPU tab under full load?
    Go to 'CPU Over Voltage' and tell us the options there.
    Start with a +0.10v.
    Did you increase the CPU voltage as mentioned in post #59?
    Give the CPU voltage a bump, increase the CPU Over Voltage an additional 0.10v.
    Is the 'VDDNB Over Voltage' still set to 1.350v?
    Both of the last crashes are the same.

    STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
    Usual causes: Hardware, Incompatibility, May be driver corruption

    This is blaming the CPU, the possibilities are: bad CPU, CPU/socket bent pins, loose cable connections, unstable power supply, CPU idle power too low.
    FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    This can be heat related (we've already looked into that), defective hardware: usually memory, processor or PSU.
    It is possible that it is driver related but usually not the case, you have updated all the motherboard drivers from the mobo website, correct?
    Remove ALL power and reseat all cards, memory, GPU, Sound, and any others you have installed.
    Be sure to check all cables on both ends - actually remove and reconnect - check for anything that doesn't fit tight or seems a little loose.
    Also check your CPU cooler fan connections.


    Check this post for anything we haven't tried yet: Stop 0x124 - what it means and what to try

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8004b65038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`031a15b0 fffff800`030d8ca9 : fffffa80`04b65010 fffffa80`03a51040 00000000`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`031a1ad0 fffff800`02fb9587 : fffffa80`04b65010 fffff800`030332d8 fffffa80`03a51040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`031a1b00 fffff800`02f20985 : fffff800`03094ae0 00000000`00000001 fffffa80`04b57170 fffffa80`03a51040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`031a1b40 fffff800`02e9f851 : fffff880`00c5ae00 fffff800`02f20960 fffffa80`03a51000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`031a1b70 fffff800`0312ce6a : 00000000`00000000 fffffa80`03a51040 00000000`00000080 fffffa80`03943840 : nt!ExpWorkerThread+0x111
    fffff880`031a1c00 fffff800`02e86f06 : fffff880`02fd5180 fffffa80`03a51040 fffff880`02fdffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`031a1c40 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a0fc0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    Followup: MachineOwner
    ---------
    Can you translate these?
    tell me what apps are crashing?
    Code:
    2012-04-21 11:33	Application Hang	Program firefox.exe w wersji 11.0.0.4454 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: c88
     Godzina rozpoczęcia: 01cd1fa6ff9f4216
     Godzina zakończenia: 18
     Ścieżka aplikacji: D:\Mozilla Firefox\firefox.exe
     Identyfikator raportu: ce425251-8ba5-11e1-a87b-14dae9c5e52a
    
    
    2012-04-06 17:31	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: a10
     Godzina rozpoczęcia: 01cd141aa29f32ec
     Godzina zakończenia: 16
     Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
     Identyfikator raportu: 
    
    
    2012-03-13 21:41	Application Hang	Program SopCast.exe w wersji 3.4.7.45585 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: 794
     Godzina rozpoczęcia: 01cd01611e99e1a5
     Godzina zakończenia: 7
     Ścieżka aplikacji: D:\SopCast\SopCast.exe
     Identyfikator raportu: 81ab542a-6d54-11e1-ba62-14dae9c5e52a
    
    
    2012-02-21 23:29	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: d8
     Godzina rozpoczęcia: 01ccf0f0834850c2
     Godzina zakończenia: 46
     Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
     Identyfikator raportu: 
    
    
    2012-02-17 20:06	Application Hang	Program PRIME95.EXE w wersji 24.14.1.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: df0
     Godzina rozpoczęcia: 01ccedae9183c0d4
     Godzina zakończenia: 18902
     Ścieżka aplikacji: D:\Prime95\PRIME95.EXE
     Identyfikator raportu: b891b03a-59a2-11e1-9fb2-14dae9c5e52a
    
    
    2012-02-16 18:16	Application Hang	Program Setup.exe w wersji 10.0.30319.1 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: d10
     Godzina rozpoczęcia: 01ccecd661a87b3d
     Godzina zakończenia: 3
     Ścieżka aplikacji: E:\f756663a13d0803aebfe4c0a820e1b34\Setup.exe
     Identyfikator raportu: 
    
    
    2012-02-05 21:56	Application Hang	Program i_view32.exe w wersji 4.3.2.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: e90
     Godzina rozpoczęcia: 01cce450eefff8a5
     Godzina zakończenia: 3
     Ścieżka aplikacji: D:\IrfanView\i_view32.exe
     Identyfikator raportu: 4e4560cf-5044-11e1-b192-14dae9c5e52a
    
    
    2012-02-05 21:55	Application Hang	Program i_view32.exe w wersji 4.3.2.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: eac
     Godzina rozpoczęcia: 01cce450c934bc3a
     Godzina zakończenia: 4
     Ścieżka aplikacji: D:\IrfanView\i_view32.exe
     Identyfikator raportu: 22491eff-5044-11e1-b192-14dae9c5e52a
    
    
    2012-02-04 00:11	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: e24
     Godzina rozpoczęcia: 01cce2d169e15786
     Godzina zakończenia: 28
     Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
     Identyfikator raportu: 
    
    
    2012-02-04 00:10	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: 950
     Godzina rozpoczęcia: 01cce2d14a701630
     Godzina zakończenia: 27
     Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
     Identyfikator raportu: 
    
    
    2012-02-02 18:45	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: 458
     Godzina rozpoczęcia: 01cce1dab113816d
     Godzina zakończenia: 25
     Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
     Identyfikator raportu: 
    
    
    2012-01-31 20:10	Application Hang	Program iw3mp.exe w wersji 0.0.0.0 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: f1c
     Godzina rozpoczęcia: 01cce0531b10e575
     Godzina zakończenia: 41
     Ścieżka aplikacji: D:\Call of Duty Modern Warfare\iw3mp.exe
     Identyfikator raportu: 
    
    
    2012-01-17 20:10	Application Hang	Program explorer.exe w wersji 6.1.7601.17567 zatrzymał interakcję z systemem Windows i został zamknięty. Aby zobaczyć, czy jest dostępnych więcej informacji dotyczących tego problemu, sprawdź historię problemu w panelu sterowania Centrum akcji.
     Identyfikator procesu: dcc
     Godzina rozpoczęcia: 01ccd5533cb9462d
     Godzina zakończenia: 41565
     Ścieżka aplikacji: C:\Windows\explorer.exe
     Identyfikator raportu:
    Last edited by Dave76; 21 May 2012 at 01:55.
      My Computer


 
Page 8 of 11 FirstFirst ... 678910 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:51.
Find Us