Various blue screen of death windows 7, Asus laptop

Experts/dear Microsoft community,

Recently I had some problems with my laptop. I tried reformatting and everything but nothing seems to solve the problem long term, brief (2-3 days)

My computer crashes (blue screen of death), whenever I play big games online. Games such as Company of Heroes, or Dota 2, etc. If I don't play these games solo (offline) I have no problems. Also all other programs work perfectly.

I have a feeling that it has to do with my Asus laptop drivers, I tried to update, restore and re - install, but without result.

To tell you that as the scenario for the crash: I start the game, I log on online, join a game. Then after 20 to 25 minutes of play online with no loss of FPS, it auto-shutsdown the game with absolutely no message, followed with an accident soon after, sometimes immediately.

Here's the accident report I got the program: Whocrashed

Look forward to hearing your suggestions.

Concerning

computer name: ICRASHEVERYWEEK
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Material: N61Ja, ASUSTeK Computer Inc..
CPU: GenuineIntel Intel (r) Core i5 CPU M 430 @ 2.27 GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4140355584 total
VM: 2147352576, free: 1929850880

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Dumps are enabled on your computer.

Friday, November 7, 2014 22:01:49 this computer crashed
crash dump file: C:\Windows\Minidump\110714-44912-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x5996A0)
Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003BF56A0, 0xFFFFF880035AEE88, 0xFFFFF880035AE6E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

Friday, November 7, 2014 22:01:49 this computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80003BF56A0, 0xFFFFF880035AEE88, 0xFFFFF880035AE6E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug control description: this bug check indicates that a system thread threw an exception that the error handler did not.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

Friday, November 7, 2014 18:29:29 GMT crashed your computer
crash dump file: C:\Windows\Minidump\110714-17737-01.dmp
This was probably caused by the following module: athrx.sys (athrx + 0x1C4F76)
Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88005E67F76, 0xFFFFF880035A7438, 0xFFFFF880035A6C90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\athrx.sys
product: Atheros CB42/CB43/MB42/MB43 network card driver
company: Atheros Communications, Inc.
Description: Atheros Extensible wireless device driver
Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: athrx.sys (pilot device wireless Atheros Extensible, Atheros Communications, Inc.).
Google search: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Friday, November 7, 2014 18:27:43 GMT crashed your computer
crash dump file: C:\Windows\Minidump\110714-14570-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag + 0x1421E5)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005B4A1E5, 0xFFFFF88003E795E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
Description: ATI Radeon driver in Kernel Mode
Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google search: ATI Technologies Inc. SYSTEM_SERVICE_EXCEPTION

Friday, November 7, 2014 6:26:57 PM GMT crashed your computer
crash dump file: C:\Windows\Minidump\110714-15194-01.dmp
This was probably caused by the following module: atikmdag.sys (0xFFFFF88005B20B5B)
Verification of error code: 0 x 50 (0x0, 0xFFFFF88005B20B5B, 0xFFFFF8A0024CF000, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
Description: ATI Radeon driver in Kernel Mode
Bug control description: This indicates that invalid system memory was referenced.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google search: ATI Technologies Inc. PAGE_FAULT_IN_NONPAGED_AREA

Friday, November 7, 2014 17:57:41 CEST your computer crashed
crash dump file: C:\Windows\Minidump\110714-49280-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag + 0x899D90)
Bugcheck code: 0xBE (0x12F9A6860, 0xFFFFF880035BC560, 0xFFFFF880062ACD90, 0xE)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
Description: ATI Radeon driver in Kernel Mode
Bug control description: sounds if a driver attempts to write to a memory segment read-only.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google search: ATI Technologies Inc. ATTEMPTED_WRITE_TO_READONLY_MEMORY

Friday, November 7, 2014 17:55:49 this computer crashed
crash dump file: C:\Windows\Minidump\110714-16692-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000395AA49, 0xFFFFF8800AB310C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

Saturday, November 1, 2014 8:24:12 PM GMT crashed your computer
crash dump file: C:\Windows\Minidump\110114-17550-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost + 0x2C476)
Bug check code: 0x1000007E (0x0, 0xFFFFF880035248B8, 0xFFFFFFFFC0000005, 0xFFFFF88003524110)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: driver for ReadyBoost
Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

