Blue screen on Windows XP installation loading

Hi...
I am trying to install windows xp professional...
I'm booting from cd and when the windows start to loads the installation tool a blue screen show and i have to restart....i tried with another cds and didn't work
is that a block to doesn't install a previous version of windows media center ??
(my current system is winxp media center(from recovery cd))
Tks

Hi Alex
Please write to us which notebook model you have. Did you upgrade some hardware components? Is some external device connected to your unit while you try to install OS?
Usually every notebook delivered with WXP MCE can be preinstalled with WXP. The drivers are the same.

Similar Messages

  • Blue screen in windows 7

    I have been getting the blue screen after windows has been running for a while. Sometimes it happens when I am trying to install something. I have uploaded minidump files to the sky drive but I can't seem to read them, I tried copying and pasting them to
    the desktop and opening them as notepad files but all I get is gibberish, at least it is to me. I need to know how to make these accessible to the pros so I can repair this problem. I have the Technical information from the blue screen here:
    A clock interrupt was not received on  a secondary processor within the allocated time interval.
    *** stop 0x000000101 (0x0000000000000031, 0x0000000000000000, 0xFFFFF88002FD3180, 0x0000000000000003)
    Don't know if this helps but there it is.
    I am running Windows 7 P 64 bit desk top
    Gigabyte MB GA-MA78Gm-S2H Rev 1.0
    4GB Crucial Ballistix PC6400 800 Mhz 2Volt BL2CP25664A80A
    AMD PHENOM 9750 2.4Ghz QUAD CORE
    CPU temp was 32-34 degrees C last time I checked.
    Disk error check was inconclusive ( I walked away and when I returned windows had loaded ) I assume this means that no errors were found.
    RAM scanned and no errors were found.
    https://skydrive.live.com/?mkt=en-US#cid=74B3C1D7DE3540EC&id=74B3C1D7DE3540EC!130

    Alan
    These worked but were inconclusive 0oease run driver verifier to pin down the misbehaving driver.
    These crashes were related to memory management (probably caused by a driver). 
    Please run these tests to verify your memory and find which driver is causing the problem.  Since this appears to be a driver I would start with driver verifier.
    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
    know what it is you probably are not overclocking.
    1-Memtest. (You can read more about running memtest here)
    2-Driver verifier (for complete directions see our wiki here)
    Co-Authored by  JMH3143
    Wanikiya and Dyami--Team Zigzag

  • My laptop become blue screen after windows logo, after i update the graphic ati and intel driver

    I have constant blue screen after windows logo and i have updated all drivers. i was upset the blue screen didn't go away and i did the factory reset. For my suprise, it didn't solve the problem and then i repair it at the comp shop. it was installed with windows 7 home premium 64 (pavilion g4 1006tx) bit as the pre installed windows and activated with the key back on sticker. I updated all drivers and i noticed every time i update the ati and intel driver it will go blue screen after windows logo. after i uninstall it at in safe mode it can load normally. My question is there any solution for my graphic card or is it already damaged? or any other hardware problem? please because i have to use high graphic as i use photoshop

    hii
    make sure you download and update correct driver version of graphic
    and know spec
    more:
    http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-g4-Notebook-PC-series/5046252/model/5068...
    try to instal  "AMD High-Definition Graphics Driver" only
    and uninstal "Intel High-Definition (HD) Graphics Driver"
    Wisnu Suryandi

  • Blue screen error "windows has recovered from a unexpected shutdown"

    Hi guys
    I am using laptop & everyday it will unexpectedly shutdown and shows Blue screen error "windows has recovered from a unexpected shutdown"...Pls help me to resolve this issue.
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.256.48
      Locale ID: 1033
    Additional information about the problem:
      BCCode: d1
      BCP1: 00000030
      BCP2: 00000002
      BCP3: 00000000
      BCP4: 8F2DA8A5
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 256_1
    Files that help describe the problem:
      C:\Windows\Minidump\062614-23836-01.dmp
      C:\Users\Venkateshwara swamy\AppData\Local\Temp\WER-74552-0.sysdata.xml
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

    It could be some driver compatibility issues.
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244(v=vs.85).aspx
     http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • MacBook Pro won't boot (question mark folder) after blue screen on windows bootcamp

    Hi,
    So, I was on windows, using bootcamp, and I was creating partitions on a pen drive with it, and then it asks me that it needs to restart to apply changes.
    But then, while restarting, a blue screen occurred (**** windows).... And I forced the shutdown pressing the power key.
    Then, I simply turned the MacBook on, trying to boot on my snow leopard and I got a flashing folder with a question mark on it.
    Now I can't access any partitions on it, if I press option key on startup I get a blank window!
    I tried to reset PRAM, repair the MacOs partition using the snow leopard DVD (it shows up fine, along with windows partition and EFI partition), and I still don't get my startup disk showing up...
    How can I fix this? I can't loose my files and I need to work with it :/

    I just fixed it!
    For future reference, what I did was:
    - Booting from OSX DVD, go to disk utility
    - Erase windows partition (yap, I lost it...)
    - Do a "repair disk" on every partition of my hard drive
    - Restart
    And it just worked ;)
    Thankfully I had no important files on my windows partition, now I will just reinstall it.

  • Skype causing Blue Screen on Windows 7

    I just recently acquired a new computer and after installing Skype the second I log in it causes a blue screen of my computer. I tried a few times and the same happened everytime. Anyone else sharing this problem?

    Blue screen on Windows 7? Wow. I've never managed to get BSOD on any of my Win7 PCs.
    But what may cause this - no idea, really.
    Добавляйте баллы, если моё сообщение вам помогло. Спасибо!
    Возврат денег | Система обновления подписок | Заблокировали/взломали аккаунт? | Пропали контакты? | Не зайти в Skype/не добавляются контакты? | Не удалось загрузить базу данных?
    Подписки | Цены

  • HT3986 i get a black screen during windows 7 installation on bootcamp 5.0.1

    i get a black screen during windows 7 installation on bootcamp 5.0.1 , it wont install

    Hi wb2009,
    I haven't found that the TV would be an issue, but did find an article that states to not have extra USB devices connected.
    Boot Camp: Windows installation boots to black screen with blinking cursor
    http://support.apple.com/kb/TS4536
    The Windows installation may boot to a black screen with a blinking cursor. This can occur if you use a USB optical drive or USB Flash drive for the Windows installation and another USB device is also connected to the computer.
    There's another article that mentions Windows XP or Vista that may apply.
    Archived - Boot Camp: Start up to black screen after installing Windows
    http://support.apple.com/kb/TS2600
    Thank you for visiting Apple Support Communities.
    Nubz

  • Display not working, external display does, but blue screen when windows loads

    Hi folks, wondering if anyone can help.
    My DV6's display is no longer working.  An external VGA display works, but when it gets to the "welcome" screen as it loads into windows, I get a blue screen.  I was able to load into safe mode previously, but I foolishly reformatted and reinstalled windows thinking it might solve the problem.  Now I can't even get into safe mode because it won't allow a first time setup of Windows in safe mode.
    I suspect this may be the death of my loyal notebook, but was hoping someone could propose a solution.
    Thanks!

    HI @Mikep037,
    Thank you for your query, I am happy to assist you!
    I understand that you are having an issue with your display.
    You have reformatted and reinstalled Windows but are unable to complete the setup.
    Did you do a recovery or did you reinstall Windows from a retail disk?
    First I would try a hard reset.  HP Notebook PCs - Use Hard Reset to Resolve Hardware and Software Issues.  Please be sure to remove any CD/DVD from tray and disconnect all externals devices or USB's.
    HP Notebook PCs - Overview of How to Troubleshoot Problems When a Computer Does Not Start Up or Boot...
    Here links to aid with the recovery process.
    HP PCs - Performing an HP system recovery (Windows 7)
    HP Notebook PCs - System Recovery May Fail or Display Error Message (Windows 7, or Vista)
    Best of Luck!
    Sparkles1
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

  • Why am I getting a blue screen during windows support software installation?

    After intalling windows 7 x64 (using boot camp 5.1), when I come to install windows support software to set up apple drivers for windows to run on my MacBook pro (late 2013), after installing a good number of drivers, I get suddenly a blue screen!....
    What can I do, once windows is not strting up? It started well, but wth no proper drivers. Thanks.

    I guess the first thing I would do would be to boot up using the original installation DVD and correct the permissions. That may not be the problem at all, it could be an incomplete upgrade install but at least you would know it isn't a permissions problem. I'd also run or verify the hard disk using this method.
    How is it done? Turn machine on. Insert DVD 1 of the Install Disks, restart the machine, hold down the Command and the C keys (that tells the machine to look to the Rom drive and boot from it). Once it is up (will take a long minute or so...) go up to the top left where the install menu buttons are listed, look for the disk utility and run it. Tell it to verify and repair the disk and repair the permissions. Once done, quit the Disk Utility and select the restart option. Wait to see if your original desktop comes back.
    If not, then you'll need to either "back out" the upgrade you installed or install your backup. If you don't have a backup you'll probably have to re-install OS X all over again (and probably lose all your previous data, apps, etc.). Let's hope it clears up first before you have to re-install.
    Lisa

  • Blue screen on windows 7 notebook

    I got a blue screen on my notebook mini 210 -2190NR
    Everytime i used my notebook, it always had to install updates before it shut down. But last time i used it though, i was able to shut down without any update.
    The next time i used it, i was able to log in windows fine. But once i went browsing on the internet with a couple of tabs open, my notebook's cooling fan started doing a loud noise then it gave me the blue screen and it shut down.
    Once i booted again, it took me to the Windows error recovery black screen with two options:
    Launch startup repair  or Start windows normally.
    Neither of them worked, once i start windows normally it loads up to the black screen with the loading bar, then it shows me the blue screen again for a second and goes back to the beginning screen. Then it tells me:
    No bootable device -- insert boot disk and press any key
    I tried inserting my windows 7 recovery USB but it showed me the same message after pressing any key.
    I tried booting from the recovery USB and on the system recovery options, the list is empty where it says operating system, partition size, and location.
    When it takes me to the window to choose a recovery tool, underneath it says, Operating system: Unknown on (Unknown) Local disk.
    Choosing system restore it tells me i must specify which windows installation to restore.
    Does anyone know what to do to fix this?? Thank you in advance.

    Hi A1b3rto, sorry to see that you are getting the Blue screen errors on your Mini. I have found a document that troubleshoots Errors Messages on a Blue Screen. Please click on the link to get to the document.  http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&dlc=en&docname=c00372711
    If you are still having issues, please let me know so I can continue to help with the issue.
    Thank you.
    Click the “Kudos Thumbs Up" at the bottom of this post to say “Thanks” for helping!
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    W a t e r b o y 71
    I work on behalf of HP

  • Blue Screen on Windows 7 Boot

    I repartitioned the hard drive on a computer running only Windows 7.  This was done using non Windows utilities that have proven to be very reliable in the past.  The utilities in question are all on the System Rescue CD and include (GParted, and
    ntfsclone).  Insofar as it appears to me that the software supplied by Windows will not allow any movement of partitions it is necessary to use other software for this purpose.  There are many articles in this forum which indicate that such software
    must be used for such partition management activity.
    The affect of the repartitioning is that the primary partition that contains the Windows 7 operating system is now the third one on the drive rather than the second one.  I was able to add an entry in the BCD for the boot manager to use to find the
    new partition.  The boot manager seems to work fine.  It appears to me as though the Windows 7 boot loader (WinLoad.exe) does execute and the kernel is loaded.  However, before there is any opportunity to interact with Windows the blue screen
    occurs.  On my computer you only see the blue screen error messages momentarily and then the computer reboots.  This amounts to the deadly embrace.  Is there some kind of setting that will allow me to learn what the error message says? 
    I have tried starting in "safe mode".
    I'm pretty confident that the partition was moved correctly.  In that, the new partition is an exact copy of the original.  This technique is something that I've done repeatedly and works very well with Windows XP even though there are registry
    updates that are necessary to complete the task.  The difference being that Windows XP does boot satisfactorily which allows this to be done.  What do I need to do to get Windows to boot successfully?

    Hi,
    Seems the PC is completely unbootable at this moment, I would suggest you use startup repair or the Last known good configuration under advanced startup options and check if it can bring the PC back to normal.
    You can see guide in the link below
    http://windows.microsoft.com/en-hk/windows/advanced-startup-options-including-safe-mode#1TC=windows-7 
    Regards
    Yolanda Zhu
    TechNet Community Support

  • Dmp file and blue screen error Windows 7

    Hi,
    Just wondering if someone can tell me how to read the dmp file created after the blue screen appears ?
    I have just recently upgraded my Toshiba P300 from Vista 64 bit to Windows 7 Home Prem 64 bit. 
    I dont know why Windows 7 keeps crashing and so far I have no idea of how to open the .dmp
    file (I have zipped the dmp file and attahced below).
    http://cid-7a99d6152c55359c.skydrive.live.com/self.aspx/.Public/minidump/022710-26223-01.zip
    The message that I been given so far says :
    Problem signature:
      Problem Event Name:                        BlueScreen
      OS Version:                                          6.1.7600.2.0.0.768.3
      Locale ID:                                             3081
      Additional information about the problem:
      BCCode:                                               a
      BCP1:                                                    FFFFF6FC40052000
      BCP2:                                                    0000000000000002
      BCP3:                                                    0000000000000000
      BCP4:                                                    FFFFF80002E62322
      OS Version:                                          6_1_7600
      Service Pack:                                       0_0
      Product:                                               768_1
      Files that help describe the problem:
      C:\Windows\Minidump\022710-26223-01.dmp
      C:\Users\Caroline\AppData\Local\Temp\WER-125393-0.sysdata.xml

    I have try step 1 and didnt boot up the window normaly...same thing happened
    Window 7 is loading...then boom the screen failed and blue screen appear...
    there is the latet crash report
    Version=1
    EventType=BlueScreen
    EventTime=129810543666556864
    ReportType=4
    Consent=1
    ReportIdentifier=9fb6a978-99f3-11e1-9b67-fa9a72be4846
    IntegratorReportIdentifier=050912-14508-01
    Response.type=4
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.256.1
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=3084
    UI[2]=C:\Windows\system32\wer.dll
    UI[3]=Windows has recovered from an unexpected shutdown
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=&Check for solution
    UI[6]=&Check later
    UI[7]=Cancel
    UI[8]=Windows has recovered from an unexpected shutdown
    UI[9]=A problem caused Windows to stop working correctly.  Windows will notify you if a solution is available.
    UI[10]=Close
    Sec[0].Key=BCCode
    Sec[0].Value=a
    Sec[1].Key=BCP1
    Sec[1].Value=0000000000000000
    Sec[2].Key=BCP2
    Sec[2].Value=0000000000000002
    Sec[3].Key=BCP3
    Sec[3].Value=0000000000000001
    Sec[4].Key=BCP4
    Sec[4].Value=FFFFF8000308BB7E
    Sec[5].Key=OS Version
    Sec[5].Value=6_1_7601
    Sec[6].Key=Service Pack
    Sec[6].Value=1_0
    Sec[7].Key=Product
    Sec[7].Value=256_1
    File[0].CabName=050912-14508-01.dmp
    File[0].Path=050912-14508-01.dmp
    File[0].Flags=589826
    File[0].Type=2
    File[0].Original.Path=C:\Windows\Minidump\050912-14508-01.dmp
    File[1].CabName=sysdata.xml
    File[1].Path=WER-27253-0.sysdata.xml
    File[1].Flags=589826
    File[1].Type=5
    File[1].Original.Path=C:\Users\Moz\AppData\Local\Temp\WER-27253-0.sysdata.xml
    File[2].CabName=Report.cab
    File[2].Path=Report.cab
    File[2].Flags=196608
    File[2].Type=7
    File[2].Original.Path=Report.cab
    FriendlyEventName=Shut down unexpectedly
    ConsentKey=BlueScreen
    AppName=Windows
    AppPath=C:\Windows\System32\WerFault.exe
    ive also have got a AI SUITE II crash...
    Version=1
    EventType=APPCRASH
    EventTime=129809041249476693
    ReportType=2
    Consent=1
    UploadTime=129809041250516752
    ReportIdentifier=ddea075d-9895-11e1-9a9f-eb38eba38a41
    IntegratorReportIdentifier=ddea075c-9895-11e1-9a9f-eb38eba38a41
    WOW64=1
    Response.BucketId=2555721005
    Response.BucketTable=1
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=AI Suite II.exe
    Sig[1].Name=Application Version
    Sig[1].Value=1.0.0.40
    Sig[2].Name=Application Timestamp
    Sig[2].Value=00000000
    Sig[3].Name=Fault Module Name
    Sig[3].Value=KERNELBASE.dll
    Sig[4].Name=Fault Module Version
    Sig[4].Value=6.1.7601.17651
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=4e211319
    Sig[6].Name=Exception Code
    Sig[6].Value=0eedfade
    Sig[7].Name=Exception Offset
    Sig[7].Value=0000b9bc
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.256.1
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=3084
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=0a9e
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=0a9e
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
    UI[2]=C:\Program Files (x86)\ASUS\AI Suite II\AI Suite II.exe
    UI[3]=AI Suite II has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Program Files (x86)\ASUS\AI Suite II\AI Suite II.exe
    LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
    LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
    LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\syswow64\WINTRUST.DLL
    LoadedModule[5]=C:\Windows\syswow64\msvcrt.dll
    LoadedModule[6]=C:\Windows\syswow64\CRYPT32.dll
    LoadedModule[7]=C:\Windows\syswow64\MSASN1.dll
    LoadedModule[8]=C:\Windows\syswow64\RPCRT4.dll
    LoadedModule[9]=C:\Windows\syswow64\SspiCli.dll
    LoadedModule[10]=C:\Windows\syswow64\CRYPTBASE.dll
    LoadedModule[11]=C:\Windows\SysWOW64\sechost.dll
    LoadedModule[12]=C:\Windows\syswow64\ADVAPI32.DLL
    LoadedModule[13]=C:\Windows\system32\VERSION.DLL
    LoadedModule[14]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.DLL
    LoadedModule[15]=C:\Windows\syswow64\GDI32.dll
    LoadedModule[16]=C:\Windows\syswow64\USER32.dll
    LoadedModule[17]=C:\Windows\syswow64\LPK.dll
    LoadedModule[18]=C:\Windows\syswow64\USP10.dll
    LoadedModule[19]=C:\Windows\system32\MSIMG32.DLL
    LoadedModule[20]=C:\Windows\syswow64\SHELL32.DLL
    LoadedModule[21]=C:\Windows\syswow64\SHLWAPI.dll
    LoadedModule[22]=C:\Windows\syswow64\OLE32.DLL
    LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.DLL
    LoadedModule[24]=C:\Windows\system32\IMM32.DLL
    LoadedModule[25]=C:\Windows\syswow64\MSCTF.dll
    LoadedModule[26]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[27]=C:\Windows\system32\rsaenh.dll
    LoadedModule[28]=C:\Windows\syswow64\imagehlp.dll
    LoadedModule[29]=C:\Windows\system32\ncrypt.dll
    LoadedModule[30]=C:\Windows\system32\bcrypt.dll
    LoadedModule[31]=C:\Windows\SysWOW64\bcryptprimitives.dll
    LoadedModule[32]=C:\Program Files (x86)\ASUS\AI Suite II\AsMultiLang.dll
    LoadedModule[33]=C:\Windows\system32\WINSPOOL.DRV
    LoadedModule[34]=C:\Program Files (x86)\ASUS\AI Suite II\ImageHelper.dll
    LoadedModule[35]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll
    LoadedModule[36]=C:\Windows\system32\USERENV.dll
    LoadedModule[37]=C:\Windows\system32\profapi.dll
    LoadedModule[38]=C:\Windows\system32\GPAPI.dll
    LoadedModule[39]=C:\Windows\system32\cryptnet.dll
    LoadedModule[40]=C:\Windows\syswow64\WLDAP32.dll
    LoadedModule[41]=C:\Windows\system32\SensApi.dll
    LoadedModule[42]=C:\Windows\system32\Cabinet.dll
    LoadedModule[43]=C:\Windows\system32\DEVRTL.dll
    LoadedModule[44]=C:\Windows\system32\WindowsCodecs.dll
    LoadedModule[45]=C:\Windows\system32\WINHTTP.dll
    LoadedModule[46]=C:\Windows\system32\webio.dll
    LoadedModule[47]=C:\Windows\syswow64\WS2_32.dll
    LoadedModule[48]=C:\Windows\syswow64\NSI.dll
    LoadedModule[49]=C:\Windows\system32\credssp.dll
    LoadedModule[50]=C:\Windows\syswow64\mswsock.dll
    LoadedModule[51]=\\.\globalroot\systemroot\syswow64\mswsock.dll
    LoadedModule[52]=C:\Windows\syswow64\WININET.dll
    LoadedModule[53]=C:\Windows\syswow64\Normaliz.dll
    LoadedModule[54]=C:\Windows\syswow64\iertutil.dll
    LoadedModule[55]=C:\Windows\syswow64\urlmon.dll
    LoadedModule[56]=C:\Windows\system32\Secur32.dll
    LoadedModule[57]=C:\Windows\System32\wshtcpip.dll
    LoadedModule[58]=C:\Windows\System32\wship6.dll
    LoadedModule[59]=C:\Windows\system32\IPHLPAPI.DLL
    LoadedModule[60]=C:\Windows\system32\WINNSI.DLL
    LoadedModule[61]=C:\Windows\system32\dhcpcsvc6.DLL
    LoadedModule[62]=C:\Windows\system32\dhcpcsvc.DLL
    LoadedModule[63]=C:\Windows\syswow64\CFGMGR32.dll
    LoadedModule[64]=C:\Windows\system32\uxtheme.dll
    LoadedModule[65]=C:\Windows\system32\DNSAPI.dll
    LoadedModule[66]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
    LoadedModule[67]=C:\Windows\system32\rasadhlp.dll
    LoadedModule[68]=C:\Windows\System32\fwpuclnt.dll
    LoadedModule[69]=C:\Program Files (x86)\ASUS\AI Suite II\AssistFunc.dll
    LoadedModule[70]=C:\Windows\system32\PROPSYS.dll
    LoadedModule[71]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.dll
    LoadedModule[72]=C:\Windows\system32\apphelp.dll
    LoadedModule[73]=C:\Windows\syswow64\CLBCatQ.DLL
    LoadedModule[74]=C:\Windows\system32\wpdshext.dll
    LoadedModule[75]=C:\Windows\system32\WINMM.dll
    LoadedModule[76]=C:\Windows\System32\shdocvw.dll
    LoadedModule[77]=C:\Windows\SysWOW64\ieframe.dll
    LoadedModule[78]=C:\Windows\syswow64\PSAPI.DLL
    LoadedModule[79]=C:\Windows\SysWOW64\OLEACC.dll
    LoadedModule[80]=C:\Windows\syswow64\SETUPAPI.dll
    LoadedModule[81]=C:\Windows\syswow64\DEVOBJ.dll
    LoadedModule[82]=C:\Windows\system32\ntmarta.dll
    LoadedModule[83]=C:\Program Files (x86)\ASUS\AI Suite II\pngio.dll
    LoadedModule[84]=C:\Program Files (x86)\ASUS\AI Suite II\AsAcpi.dll
    LoadedModule[85]=C:\Program Files (x86)\ASUS\AI Suite II\asacpiEx.dll
    LoadedModule[86]=C:\Windows\system32\RpcRtRemote.dll
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    State[1].Key=DataRequest
    State[1].Value=Bucket=-1739246291/nBucketTable=1/nResponse=1/n
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=AI Suite II
    AppPath=C:\Program Files (x86)\ASUS\AI Suite II\AI Suite II.exe

  • FB 4 crashed to blue screen on windows - what to do?

    issue: when i am installing flash builder 4 to system - at step of installation where it calculates required time before placing files - it crashes to blue screen of OS.
    version of flash builder 4 trial downloaded today from Adobe.
    system configuration very shortly:
    windows xp sp3+++
    proc: Intel Core2 Duo E8400 3 GHz
    motherboard: MSI P41T
    Ram 2 GB
    I can make small dump of memory, it display some wrong memory read in win32k.sys
    Where to search for source of issue?
    I cant find in google..
    Thanks

    Thanks for reply.
    i am using other Adobe software like Adobe CS4 package, and it installed and works correctly.
    so this issue with crash to blue screen is only with this installation of Flash Builder.
    I may  will try to install some previous version of FB ,
    ps.
    I am using Comodo internet security premium as anitivirus

  • Recurring Physical Memory Dump and Blue Screen on Windows 7

    I recently built a PC and have been getting pretty frequent blue screens whenever I use it. Today I got about 5 within an hour and have finally tried to fix it. I got Windows Debugger and have analyzed the .dmp files and the most common one that I have gotten
    is this one:
    *                        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: fffffa800d062028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    BUGCHECK_STR:  0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  f
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre
    STACK_TEXT:  
    fffff880`031dfb58 fffff800`0320ea3b : 00000000`00000124 00000000`00000000 fffffa80`0d062028 00000000`bf800000 : nt!KeBugCheckEx
    fffff880`031dfb60 fffff800`02da3463 : 00000000`00000001 fffffa80`0cc9f9a0 00000000`00000000 fffffa80`0cc9f9f0 : hal!HalBugCheckSystem+0x1e3
    fffff880`031dfba0 fffff800`0320e700 : 00000000`00000728 fffffa80`0cc9f9a0 fffff880`031dff30 fffff880`031dff00 : nt!WheaReportHwError+0x263
    fffff880`031dfc00 fffff800`0320e052 : fffffa80`0cc9f9a0 fffff880`031dff30 fffffa80`0cc9f9a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`031dfd50 fffff800`0320df0d : 00000000`00000008 00000000`00000001 fffff880`031dffb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`031dfd90 fffff800`03201e88 : 00000000`00000000 fffff880`031d7180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`031dfdc0 fffff800`02c8b4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`031dfdf0 fffff800`02c8b313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`031dff30 fffff880`053889c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`031ffb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: GenuineIntel
    IMAGE_NAME:  GenuineIntel
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    IMAGE_VERSION:  
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache
    FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}
    Followup: MachineOwner
    It looks like it's happening because of a system update I may have done? I'm not sure what to make of this or how to fix it.
    Any help would be greatly appreciated.
    Thanks

    Mike
    Virtual all of these are hardware related so I would start there.  This type of crash is called a BCC124 and 99 times out of 100 it is hardware related.
    Stop 0x124 is a hardware error
    If you are overclocking try resetting your processor to standard settings and see
    if that helps.
    If you continue to get BSODs here are some more things you may want to consider.
    This is usually heat related, defective hardware, memory or even processor though
    it is"possible" that it is driver related (rare).
    Stop 0x124 - what it means and what to try
    Synopsis:
    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
    Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
     Generic "Stop 0x124" Troubleshooting Strategy:
    1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable
    ways.
    2) Ensure that the machine is adequately cooled.
     If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
    3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
    It is good practice to run the latest drivers anyway.
    4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
    Their website should provide detailed instructions as to the brand and model-specific procedure.
    5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
    At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
    6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
    The most obvious examples are the RAM and HDD(s).
    For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
    For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
    Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
    free from defects - only that none were encountered during the test passes.
    7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games,
    utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
    Should that fail to mitigate the 0x124 problem, jump to the next steps.
    If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine
    is still free from 0x124 crashes.
    Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
    If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
    Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
    8) Clean and carefully remove any dust from the inside of the machine.
    Reseat all connectors and memory modules.
    Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
    9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
    Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
    Should you find yourself in the situation of having performed all of the steps
    above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
    More advanced reading can be found here from a MS MVP IT PRO
    http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
    Wanikiya and Dyami--Team Zigzag

  • Toshiba L500 Blue Screen crashes - Windows 7

    I have a Toshiba L500-1XJ, part no. PSLS0E-07D01DEN which crashes almost immediately on loading Windows 7.
    As it belonged to my son, who is now using another machine, I have restored the machine to its original state and still the machine crashes.
    The blue screen of death appears with the following message:
    PROCESS HAS LOCKED PAGES
    STOP: 0x00000076 (0x0000000000000000, 0xFFFFFA8004F4D060, 0x0000000000000033, 0x0000000000000000)
    I am only able to access Windows in Safe mode, otherwise the machine crashes.
    Microsoft Knowledge Base indicate the problem to be with a driver not cleaning up completely after an I/O operation and talks about editing the registry to find out.  I am hesitant about editing the registry as I have not done this before and am not not clear about adding parameters to the registry.
    Microsoft Knowledge Base states -
    =====>  Windows includes a registry value that you can use to save stack traces that enable you to identify the problem driver. 
    Note Using DriverVerifier to enable the Pool Tracking option will result in the same behavior in Vista, 2008, Win7 and 2008 R2 as setting the registry value TrackLockedPages to 1. 
    Use Registry Editor (Regedt32.exe) to view the following registry key: 
    HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
    Add the following registry value, and then restart your computer:
    Value Name: TrackLockedPages
    Value Type: REG_DWORD
    Value Data: 1
    Radix: hexadecimal
    After you make this change, Windows saves stack traces so that you can identify the problem driver. There is no other way to determine which driver is neglecting to clean up the I/O operations. After you enable this flag, if the driver commits the error again, you see the following error message:
    STOP: 0x000000CB (0xY,0xY,0xY,0xY) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
    Parameter 1 - The calling address in the driver that locked the pages
    Parameter 2 - The caller of the calling address in the driver that locked the pages
    Parameter 3 - A pointer to the MDL containing the locked pages
    Parameter 4 - The problem driver's name (Unicode string)
    The problem driver's name is listed on the blue "Stop" screen and is available for dumping again as the fourth parameter in the "Stop" data. 
    After you identify and update or remove the problem driver, you should remove the TrackLockedPages value from the registry.
    =====>
    I have run regedit, but am not confident in what to do next.  Two folders are shown under Memory Management as well as a number of other files contained within the folder itself.  If I highlight Memory Management and click EDIT, NEW a number of options are presented - Key; String Value; Binary Value; DWORD (32-bit) Value; QWORD (64-bit) Value; Multi-String Value; Expandable String Value
    How should I proceed?  Any help would be welcomed.
    Thanks
    Solved!
    Go to Solution.

    Sorry, none of that helps me identify the hardware at fault.
    ==================================================
    Dump File         : 012915-27440-01.dmp
    Crash Time        : 1/30/2015 6:16:00 AM
    Bug Check String  : PROCESS_HAS_LOCKED_PAGES
    Bug Check Code    : 0x00000076
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`060e2b30
    Parameter 3       : 00000000`00000033
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+71f00
    File Description  :
    Product Name      :
    Company           :
    File Version      :
    Processor         : x64
    Computer Name     :
    Full Path         : C:\Test\012915-27440-01.dmp
    Processors Count  : 2
    Major Version     : 15
    Minor Version     : 7600
    ==================================================
    ==================================================
    Dump File         : 012615-22261-01.dmp
    Crash Time        : 1/30/2015 6:15:50 AM
    Bug Check String  : PROCESS_HAS_LOCKED_PAGES
    Bug Check Code    : 0x00000076
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`0504a060
    Parameter 3       : 00000000`00000033
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+71f00
    File Description  :
    Product Name      :
    Company           :
    File Version      :
    Processor         : x64
    Computer Name     :
    Full Path         : C:\Test\012615-22261-01.dmp
    Processors Count  : 2
    Major Version     : 15
    Minor Version     : 7600
    ==================================================
    ==================================================
    Dump File         : 012615-22214-01.dmp
    Crash Time        : 1/30/2015 6:15:45 AM
    Bug Check String  : PROCESS_HAS_LOCKED_PAGES
    Bug Check Code    : 0x00000076
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`04f24060
    Parameter 3       : 00000000`00000033
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+71f00
    File Description  :
    Product Name      :
    Company           :
    File Version      :
    Processor         : x64
    Computer Name     :
    Full Path         : C:\Test\012615-22214-01.dmp
    Processors Count  : 2
    Major Version     : 15
    Minor Version     : 7600
    ==================================================
    -Jerry

Maybe you are looking for