Saturday, November 1, 2014 8:22:52 CEST your computer crashed
crash dump file: C:\Windows\Minidump\110114-18142-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
Error: "KMODE_EXCEPTION_NOT_HANDLED"
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

Wednesday, October 15, 2014 9:09:56 CEST your computer crashed
crash dump file: C:\Windows\Minidump\101514-50856-01.dmp
This was probably caused by the following module: athrx.sys (athrx + 0xF9D77)
Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880051BED77, 0xFFFFF880033A7708, 0xFFFFF880033A6F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\athrx.sys
product: Atheros CB42/CB43/MB42/MB43 network card driver
company: Atheros Communications, Inc.
Description: Atheros Extensible wireless device driver
Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: athrx.sys (pilot device wireless Atheros Extensible, Atheros Communications, Inc.).
Google search: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

13 dumps were found and analysed. Only 10 are included in this report. 2 third party drivers have been identified to be the cause of breakdowns of the system on your computer. It is strongly recommended that you check the updates for these drivers on their corporate Web sites. Click on the links below to search with Google for updates these drivers:

athrx.sys (Atheros Extensible, Atheros Communications, Inc. wireless device driver.)
atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)

If no updates for these drivers is available, try searching with Google on the names of these drivers in combination errors that have been reported for these drivers and include the brand name and model of your computer as well in the query. This often gives interesting results of the discussions of the users who have similar problems.

Read the WARNINGS GENERAL topic for troubleshooting failures of the system for more information.

Note that it is not always possible to say with certainty whether a reported driver is in fact responsible for crash your system or cause is in another module. However, it is suggested that you look for updates for the products that these drivers belong to and regularly visit Windows Update or activate the automatic updates for Windows. In case a piece of defective material is originally wrong, a Google search on the errors of control of bug with the name of the model and brand of your computer can help you to deepen this review.

Analysis of Dump 1Crash
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Dumps are enabled on your computer.

Monday, October 13, 2014 5:41:45 PM GMT crashed your computer
crash dump file: C:\Windows\Minidump\101314-17004-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B90)
Verification of error code: 0 x 17 (0x0, 0x0, 0x0 0 x 0)
Error: CID_HANDLE_DELETION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: this bug control appears very rarely.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

Monday, October 13, 2014 5:41:45 PM GMT crashed your computer
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheck + 0x0)
Verification of error code: 0 x 17 (0x0, 0x0, 0x0 0 x 0)
Error: CID_HANDLE_DELETION
Bug control description: this bug control appears very rarely.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

Monday, October 13, 2014 12:15:52 CEST your computer crashed
crash dump file: C:\Windows\Minidump\101314-17784-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x2EDF95)
Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003145F95, 0xFFFFF88004650448, 0xFFFFF8800464FCA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

Monday, October 13, 2014 11:09:34 AM GMT crashed your computer
crash dump file: C:\Windows\Minidump\101314-14320-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
Bugcheck code: 0xA (28, 0 x 2, 0 x 0 x 0, 0xFFFFF80002F21D80)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

Monday, October 13, 2014 2:53:45 AM GMT crashed your computer
crash dump file: C:\Windows\Minidump\101314-46987-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0x0, 0xFFFFF88002DA2910)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

Sunday, September 28, 2014 17:57:12 CEST your computer crashed
crash dump file: C:\Windows\Minidump\092814-16926-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1 + 0xC0A1)
Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
Error: "KMODE_EXCEPTION_NOT_HANDLED"
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: DirectX Graphics MMS
Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.
Google search: Microsoft Corporation KMODE_EXCEPTION_NOT_HANDLED

Monday, September 22, 2014 6:50:05 PM GMT crashed your computer
crash dump file: C:\Windows\Minidump\092214-42525-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
Bugcheck code: 0x1A (0xFFFFF780C0000000, 0x1DEE, 0 x 5003, 0x420700003BD8)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: This indicates that an error occurred serious memory management.
This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 dumps were found and analysed. A third-party driver has been designated to be the cause of breakdowns of the system on your computer. It is strongly recommended that you check the updates for these drivers on their corporate Web sites. Click on the links below to search with Google for updates these drivers:

dxgmms1.sys (DirectX Graphics MMS, Microsoft Corporation)

If no updates for these drivers is available, try searching with Google on the names of these drivers in combination errors that have been reported for these drivers and include the brand name and model of your computer as well in the query. This often gives interesting results of the discussions of the users who have similar problems.

Read the WARNINGS GENERAL topic for troubleshooting failures of the system for more information.

Note that it is not always possible to say with certainty whether a reported driver is in fact responsible for crash your system or cause is in another module. However, it is suggested that you look for updates for the products that these drivers belong to and regularly visit Windows Update or activate the automatic updates for Windows. In case a piece of defective material is originally wrong, a Google search on the errors of control of bug with the name of the model and brand of your computer can help you to deepen this review.

PC! PK

These two were related to the material.  Specifically of the RAM.  Please run memtest

Tags: Windows

Similar Questions

  • Blue Screen Driver IRQL blue screen of death Windows 7 Ultimate edition and Windows Vista

    original title: BSOD Driver IRQL blue screen of death Windows 7 ultimate and Windows Vista

    I get the BSOD, and they are different every time.

    I had originally Windows Vista on my pc (HP m8300f) and it worked fine for 3 years until last month, I started to have these BSOD.

    So I thought a new clean install of Windows 7 Ultimate would solve the problem. Well, I was very happy to get the new operating system installed, but a few hours later that darn BSOD appeared and im now distraught.

    What is my RAM? My drivers? My hard drives?

    Computer IM but I'm certainly some type of technology. I have basic computer knowledge and that's all.

    You can download minidump files and find the information system here in this zip file http://www.sendspace.com/file/mfx420

    This issue is very very irritating and has ruined a lot of my work.

    Well up to now (18 hours) my computer has not had the BSOD and what I did is that I removed 1 GB of ram for my motherboard. Their were two sticks of 512 MB. I took them both. Now, I have 2 GB of ram running in my system and had not had a BSOD or an error after you have done this.

    What is the problem with my ram? I now have 2 sticks of RAM on my motherboard and both are 1 GB each stick. What is the mix n match that causes a problem all of a sudden? My computer came with this stock of installation. I also noticed the ram I got were the brand Samsung and the other on my motherboard are another brand.

    Well idk I hope it was my problem. We'll see.

  • Blue screen of death, the PC toshiba laptop!

    Ive been doing blue screen of death, what happens is that when I start my laptop it goes to the windows loading screen and it doesn't go to the login screen. It automatically restarts and the same thing happens. The error is as follows:

    Stop: 0 x 00000024 (0 x 00190203, 0x8A9D4828, 0xC0000102, 0x00000000)
    Ive had 2 technicians and really I just have trouble according to them to solve the problem, sometimes I do not trust what they do and others, I have just 17 so I just try to be careful.
    Anyway, I've heard of what is called a CHKDSK with the windows disc and it would continue with a windows disc, Ive tried the windows disc and when I press R on my keyboard, it just says: can not find a hard drive.
    My priority here is now all of my files and solve the problem.

    If it supports booting from a flash drive, and you have one, put this on it then run it .

    0 x 00000024 can mean the hard disk is full error / corrupt / failing and should be replaced as well

  • Blue Screen of Death - Windows 7

    Hello world!

    I'm really upset with my laptop, these a few days ago. Recently, I had the BSOD over and over again. I use Windows 7 (32 bit) on my HP 14-d008AU. I also looked for answers on the web, tried everything, and I still get this BSOD.

    He looked enough like this (I guess).

    Can someone help me with the please my problem?

    Thanks in advance! I waiting for your answers.

    And then I just already this ut myself. So for all those who are going to have this kind of problem. Before you do all these things as the restoration of the system or other method of troubleshooting. Make a troubleshooting first material. What I did was removed the RAM, cleaned with an eraser and brushing decision-making. After that, simply put in its place. Since I did that, I never had the BSOD again.

    I hope it will work for you too!

  • State of power failure - Blue Screen Of Death - Windows Vista driver

    My computer broke down 5 times, twice on 16, then once 18, 21 and now today, January 31, 2014.

    The minidump file identifies the following as the culprit in all 5 cases:
    File name: ntkrnlpa.exe
    Address of the stack: ntkrnlpa.exe + f5a98
    Address: 0 x 82438000
    Address: 0x827f1000
    Size: 0x003b9000
    Time stamp: 0x4cb715e0
    Time warp: 15/10/2010 12:38:24 AM
    Product name: Microsoft® Windows® Operating System
    File description: NT kernel & system
    File version: 6.0.6001.18538 (vistasp1_gdr.101014 - 0432)
    Company: Microsoft Corporation
    Full path: C:\Windows\system32\ntkrnlpa.exe
    Please tell us what actions I need to take to prevent or reduce this incident?
    Please note that I am not a computer scientist, but I can follow directions - I found the software Nirsoft of this forum which allowed me to access the above minidump file.
    Hoping you can help.

    Thank you!

    All attached files of the DMP are the bug check DRIVER_POWER_STATE_FAILURE (9f) .

    This bug check indicates that the driver is in an inconsistent or invalid power state.

    If we run one! Check irp on the 4th parameter of the bug, we get the following:

    > [16, 2] 0 00000000 87976288 8243cdb4-893e5a90 success error e1 cancel pending
    \Driver\rt2870 nt! PopRequestCompletion

    ^^ rt2870 = rt2870.sys which is the Ralink 802.11 USB Wireless Adapter driver. Also used by Linksys and D-Link. Make sure that this driver is up to date:

  • Blue Screen of Death - Windows 7 product # QW743AA #ABC

    This is a first time for me and unable to solve the problem.  Even though I have 4 the OS recovery disks I still can't solve the problem.  I would be grateful some support and thank you to you all!

    I'm always looking for my files... it certainly isn't an easy process.

    And I'm not sure that all of my files have been saved... for the life of me I am not able to find some of them, but I'll keep trying.

    Thank you very much for your support.

    With your advice, I appreciate what I've been able to accomplish.

    Once again thank you,

    Winn

  • Windows Update and Blue Screen of Death

    Hello

    I use a laptop ASUS X550C of windows 8.

    The problem that seems to have the laptop is blue screen of death after a second batch of updates.

    I think that some updates are not compatible with the hardware, but I don't know which.

    Kindly help as soon as possible.

    Thank you

     We need the log files themselves (called a DMP files) because they contain the only record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.


    Please follow our instructions to find and download the files, we need to help you fix your computer. They can be found at here

    If you have any questions regarding the procedure, please ask


  • Blue Screen of death - now cannot load Windows (even in safe mode)

    Laptop last night (Satellite L500-19Z;) Win 7 64 bit) crashed while playing CIV4. Had a blue screen of death. before I had the chance to read one of the error messages about the computer restarted.

    It loaded windows in SafeMode very well then and informed me that he had loaded OK the problem safe mode will be linked to some recently installed software and I should uninstall programs I had installed until it loads normally. As it was late last night I closed and thought I would sort the morning (with the benefit of hindsight it may have been a mistake...).

    Today, when the computer tries to start, it tries a startup repair; Unfortunately it does not work every time and it says "Startup Repair tried several times but still cannot determine the cause of the problem"

    I looked at the paper it produces, but it passes all of the individual tests.

    I can't access also advanced recovery options system & support, that appears in the Startup Repair dialog box as it requires that I be connected, which apparently I am not (probably the machine never got to the windows screen connection before attempting repair system). The error message reads "you must be logged to access system recovery options. If you encounter problems to connect, please contact your computer administrator for help. Please click OK to restart the computer. »

    I had a go at the start in the advanced options (safe mode, safe mode with command etc., but the result is the same).

    I also tried the repair of your computer to the screen option options advanced boot, but after the screen where it asks you to choose the language and keyboard, I get the same error of connection mentioned above.

    Is it possible to repair or even run windows based hard drive recovery (do not have the DVD of recovery with me as I'm away from home for a few weeks) without connecting to windows? I expected here, but have not yet find a way to do it.

    (there is no disc in the disc drive, no other devices connected to the laptop - I tried with power outlet and the battery and have not noticed differences)

    Thank you
    James

    Hello

    Pitty, you cannot retrieve the HEXADECIMAL code
    On this side, I think that your HD or registry is damaged and you have to reinstall the entire system

    Good luck

    Post edited by: Praepositus

  • Windows 7 clean installation Blue Screen of Death (BSoD) on a loop of reboot

    Aloha everyone,
    I did an install customized windows 7 on a new Western Digital 1 TB sata hard drive, which has been formatted, partitioned, scandisk, and a ntfs c drive was created prior to installation.
    The installation ended safely.  I then install my screen reader, Window-Eyes, requiring a reboot.  After the reboot, I started to install critical updates to Windows.  On my fourth update and restarting, I got the blue screen of death, that of some people call a BSoD.  I rebooted and Windows itself restored to a previous state of good, of my just accept the default choice.  Then the rear computer works, but if I stop, restart I get the blue screen of death (BSod) is back, and the loop begins again, i.e. windows restores good condition that works well, until you stop, but on reboot - BSoD is BACK!
    I removed the automatic update option, I disabled ScanDisk, drivers updated, bluetooth devices, deactivated sideshow, etc., without any positive result.  I called Microsoft for assisstance and the technician acted like this isn't a known issue, but he assured me that he could solve the problem.  He took control of my computer remotely and do not tell me anything except that the computer would check and repair any problem on reboot, and if he did does not resolve the problem, I have to remember.  The computer has rebooted without the BSod, but I stopped to check if the loop went, and it is not!  To restart the BSOd was back.  It is to note that if I put the computer to sleep, I get a clean start, but stop, restart or hibernation, I get the blue screen of death (BSoD)!
    It is a Dell Dimension XPS 420 with a intel Q6600 processer, 3 GB of ddr2 memory, which came with OS Vista Home premium 32-bit.  The Vista system, the last time I got a BSoD has been for more than a year.

    After researching this problem on Google, it appears that there is a problem without a solution.
    I ran "which has crashed, you can get:
    http://www.resplendence.com/downloads

    The following accident report:
    Monday, December 21, 2009 23:23:44 your computer crashed
    This was probably caused by the following module:
    Wininit.exe
    Bug check code: 0xF4 (0x3, 0xFFFFFA800573B060, 0xFFFFFA800573B340, 0xFFFFF80002D91240)
    Error:
    CRITICAL_OBJECT_TERMINATION
    Empty the file: C:\Windows\Minidump\122109-16972-01.dmp
    file path: C:\Windows\system32\wininit.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: Application to Windows startup
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Monday, December 21, 2009 20:22:10 crashed your computer
    This was probably caused by the following module:
    Ntoskrnl.exe
    Verification of error code: 0 x 50 (1, 0xFFFFF80002A9300C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
    Error:
    PAGE_FAULT_IN_NONPAGED_AREA
    Empty the file: C:\Windows\Minidump\122109-33306-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: NT Kernel System &
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Sunday, December 20, 2009 15:28:42 crashed your computer
    This was probably caused by the following module:
    Ntoskrnl.exe
    Verification of error code: 0 x 50 (1, 0xFFFFF80002ADC00C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
    Error:
    PAGE_FAULT_IN_NONPAGED_AREA
    Empty the file: C:\Windows\Minidump\122009-17565-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: NT Kernel System &
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Thursday, December 17, 2009 12:27:45 AM your computer crashed
    This was probably caused by the following module:
    Ntoskrnl.exe
    Verification of error code: 0 x 50 (1, 0xFFFFF80002A9300C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
    Error:
    PAGE_FAULT_IN_NONPAGED_AREA
    Empty the file: C:\Windows\Minidump\121609-28111-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: NT Kernel System &
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Monday, December 14, 2009 20:59:21 crashed your computer
    This was probably caused by the following module:
    Wininit.exe
    Bug check code: 0xF4 (0x3, 0xFFFFFA80059A3060, 0xFFFFFA80059A3340, 0xFFFFF80002DC4240)
    Error:
    CRITICAL_OBJECT_TERMINATION
    Empty the file: C:\Windows\Minidump\121409-25506-01.dmp
    file path: C:\Windows\system32\wininit.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: Application to Windows startup
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Sunday, December 13, 2009 02:17:55 your computer crashed
    This was probably caused by the following module:
    Wininit.exe
    Bug check code: 0xF4 (0x3, 0xFFFFFA80058A4060, 0xFFFFFA80058A4340, 0xFFFFF80002D8A240)
    Error:
    CRITICAL_OBJECT_TERMINATION
    Empty the file: C:\Windows\Minidump\121209-24648-01.dmp
    file path: C:\Windows\system32\wininit.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: Application to Windows startup
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Conclusion
    6 dumps were found and analysed. Note that it is not always possible to
    assert with certainty whether a reported driver is really responsible for crashing
    your system or that the cause is in another module. However, it is suggested
    looking for updates for the products that these drivers belong to and regularly
    Visit the Windows Update or activate the automatic updates for Windows. In the case of a piece of
    defective material is in trouble, a Google search on the bug control
    Errors, as well as the name of the model and brand of your computer can help you investigate
    This further.
    end of the crash report.
    A side comment:
    Them are 56 reported problems, and none of them have solutions. If I go through each problem report and check for solutions, about 80% of the times I ask myself to send to Microsoft for more information about the problem and I click on send, but I always get the following:
    [Window title]
    Incident reports

    [Main instruction]
    Problem connecting to the Windows error reporting service

    [Content]
    Some of the reports can not be uploaded to the Windows error reporting service. Please try again later.

    [Close] »
    I tried several times with the same result, that is, the details of the problem which has need of Microsoft is not be received.  To this end, the problem will not be found.
    Thanks much for any help.
    Manny
    P.S. I'll never upgrade a Windows operating system.  My recommendation for anyone who is planning to upgrade to Windows 7 is to try first on a dual boot using the free download.  If it works for you, consider yourself lucky and buy the upgrade.  If it does not, then remove Windows 7 and stay with your old system.

    Please check your RAM for errors (use memtest86 + to test). "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

  • Windows blue screen of death (ASF) when I play Garrysmod

    Windows blue screen of death (ASF) when I play Garrysmod

    Hey,.

    When I started to play Garrysmod (GMod) as blue screen arrives (happened 2 twice now)...

    Signature of the problem:
    Problem event name: BlueScreen
    The system version: 6.1.7600.2.0.0.256.1
    Locale ID: 2057

    More information about the problem:
    BCCode: 101
    BCP1: 0000000000000061
    BCP2: 0000000000000000
    BCP3: FFFFF880009E7180
    BCP4: 0000000000000001
    OS version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Operating system: Windows 7

    Graphics card: Nvidia Geforce 9800 Gt

    If you want something else, ask here.

    Help, please!

    Thank you

    Christopher Kelly

    CEO Christopher Kelly - ChrisJets432 - ChrisJets Corporation - Check http://cjcw.sm4.biz/ for updates, etc.

    Right, I found the problem, the card (s) has an addon called HDR source and what is the cause of the crash.
    For example on gm_construct that I never go on the plan, due to the fact it triggers it

  • Blue screen of death (stop 0x0000007B) after April Windows Update on XP Home.

    My machine (Dell Dimension 3100 with XP Home) home is set for automatic recovery of Windows updates. I reload often, but when I was forced to start again last week, I got the blue screen of death. Apart from the general BSOD error message, I got the stop code:

    STOP 0x0000007B...

    I forgot the subsequent stop codes, but search recall I was doing on them indicated drivers disk or storage-related problem.

    I ran all sorts of Dell diagnostics on my hardware, get absolutely no problem. Scan of a viral infection was also negative. A colleague help out me suggested removing the updates of Windows of April, he did help and usefulness of the ERD. XP loaded and started after that, if I had to go through a process of slooow restart for most updates. My office also now charge many times slower - I suspect drivers and services can't find what they expect to find and take considerable time to make mistakes.

    My Dell has a range of Intel (RAID-1) matrix installed. I strongly suspect that this pilot was in trouble after the April update Windows Update.

    So, what should I do to prevent this from happening again? I don't know the specific fix involved. I have disabled the automatic updates for now.

    TIA

    Rick

    Complete sweep of Kaspersky AV, booted from the CD, turned up negative, so I doubt that it is an infection.

    I'm sorry, but this does not exclude the possibility of infection. See step # 3 in my previous response, or contact Ms. PCSafety for assistance.

    Or see http://msdn.microsoft.com/en-us/library/ff559218 (VS.85) .aspx and/or http://aumha.org/a/stop.php#0x7b for more troubleshooting ideas.

    Or if you let Windows Update to install an update for the driver (never a good idea), try a roll-back of pilot.

    ~ Robear Dyer (PA Bear) ~ MS MVP (that is to say, mail, security, Windows & Update Services) since 2002 ~ WARNING: MS MVPs represent or work for Microsoft

  • Blue Screen of Death After Windows Update

    I was out of the House one night and while outside, my cell phone went through a routine Windows Update and restarted (what he did specifically I'm not aware of). Unfortunately, when I came back, I met a blue screen of death. I tried a system repair and restoration of the system, and none of them worked. I'm typing this from my wife's computer as we speak. I am very anxious, and I would like to use my laptop again. If anyone can help, please reply as soon as possible.

    Visit the Microsoft Solution Center and antivirus security for resources and tools to keep your PC safe and healthy. If you have problems with the installation of the update itself, visit the Microsoft Update Support for resources and tools to keep your PC updated with the latest updates.

    MS - MVP - Elephant Boy computers - don't panic!

  • Blue screen of death. Windows xp family on dell e520

    I got the blue screen of death since 10/17 and have found no solution.
    I can't get into safe mode (networking, command, prompt etc.), nor any other
    f8 options option in the menu. I can't change the cache or shading where the blue screen would recommend either.
    Can anyone help

    It seems that this happened during the night with the automatic updates. my brother got up and the screen is stuck on windows stops. It was restarted by pressing the button and this screen comes up with codes such as 0 x 00000050 or 0x0000007e and other codes. nothing I've tried works. I can't get any internet access when I connect to this computer. What are my other options. my mother also lost the discs when this is supplied with the computer.

    any help will be great...

    read this http://www.asklaptopfreak.com/laptop-notebook-help/2006/06/04/blue-screen-when-start-computer/

    some good stuff there for you to try

  • Blue Screen Of Death with Windows Vista

    I am running Windows Vista and after trying to update a NVIDIA Geforce driver, my computer will not start at the top and comes up with the "blue screen of death/Disconnections. Initially it started, but icons were very large and I could finally get the right size. Thought that there was a problem with the driver compatibililty and deleted driver (I think), not knowing that I would not be able to find the original driver. Restarted and it is when I got the dreaded "BSOD" and knew with my computer knowledge, I was in trouble. Tried to reboot and then restart with the Windows disk, with the same results. Past to start in safe mode, normal mode, etc... and does not boot in any mode, when eneter is pushed (of your choice) Unit acts as if it starts successfully, with the small bar down Center of screen scrolling as it should, but then the BOSD rises. Support, not much luck, worked with NVIDIA replaced card video, restarted, same result. Need help please.

    Hello

    Here's a problem similar to yours that I help a CO-OP with.

    See if it helps you too.

    http://answers.Microsoft.com/en-us/Windows/Forum/windows_vista-system/unable-to-successfully-boot-syste-after-trying-to/14523396-5c88-4460-A29E-87d03fa00074

    See you soon.

  • Installation of Powershell 2 on Windows Vista causes Blue Screen of Death

    I tried to install Powershell 2 on my Windows Vista Home Premium (with SP2) machine. I use the Windows6 package. 0-KB968930-x 86.msu. However, in the middle of the installation, I get a blue screen of death, and the computer restarts.

    I don't know if it is a help, but the problem report displayed when the machine came back to the top is as follows:

    Signature of the problem:

    Problem event name: BlueScreen

    The system version: 6.0.6002.2.2.0.768.3

    Locale ID: 2057

    More information about the problem:

    BCCode: 1000008e

    BCP1: C0000005

    BCP2: 00000000

    BCP3: 8FB3DB9C

    BCP4: 00000000

    OS version: 6_0_6002

    Service Pack: 2_0

    Product: 768_1

    Files helping to describe the problem:

    C:\Windows\Minidump\Mini073110-01.dmp

    C:\Users\Martin Lee\AppData\Local\Temp\WER-142803-0.sysdata.xml

    C:\Users\Martin Lee\AppData\Local\Temp\WER25F6.tmp.version.txt

    Hello CodeMunger,

    You can post on the Forum of Microsoft Powershell. Click here for a link to the forums.
    They may be better able to help with your questions.

    Sincerely,

    Marilyn
    Microsoft Answers Support Engineer
    Visit our Microsoft answers feedback Forum and let us know what you think

Maybe you are looking for