Windows 8, BSOD bugcheck 3B, ATI

My machine crashed and when I try to check for solutions to a problem, the service is unable to download files to windows error reporting. I put the minidump on my skydrive here http://sdrv.ms/1h3ntG5

Of a Dumpcheck on the minidump file

Bugcheck 3B {c0000005, fffff880076650b5, fffff8800f42f050, 0}

Probably caused by: atikmpag.sys (atikmpag + 480b 5)

The blue screen that has happened when you try to view a flash video in Internet Explore.

Install the latest driver for ATI graphics card. You can download ATI form site.

After installation, restart and monitor the system.

Ded9

Tags: Windows

Similar Questions

I use 1023TX dm4, and I install the windows 8, it have problem ATI display driver

I use 1023TX dm4, and I install the windows 8, there is an ATI driver problem, I have two screen, one intel, and one is ATI. but ati driver does not, I need to turn off, can you help me?

Hi Tomiko094,

More than likely HP won't to material support for W8 on any system purchased before October 1, 2011. Most of the W7 drivers will work W8.

Have a look here http://goo.gl/hmPRB for a document official on the update of drivers and software

This document here http://goo.gl/CO6uV provides information on the upgrade to Windows 8

I hope this helps.

Windows 7 BSOD and receiver code error BCCode: 9f

Original title: Windows 7 BSOD

Hey guys I just built my first system and it was a lot. I used the trial version of Windows 8 64-bit for about a week I had to wait for my windows 7 to arrive. Windows 8 everything went fine with no problems. Then I installed windows 7 and ever since then, every time I leave my system alone for an hour or two, I'll be back to see that it crashed because of this error message below. Can I use my computer all day, video, editing, etc, but when I close all and leave for an hour, I'll be back to see that I have broke down. I try to leave it overnight to install my steam on games but crashes after about an hour.

Any help would be great.

Error message:

Signature of the problem:

Problem event name: BlueScreen

OS version: 6.1.7601.2.1.0.256.48

Locale ID: 1033

More information about the problem:

BCCode: 9f

BCP1: 0000000000000003

BCP2: FFFFFA80070A4A10

BCP3: FFFFF800047C43D8

BCP4: FFFFFA80097AB010

OS version: 6_1_7601

Service Pack: 1_0

Product: 256_1

Files helping to describe the problem:

C:\Windows\Minidump\122112-20077-01.dmp

C:\Users\Ryan\AppData\Local\Temp\WER-58203-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 offline privacy statement:

C:\Windows\system32\en-US\erofflps.txt

Data sheet:

Intel i5 3570 k @3.4 ghz

Cooler Master Hyper 212 Evo

Z77 UD5H Gigabyte motherboard

EVGA Gtx 670 FTW

Corsair Vengeance 8 GB 1600

Corsair HX 750w PSU

Seagate Barracuda 7200 rpm 1 TB

Cooler Master Storm Stryker

Edit: I thought it might have something to do with memory, so I ran Memtest 86 + 4 hours and had no error: P

Hello

Thanks for posting your query in Microsoft Community!

According to the description, you are receiving BSOD (Blue Screen of Death) and receive the error code BCCode: 9f.

To help you to propose measures to solve the problem, I would appreciate if you could answer the following question:

Did you do changes on the computer before the show?

I suggest to follow the steps of the items listed below and check if it works.

Error message when you try to resume a Windows 7 or Windows Server 2008 R2 to Hibernate computer-based: "Stop 0x0000009F"

http://support.Microsoft.com/kb/977186

Stop error when you upgrade a computer that is running Windows 7 or Windows Server 2008 R2 standby or into hibernation, or when you restart the computer: "0x9F".

http://support.Microsoft.com/kb/975599

stop "0x0000009F" error message when a computer enters and fate of putting into hibernation in Windows 7 or Windows Server 2008 R2

http://support.Microsoft.com/kb/981848

Hope this information helps. For any other corresponding Windows help, do not hesitate to contact us and we will be happy to help you.

Start the upgrade to Windows 7 BSOD

Satellite L300 was running Vista 32 sweet as a nut, never any problems. Upgrading to 7 and twice in the last few weeks have had an error at startup 'Page in the nonpaged area failure'. The Startup Repair utility was not able to fix it, but ok after system startup.

Journal displays all tests OK except:

Root cause found:
---------------------------
Unknown error checking: bugcheck 50. Parameters = 0 x 0, 0x931f2493, 0x9d789000, 0 x 0.

Repair action: repair and checking the integrity of system files
Result: failed. Error code = 0 x 490

No change in hardware/software/updates or the failure of the system before the startup problem.

I would normally think RAM may be suspect, but it seems more likely given the totality of the circumstances that it is Windows 7 that is at fault.

Any thoughts?

Hmm. It of always difficult to say what could be the reason for the BSOD
Above all it s related to a software or hardware problem

I google a bit and result: failure. Error code = 0 x 490 appears also running Vista OS.
So it s not associated with Win 7 only

Maybe it s RAM as you suggested you can try to use only a single module of RAM for test purposes

Windows 7 BSOD

We have recently started getting BSOD on Dell XPS8700 with 16G of Ram, processor I7, Windows 7 Professional.

The error is caused by ntkrnlmp.exe, process name: audiodg.exe and (sometimes) can be triggered by her disconnect and reconnect the speaker/headphone cable or line-in cable.

Some of the information from the Minidump is listed below, and zipped Minidump and MSInfo files have been downloaded on this link OneDrive:

https://onedrive.live.com/redir?RESID=685745AE9B3E889E! 106 & authkey =! AOCyTvAkAsOQbVc & ithint = % 2czip

You can provide any help will be greatly appreciated.

Thank you!

Bugcheck 3B {c0000005, fffff800034c2a3e, fffff8800f35ec30, 0}

Probably caused by: ntkrnlmp.exe (nt! KiSignalSynchronizationObject + 4th)

System_service_exception (3B)
An exception occurred during the execution of a system service routine.
Arguments:
Arg1: 00000000c 0000005, Exception that caused the error checking code
Arg2: fffff800034c2a3e, the address of the instruction that caused the error checking
Arg3: fffff8800f35ec30, address of the context record to the exception that caused the error checking
Arg4: 0000000000000000, zero.

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0X3B

Nom_processus: audiodg.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: LAPTOP_2

ANALYSIS_SESSION_TIME: 12/05/2016 00:17:05.0764

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800034c2a3e

STACK_TEXT:
fffff880 '0f35f610 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiSignalSynchronizationObject + 0x4e

Update the driver Realtek Audio version 6.0.1.7525:

http://downloads.Dell.com/FOLDER03113490M/1/XPS-8700_Audio_Driver_MN0T2_WN32_6.0.1.7525_A00.exe

This file automatically installs automatically after downloading. Reboot required.

Update Intel AMT HECI driver to version 11.0.0.1153:

http://downloads.Dell.com/FOLDER03130113M/1/XPS-8700_Chipset_Driver_VJ54R_WN32_11.0.0.1153_A00.exe

Installation

1. navigate to the location where you downloaded the file, and then double-click the new file.

2. read the information about the version presented in the dialogue window.

3. download and install all of the components required in the dialogue window before proceeding.

4. click on the button to install.

5. follow the remaining prompts to perform the update

Update the Chipset Intel version 10.1.1.7:

http://downloads.Dell.com/FOLDER03130099M/1/XPS-8700_Chipset_Driver_CR5PJ_WN32_10.1.1.7_A00.exe

This file automatically installs automatically after downloading. Reboot required.

The 7260 Intel Wireless Driver version 17.1.0 update:

http://www.Dell.com/support/home/us/en/19/drivers/DriversDetails?driverId=VXCDN&FILEID=3493199299&osCode=W764&ProductCode=XPS-8700&LanguageCode=en&CategoryID=NI

Intel rapid storage technology driver update to version 14.5.0.1081:

http://downloads.Dell.com/FOLDER03127021M/1/XPS-8700_Serial-ATA_Driver_C2JM0_WN32_14.5.0.1081_A00.exe

This file automatically installs automatically after downloading. Reboot required.

Updated the Realtek network driver 8111E to version 10.1.505.2015:

http://downloads.Dell.com/FOLDER03184762M/1/XPS-8700_Network_Driver_5Y97W_WN64_10.1.505.2015_A01.exe

Update the Nvidia graphics driver to version 10.18.13.5324:

http://downloads.Dell.com/FOLDER03102665M/1/Video_Driver_086XM_WN32_10.18.13.5324_A00.exe

Stop Windows 7 BSOD 0x0000000A code

Hello

I started having BSOD in my two year, Windows 7 Home Premium edition desktop PC on 08/12/15 after an automatic update of Windows and then get their most frequently every day since. The minidump lists always stop Code A to NTOSKRNL.exe + 73c40 as the offending code. What I've tried so far:
- BlueScreenView installed
- Opened the case and clear any dust of fittings of air circulation where it could have been due to overheating
- A ran Memtest86 for 10 assists without reported errors (8G of RAM)
- A ran chkdsk with no error reported.
- Tried to manually run Windows Update - get BSOD Stop Code 50
- Tried running a full virus scan - get BSOD
- Uninstalled SuperAntiSpyware and Avast, install MSE - produced complete sweep of the BSOD
- Run the full scan MSE properly in Mode safe
- Using Device Manager, try to update the drivers one by one in Safe Mode. Among those that I tried, most respond that the existing driver is up-to-date. The ATI/AMD video driver did however update. However, as soon as I press the mouse in Normal mode, he returned BSOD.
I'm not a gamer nor I am overclocking (whatever it is) anything. I would like to believe that my BSOD is related to the software, but am now short of ideas on how to proceed.

The only two actions absolutely will be 100% of the time product Code A BSOD Stop are: 1) try any virus (quick or full) of any of the three scanners scan I tried - get the BSOD in a minute; and (2) try a Windows Update - produced the BSOD once I select an update to download and install. Otherwise, they seem to appear randomly in about 5 minutes after the start.

I think my next steps are:
1. Restore the PC to a restore before the 08/12/15 point (but then how I never go forward again?)
2. Try the driver verifier (although the debate surrounding this step sounds scary)
3. Repair Windows from the CD (although if it is a non-Windows, the origin of the problem driver, how can he help?)
4. Re-install Windows on a hard drive clean (a lot of work to reload everything)
5. Buying a new PC (groan)
Any help would be greatly appreciated.

The most recent minidump are at: https://www.dropbox.com/s/savjud82p70i6io/121715-16894-01.dmp?dl=0

Hello

We can successfully close this thread. The source of my BSOD has proved to be the four old vestige McAfee drivers. My Dell PC of 2012 has been preloaded with McAfee and I must not have successfully uninstalled three years ago. For anyone else who may be looking for a BSOD from 0 to stop Code referencing NTOSKRNL.exe + 73c40, the key for me was to find a file to mcafee under c:\program files\common files and also several pilot named MFExxxx.sys in the folder c:\windows\system32\drivers. When I ran check, he scored these MFE drivers as being loaded. I don't know exactly how and why they were active in my PC. Maybe a registry key to load. Since McAfee is not listed as a product registered in my PC, they have not updated successfully since installation in 2012. They were apparently benign drivers for the last 3 years until 08/12/15 Windows Update which turned them into little evil monsters. To remove all the remains of McAfee, search for "Tool McAfee Consumer Product Removal" in your favorite browser. Download and run the latest version of MCPR.exe to purge your system. No BSOD more.

Ken

Windows 7 BSOD Dump

I'm looking for help with my BSOD dump. As far as I can tell, the research that the core of the system is having a problem. Can someone tell me exactly what can happen? Dump below.

--------------------------------------------------------------------------------------
Microsoft (R) Windows debug 6.12.0002.633 AMD64 Version
Copyright (c) Microsoft Corporation. All rights reserved.

Loading dump file [C:\Windows\Minidump\102615-19063-01.dmp]
The mini kernel dump file: only registers and the trace of the stack are available

Symbol search path is: SRV * C:\Windows\symbol_cache* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 processors) free x 64
Product: WinNt, suite: TerminalServer SingleUserTS
By: 7600.16385.amd64fre.win7_rtm.090713 - 1255
Computer name:
Kernel base = 0xfffff800 '0302 c 000 PsLoadedModuleList = 0xfffff800' 03269e50
The debugging session: 18:56:39.560 Mon 26 Oct 2015 (UTC - 04:00)
System Uptime: 0 days 0:00:12.183
Loading the kernel symbols
...............................................................
....................................................
Loading user symbols
Loading unloaded module list
.
*******************************************************************************
* *
* Bugcheck analysis *.
* *
*******************************************************************************

Use! analyze - v to obtain detailed debugging information.

Bugcheck 50, {fffff8a005070000, 0, fffff800030ec69e, 0}

WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe

Could not read the name of the problem driver
Probably caused by: ntoskrnl.exe (nt_fffff80003000000 + 2a 49)

Follow-up: MachineOwner
---------

1: kd >! analyze - v
*******************************************************************************
* *
* Bugcheck analysis *.
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
It must be protected by a probe. In general, the address is simple bad or it
pointing to freed memory.
Arguments:
Arg1: fffff8a005070000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030ec69e, if not zero, the address of the instruction that refers to bad memory
address.
Arg4: 0000000000000000, (reserved)

Debugging information:
------------------

Could not read the name of the problem driver

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032d40e0
fffff8a005070000

FAULTING_IP:
NT! wcsrchr + 6
fffff800'030ec69e 0fb701 movzx eax, word ptr [rcx]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0 X 50

Nom_processus: smss.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88002e71570-(.trap 0xfffff88002e71570)
NOTE: The frame trap does contain not all registers.
Some registry values can be set to zero or incorrect.
Rax = 000000000000000c rbx = 0000000000000000 rcx = fffff8a005070000
RDX = 000000000000005c rsi = 0000000000000000 rdi = 0000000000000000
RIP = fffff800030ec69e rsp = fffff88002e71708 rbp = fffff8000324b4a8
R8 = 0000000000000000 r10 = 0000000000501902 fffff8a00506ffc0 = r9
R11 = 0000000000000000 r12 = 0000000000000000 r13 = 0000000000000000
R14 = 0000000000000000 r15 = 0000000000000000
iopl = 0 nv up ei pl nz na po nc
NT! wcsrchr + 0 x 6:
fffff800'030ec69e 0fb701 movzx eax, word ptr [rcx] ds:1902:fffff8a0'05070000 =?
Reset the default scope

LAST_CONTROL_TRANSFER: from fffff8000311d1e4 to fffff8000309df00

STACK_TEXT:
"fffff880 '02e71408 fffff800' 0311d1e4: 00000000'00000050 fffff8a0 ' 05070000 00000000 00000000' fffff880 ' 02e71570: nt! KeBugCheckEx
fffff880 '02e71410 fffff800' 0309bfee: 00000000'00000000 00000000'00000001 fffffa80 '08 a 17000 00000000' 00000160: nt! : FNODOBFM: 'chain' + 0 x 42907
fffff880 '02e71570 fffff800' 030ec69e: fffff800 '03002-49 fffff880' 02e717b0 00000000'00000001 00000000'00000000: nt! KiPageFault + 0x16e
fffff880 '02e71708 fffff800' a 03002, 49: fffff880'02e717b0 00000000'00000001 00000000'00000000 00000000'00000000: nt! wcsrchr + 0 x 6
fffff880 '02e71710 fffff880' 02e717b0: 00000000'00000001 00000000'00000000 00000000'00000000 00000000'00000002: nt_fffff80003000000 + 0x2a49
fffff880'02e71718 00000001' 00000000: 00000000'00000000 00000000'00000000 00000000'00000002 fffff800'0307e0d2: 0xfffff880'02e717b0
fffff880 '02e71720 00000000' 00000000: 00000000'00000000 00000000'00000002 fffff800 '0307e0d2 00000000' a 0000030: 0 x 1

STACK_COMMAND: kb

FOLLOWUP_IP:
nt_fffff80003000000 + 2 has 49
fffff800'03002 has 49? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt_fffff80003000000 + 2 has 49

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt_fffff80003000000

Nom_image: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 550e41b6

FAILURE_BUCKET_ID: X64_0x50_nt_fffff80003000000 + 2 has 49

BUCKET_ID: X64_0x50_nt_fffff80003000000 + 2 has 49

Follow-up: MachineOwner
---------

1: kd > lmvm nt_fffff80003000000
start end module name
fffff800 '03000000 fffff800' nt_fffff80003000000 03016000 T (no symbol)
Loaded symbol image file: ntoskrnl.exe
Image path: \SystemRoot\system32\ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Sun Mar 22 00:14:46 2015 (550E41B6)
CheckSum: 00014804
ImageSize: 00016000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
1: kd > .trap 0xfffff88002e71570
NOTE: The frame trap does contain not all registers.
Some registry values can be set to zero or incorrect.
Rax = 000000000000000c rbx = 0000000000000000 rcx = fffff8a005070000
RDX = 000000000000005c rsi = 0000000000000000 rdi = 0000000000000000
RIP = fffff800030ec69e rsp = fffff88002e71708 rbp = fffff8000324b4a8
R8 = 0000000000000000 r10 = 0000000000501902 fffff8a00506ffc0 = r9
R11 = 0000000000000000 r12 = 0000000000000000 r13 = 0000000000000000
R14 = 0000000000000000 r15 = 0000000000000000
iopl = 0 nv up ei pl nz na po nc
NT! wcsrchr + 0 x 6:
fffff800'030ec69e 0fb701 movzx eax, word ptr [rcx] ds:1902:fffff8a0'05070000 =?

Good work on win debugger

First of all, you need to update to SP - 1

Service pack 1 update.

http://Windows.Microsoft.com/installwindows7sp1

Learn how to install Windows 7 Service Pack 1 (SP1)

http://Windows.Microsoft.com/en-us/Windows7/learn-how-to-install-Windows-7-Service-Pack-1-SP1

Additional resources:
http://Windows.Microsoft.com/en-us/Windows7/uninstall-SP1
http://Windows.Microsoft.com/troubleshootwindows7sp1

If you continue to plant

These accidents were related to the corruption of memory (probably caused by a driver).

Run these two tests to check your memory and find which driver is causing the problem. Launch auditor. You don't need to run memtest again unless the auditor is not the cause, or you want to.

If you are overclocking anything reset by default before running these tests.

In other words STOP! If you don't know what it means that you're probably not

1-Driver Verifier (for full instructions, see our wiki here)

2-Memtest. (You can learn more about running memtest here)

Windows 7 BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Hey, I really need help with this problem, today 13/10/2013, I got a BSOD at 04:14. For more details, I enclose the minidump here:

https://SkyDrive.live.com/?v=FirstRunView#CID=ffeb8e1ecdbb1c20

If you could help me I will be very proud. Cordially, Cristian.

Thank you!

The attached file of the DMP is the error checking SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) .

This indicates that a system thread threw an exception who did not catch the error handler.

Bugcheck 1000007E, {c0000005, 82e24734, 8ab1f648, 8ab1f220}

^^ The 1st parameter of error c0000005 checking indicating an access violation has occurred, we will see what caused:

: kd > .exr 0xffffffff8ab1f648
ExceptionAddress: 82e24734 (nt!) RtlEqualUnicodeString+ 0x0000002f)
ExceptionCode: c0000005 (access violation)

It was caused by RtlEqualUnicodeString which is the routine compares two Unicode strings to determine if they are equal. Most likely a related device driver.

----------------------------------------

Remove and replace avast! with Microsoft Security Essentials for purposes of troubleshooting temporary:

avast!-removal tool from http://www.avast.com/uninstall-utility

MSE - http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download

In your list of drivers loaded, dtsoftbus01.sys figure who is the driver for Daemon Tools. Daemon Tools is a very popular cause of BSOD in 7/8 base systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

Kind regards

Patrick

Windows 7 BSOD ntoskrnl.exe question

Hello. I'm having the same problem as the next person - http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/ntoskrnlexe-1040b-e58d2-6d5be/ea3a3e93-69bd-47c7-9f31-ddb723120912. I ran Driver Verifier and then encountered the problem of not being able to access my laptop normally. I disabled the driver verifier now.

I redid my laptop about 3 times in the hope of solving my BSOD problem, but it is ongoing.

Any help is appreciated.

David Martinez

THE

They are related to your video driver. I would like to begin by updating to the latest driver that yours is ~ 1 year.

Microsoft (R) Windows debug 6.3.9600.17029 AMD64 Version
Copyright (c) Microsoft Corporation. All rights reserved.

Loading dump file [C:\Users\Ken\Desktop\052814-20592-01.dmp]
The mini kernel dump file: only registers and the trace of the stack are available

Symbol of validation of the path summary *.
Location of response time (ms)
Deferred SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) free x 64
Product: WinNt, suite: TerminalServer SingleUserTS
By: 7601.18409.amd64fre.win7sp1_gdr.140303 - 2144
Computer name:
Kernel base = 0xfffff800'02e63000 PsLoadedModuleList = 0xfffff800'030 was 6890
The debugging session: 14:44:02.483 Wed 28 may 2014 (UTC - 04:00)
System Uptime: 0 days 0:02:46.482
Loading the kernel symbols
...............................................................
................................................................
..................................................
Loading user symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************

Use! analyze - v to obtain detailed debugging information.

BugCheck C4, {c0, fffffa800a546340, f6, fffff8800f2b9879}

WARNING: Unable to verify timestamp for nvlddmkm.sys
ERROR: Module load completed but symbols can be loaded for nvlddmkm.sys
Probably caused by: nvlddmkm.sys (nvlddmkm + 9a 879)

Follow-up: MachineOwner
---------

2: kd >! analyze - v
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has taken. It comes
because the driver was specified in the registry as being suspect (by the)
Administrator) and the kernel has allowed substantial control of this driver.
If the pilot attempts to corrupt the system, looking for bugs, 0xC4, 0xC1, and 0xA
Be one of the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, handle user SEO as the core.
Arg2: 00000000000000c 0, the value of Handle referenced.
Arg3: fffffa800a546340, address of the current process.
Arg4: fffff8800f2b9879, address inside the pilot making the incorrect reference.

Debugging information:
------------------

BUGCHECK_STR: 0xc4_f6

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

Nom_processus: rundll32.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers (dbg). 140219-1702) amd64fre

LAST_CONTROL_TRANSFER: from fffff800033654ec to fffff80002ed8bc0

STACK_TEXT:
"" fffff880 ' 0 c 315308 fffff800 ' 033654ec: 00000000 ' 000000 c 4 00000000' 000000f6 00000000'000000 c 0 fffffa80 ' a 0, 546340: nt! KeBugCheckEx
"" fffff880 ' 0 c 315310 fffff800 ' 0337abf4: 00000000 ' 000000 c 0 fffffa80 ' 0a 546340 00000000'00000004 fffff880'0 c 317000: nt! VerifierBugCheckIfAppropriate + 0x3c
fffff880 ' 0 c 315350 fffff800' 03132890: fffff8a0 '000016-0 fffff880' 0c3155a0 fffff880 '0 c 315700 fffff880' 0c 315930: nt! VfCheckUserHandle + 0x1b4
"fffff880 ' 0 c 315430 fffff800 ' 031a95b5: 00000000 '00000000 fffff880' 00000001 fffffa80 '06067f30 fffff8a0' 05c08a00: nt! : NNGAKEGL: 'string' + 0x2027e
"fffff880 ' 0 c 315500 fffff800 ' 02ed7e53: fffffa80 '0aa1e060 fffff880' 0c3158b8 00000000'00000002 00000000'00000000: nt! NtQueryValueKey + 0 x 115
"" fffff880 ' 0 c 315690 fffff800 ' 02ed4410: fffff800 ' 03369 d 96 fffff880 ' 0f2b9879 fffff880 '0 c 315930 fffff880' 0c 315928: nt! KiSystemServiceCopyEnd + 0x13
fffff880 '0 c 315898 fffff800' 03369d 96: fffff880 ' 0f2b9879 fffff880 '0 c 315930 fffff880' 0c 315928 fffff800 ' 02ed4410: nt! KiServiceLinkage
"fffff880 '0c3158a0 fffff880' 0f2b9879: fffff880 ' 0c3168ca fffff880 ' 0 c 315970 fffff880 ' 0c3168b8 fffffa80 ' 0591ff18: nt! VfZwQueryValueKey + 0 x 76
fffff880 '0c3158f0 fffff880' 0c3168ca: fffff880' 0591ff18 fffff880 '0c3168b8 fffffa80' 0 c 315970 00000000 00000000': nvlddmkm + 0x9a879
fffff880'0c3158f8 fffff880'0 c 315970: fffff880 '0c3168b8 fffffa80' 0591ff18 00000000 00000000' fffff880 0'c 315920: 0xfffff880'0c3168ca
"fffff880 ' 0 c 315900 fffff880 ' 0c3168b8: fffffa80'0591ff18 00000000 00000000' fffff880 ' 0 c 315920 fffff980' 00000000: 0xfffff880'0 c 315970
"fffff880 ' 0 c 315908 fffffa80 ' 0591ff18: 00000000 '00000000 '0c 315920 fffff980'00000000 00000000 fffff880' 000000 c 0: 0xfffff880'0c3168b8
fffff880'0 c 315910 00000000 00000000': fffff880 '0 c 315920 fffff980' c 0 00000000 00000000'000000 ' 00280026 fffffa80: 0xfffffa80'0591ff18

STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm + 9 has 879
fffff880'0f2b9879 3d340000c0 cmp eax, 0C0000034h

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: nvlddmkm + 9 has 879

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

Nom_image: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5280da75

FAILURE_BUCKET_ID: X64_0xc4_f6_nvlddmkm + 9 has 879

BUCKET_ID: X64_0xc4_f6_nvlddmkm + 9 has 879

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xc4_f6_nvlddmkm + 9 has 879

FAILURE_ID_HASH: {0c031110-986a-b405-c565-3ead8c9b6e45}

Follow-up: MachineOwner
---------

Windows 7 BSOD - happening for awhile now - HELP

Well, I tried to understand it on my own, but I can't install the windows SDK, so I would appreciate help from you guys.

The BSOD usually happens when I leave the computer for long periods of time, only to return to my computer is off.

Wednesday, April 30, 2014 6:04:58 PM GMT crashed your computer
crash dump file: C:\Windows\Minidump\043014-29218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800A9C4A10, 0xFFFFF80000B9C518, 0xFFFFFA800BDFFCC0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
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.

I can't find that one PRI blocked, so if you could help that would be great!

Landfills are:

https://onedrive.live.com/redir?RESID=697CD2CA8EC05636! 182 & authkey =! AHoRjA-BKsOXAgc&ithint=file%2c.rar

Thank you

Josh

Josh

These were related to BCMWL664. SYS 802.11 card Broadcom Corporation wireless network driver. I'd install the most recent driver available.

Microsoft (R) Windows debug 6.3.9600.17029 AMD64 Version
Copyright (c) Microsoft Corporation. All rights reserved.

Loading file Dump [C:\Users\Ken\Desktop\New folder\042914-33774 - 01.dmp]
The mini kernel dump file: only registers and the trace of the stack are available

DbsSplayTreeRangeMap::Add: ignoring size zero range to the? fffff8a0'07894 has 42?
DbsSplayTreeRangeMap::Add: ignoring size zero range to the? fffff8a0'057025 c 2?
DbsSplayTreeRangeMap::Add: ignoring size zero range to the? fffff8a0'0023e022?
DbsSplayTreeRangeMap::Add: ignoring size zero range to the? fffff8a0'04bf9c32?
DbsSplayTreeRangeMap::Add: ignoring size zero range to the? fffff800'00b9c500?

Symbol of validation of the path summary *.
Location of response time (ms)
Deferred SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) free x 64
Product: WinNt, suite: TerminalServer personal TerminalServer
By: 7601.18247.amd64fre.win7sp1_gdr.130828 - 1532
Computer name:
Kernel base = 0xfffff800 '0364a 000 PsLoadedModuleList = 0xfffff800' 0388d6d0
The debugging session: Mon Apr 28 23:59:54.424 2014 (UTC - 04:00)
System Uptime: 0 days 6:54:28.891
Loading the kernel symbols
...............................................................
................................................................
...........................................
Loading user symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************

Use! analyze - v to obtain detailed debugging information.

9F error checking, {3, fffffa8009cfba10, fffff80000b9c518, fffffa800addd010}

Probably caused by: pci.sys

Follow-up: MachineOwner
---------

0: kd >! analyze - v
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A pilot was not a power of the PRI ends in a moment.
Arguments:
Arg1: 0000000000000003, a device object has been blocking an Irp for too long
Arg2: fffffa8009cfba10, physical device from the stack object
Arg3: fffff80000b9c518, nt! TRIAGE_9F_POWER on Win7 and higher, otherwise the functional device object of the stack
Arg4: fffffa800addd010, blocked IRP

Debugging information:
------------------

DRVPOWERSTATE_SUBCODE: 3

Nom_image: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000e00000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0X9F

Nom_processus: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers (dbg). 140219-1702) amd64fre

DPC_STACK_BASE: FFFFF80000BA2FB0

STACK_TEXT:
fffff800 '00b9c4c8 fffff800' 0372f8d2: 00000000' 0000009f 00000000 00000003' fffffa80 '09cfba10 fffff800' 00b9c518: nt! KeBugCheckEx
fffff800 '00b9c4d0 fffff800' 036ca85c: fffff800 '00b9c600 fffff800' 00b9c600 00000000'00000000 00000000'00000002: nt! : FNODOBFM: 'string' + 0x33af0
fffff800 '00b9c570 fffff800' 036ca6f6: fffffa80 '0dad8a48 fffffa80' 0dad8a48 00000000'00000000 00000000'00000000: nt! KiProcessTimerDpcTable + 0x6c
fffff800 '00b9c5e0 fffff800' 036ca5de: 00000039' e703a307 fffff800 '00b9cc58 00000000' 00185325 fffff800'0383 d 728: nt! KiProcessExpiredTimerList + 0xc6
"fffff800 '00b9cc30 fffff800' 036ca3c7: 0000000f'd55b37c4 0000000f ' 00185325 0000000f ' d55b3726 00000000'00000025: nt! KiTimerExpiration + 0x1be
fffff800 '00b9ccd0 fffff800' 036b78ca: fffff800 '0383ae80 fffff800' 03848cc0 00000000 00000001' fffff880' 00000000: nt! KiRetireDpcList + 0 x 277
fffff800'00b9cd80 00000000' 00000000: fffff800'00b9d000 fffff800 '00b 97000 fffff800' 00b9cd40 00000000' 00000000: nt! KiIdleLoop + 0x5a

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.1.7601.17514

FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_bcmwl664_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_POWER_DOWN_bcmwl664_IMAGE_pci.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_bcmwl664_image_pci.sys

FAILURE_ID_HASH: {03ad8a78-2fdb-fcb3-4095-637363008d10}

Follow-up: MachineOwner
---------
IRP is active with 4 batteries 2 is current (= 0xfffffa800addd128)
No Mdl: No system don't buffer: wire 00000000: Irp stack trace.
cmd flg cl device file completion-context
[0, 0] 0 0 00000000 00000000 00000000 - 00000000

Args: 00000000 00000000 00000000 00000000
> [16, 2] fffffa800b933050 0 0 00000000 00000000 - 00000000
Cannot load the image \SystemRoot\system32\DRIVERS\bcmwl664.sys, 0n2 error Win32
WARNING: Unable to verify timestamp for bcmwl664.sys
ERROR: Module load completed but symbols can be loaded for bcmwl664.sys
\Driver\BCM43XX
Args: 00012200 00000000 00000002 00000002
[16, 2] e1 0 fffffa800ba1b270 fffff8000390c200-fffffa800fd17160 00000000 success error cancel pending
\Driver\vwifibus nt! PopSystemIrpCompletion
Args: 00012200 00000000 00000002 00000002
[0, 0] 0 0 00000000 00000000 00000000 - fffffa800fd17160

Args: 00000000 00000000 00000000 00000000
0: kd >! drvobj \Driver\BCM43XX
fffff80003870010: failed to get the value of ObpRootDirectoryObject
Pilot object not found \Driver\BCM43XX

Help Windows 7 BSOD

Hi, I got a new laptop, for a month so that I'll be gone 3 or 4 BSOD.

The BSOD began in early January and it would still be the case when my computer is in mode 'sleep' so once I wake my computer, there will be a window telling me that the computer shut down unexpectedly. So I made a new installation 14. And I got the report this morning that my computer has stopped unexpectedly.

That's what the box said this morning:

Signature of the problem
Problem event name: BlueScreen
OS version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem
BCCode: 9f
BCP1: 00000004
BCP2: 00000258
BCP3: 853CED48
BCP4: 82D3CB24
OS version: 6_1_7600
Service Pack : 0_0
Product: 768_1
Bucket ID: MEMORY_CORRUPTION_ONE_BIT_LARGE

and I found this in the event viewer

The computer was restarted after a bugcheck. The bugcheck was: 0x0000009f (0 x 00000004, 0 00000258, 0x853ced48, 0x82d3cb24). A dump was saved in the: C:\windows\MEMORY. DMP. Report ID: 011910-16114-01.

I am running 32-bit Windows 7 Home Premium
I installed programs:
Firefox
Avast 5
iTunes
CCleaner
Open Office
Foxit Reader
QuickTime
Skype

What's the problem (or how do I know?)

Thank you!

The error is a DRIVER_POWER_STATE_FAILURE but no third-party driver has been designated as causing the accident.

The problem, however, may be the audio driver Realtek High definition.

Try to update this driver from Realtek:

http://www.Realtek.com.tw/downloads/downloadsCheck.aspx?langid=1&PNid=14&PFID=24&level=4&Conn=3&DownTypeID=3&GETDOWN=false

If problems persist after return and make it available to the minidump files.

Also, what computer you have (make and model)?

Windows 7 BSOD - ntoskrnl.exe (nt + 0x7F1C0)

I have this problem since April, 2012

HP support suggested that I should reinstall windows 7. I did some time at the beginning of August, but the problem persists.

Help, please! Otherwise, I'll keep change the OS with a Microsoft OS No.

Here are the dumps:

(Local) information system
computer name: RADU-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
CPU: GenuineIntel Intel (r) Core i5 CPU M 520 @ 2.40 GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4145868800 total
VM: 2147352576, free: 1943330816

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Dumps are enabled on your computer.

Sat 29-Sep-12 12:56:36 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092912-34632-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003344E30, 0xFFFFF8800AEE8C70, 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.

Sat 29-Sep-12 12:56:36 GMT crashed your computer
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: bcm42rly.sys (BCM42RLY + 0 x 1280)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003344E30, 0xFFFFF8800AEE8C70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\bcm42rly.sys
product: Broadcom iLine10 (TM) PCI network card
company: Broadcom Corporation
Description: Broadcom iLine10 (TM) PCI network adapter Proxy Protocol Driver
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: bcm42rly.sys (Broadcom iLine10 (TM) PCI network adapter Proxy Protocol Driver, Broadcom Corporation).
Google search: bcm42rly.sys Broadcom Corporation SYSTEM_SERVICE_EXCEPTION

Sat 29-Sep-12 12:47:59 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092912-34772-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003347E30, 0xFFFFF8800BCDCC70, 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.

Sat 29-Sep-12 12:39:07 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092912-35552-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000333CE30, 0xFFFFF88008D9CC70, 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.

Fri 28-Sept-12 07:30:24 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092812-35630-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003389E30, 0xFFFFF8800C0C5C70, 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.

Fri 28-Sept-12 07:20:56 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092812-58531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003349E30, 0xFFFFF8800ACA9C70, 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.

Play 27 Sept - 12 22:01:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-21606-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x1A (0xFFFFFA8000532F50, 41790, 0 x 0 x 0, 0xFFFF)
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.

Play 27 Sept - 12 09:26:28 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092712-30108-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x19 (0 x 22, 0 x 20000000000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.

The sea 26-Sept-12 07:12:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092612-19734-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs + 0x5A88)
Verification of error code: 0 x 24 (0xFFFFF8800996BAE8, 0xFFFFF8800996B340, 0x1904FB, 0xFFFFF88001231A74)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT file system driver
Bug control description: This indicates there is a problem in the NTFS file system.
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.

Mar 25 - Sep - 12 20:55:48 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092612-22354-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
Bugcheck code: 0x7A (0xFFFFFFFFC0000005, 0xFFFFFA8004646060, 0x1, 0xFFFFF680000B1000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: NT Kernel System &
Bug control description: this bug check indicates that the data page of the kernel of the required paging file cannot be read into memory.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

The game 20-Sept-12 15:08:27 GMT crashed your computer
crash dump file: C:\Windows\Minidump\092012-53929-01.dmp
This was probably caused by the following module: win32k.sys (win32k + 0xC6A12)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000116A12, 0xFFFFF8800AC5B130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
Description: Multi-User Win32 Driver
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 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.

Wednesday, August 7, 12 10:29:53 GMT crashed your computer
crash dump file: C:\Windows\Minidump\080712-41917-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x71F00)
Verification of error code: 0 x 50 (0x0, 0xFFFFF8000311445B, 0xFFFFF8A00B2DF000, 0 x 2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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.
The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

Wednesday, August 7, 12 10:08:21 GMT crashed your computer
crash dump file: C:\Windows\Minidump\080712-53305-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt + 0x1A50F3)
Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002DBB0F3, 0xFFFFF880031A18B8, 0xFFFFF880031A1110)
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.

We need the DMP file because it contains the single record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting in SafeMode (F8) with networking.

Please follow these instructions to collect data against crashes and upload them here, to your Skydrive or a service such as Rapidshare file sharing.

http://www.SysNative.com/forums/showthread.php/68-blue-screen-of-death-%28BSOD%29-posting-instructions-Windows-8-7-amp-Vista?p=303&viewfull=1#post303

http://SysNative.com/0x8/BSOD_Windows7_Vista_v2.64_jcgriff2_.exe

To allow us to help you with symptoms BSOD on your computer, download the contents of your folder "\Windows\Minidump".

The procedure:

* Copy the contents of \Windows\Minidump to another location (temporary) somewhere on your machine.
* Zip up the contents of this folder
Please, upload to skydrive or a file sharing service and put a link to them in your next post.

Go to start > search/run > cmd > msinfo32 and include it in the upload

To ensure the minidumps are enabled:

* Click Start, in the search box, type: sysdm.cpl, press ENTER.
* On the Advanced tab, click Startup and recovery... Settings button.
* Make sure that automatically restart is unchecked.
* Under the writing debugging information header, select image partial memory (256 KB) in the list box drop-down (varies from 256kb).
* Ensure to that small Dump Directory is listed as % systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

http://www.SysNative.com/forums/showthread.php/325-BSODs-but-no-dump-files

http://www.osronline.com/article.cfm?article=545

Please also go to start > run > msinfo32 and record the results. Send it with the DMP files, thank you.

Windows 7 bsod 'Kernel Power' errors and bugs.

I built my own PC and installed windows 7 64-bit. have a lot of stability issues.

I formatted the Partition o/s and re-installed with only minimal software and still blue screens!

Errors in the paper are either checking bug like this... The computer was restarted after a bugcheck. The bugcheck was: 0x0000001a (0xfffffa8001f799d0, 0x000000000000ffff, 0 x 0000000000041790, 0 x 0000000000000000).

Or errors in core like this power: the system has rebooted without judgment properly first. This error can be caused if the system unresponsive, crashed or unexpected power loss.

I have many minidumps etc but no tool to examine the...

In fact, I just them loaded up to my sky drive...

http://CID-af314679bdeeac55.SkyDrive.live.com/self.aspx/.public/041210-16738-01.zip

I have a mirror RAID hardware for my o/s using the matrix aboard the intel RAID Controller and could get a lot of warnings in the log of events like this:

An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

I tried to fix this using the tools for the RAID controller, if I check and repair the volume, then the errors disappear for a few days, but then start again.

I hope that I don't have a hardware problem... I ran the windows recovery options which reported no material error.

The specs of my PC are:

Intel Core i7 950 CPU

ASUS p6t Deluxe V2 mobo with 6 GB of RAM Patriot

2 x WD SATA 300 GB hard drives configured in RAID 1

Videocard ATI Radeon xfx4770

can anyone help me track down the issue? I also have a pro 9000 Logitech webcam that I uninstalled now to see if this is the cause.

See you soon,.

Danrth

Error checking 1a is "MEMORY_MANAGEMENT. This indicates memory corruption has occurred. This may be due to a hardware failure (defective RAM, for example), or a bad/buggy driver.

Consider the following general guidelines to treat the type of memory, corruption problems which could mean a defective hardware such as memory, or a bad driver.

Consider running chkdsk on all partitions. Leave complete chkdsk on each partition and see if that helps.

It may be useful to use the driver verifier. To activate the... Driver Verifier start-> verifier.exe-> OK-> create standard settings-> next-> driver select the names to a list-> next-> sort by provider-> select all other Microsoft drivers-> finish and OK your way out of the dialog box.

Then restart and use the system as you normally and wait for a problem. In case the system does not completely start after activation of the Verifier, boot mode safe and run driver verifier and tell him to remove the changes.

Wait for a bugcheck occurs after you have enabled the auditor as described, and then download the dump on your SkyDrive and provide a link.

Also consider running SFC/scannow.

If you start in safe mode, do you still feel bugs? What if you do a clean boot, or boot device?

Consider the memory with memtest86 or Windows Memory Diagnostic test. Note that memory that pass the tests isn't necessarily good memory - he not only failed a review. Examine systematically to eliminate the system RAM - run with a few modules for awhile and see how things are going. Then try the other modules.

Other common suggestions include ensuring drivers are up to date, but also to ensure that you use the latest version of the BIOS.

64 - bit Windows 8 (BSOD) system service exception error

I couldn't connect on my laptop, after loading Windows, and then on the blue screen (BSOD).

Please help me. Here are the files that you may need to help me.

the Minidump files: https://onedrive.live.com/redir?resid=34DB0826A5470047%21107
information system: https://onedrive.live.com/redir?resid=34DB0826A5470047%21108

Thank you Microsoft... :)

The same bug, check cause. Uninstall AMD/ATI drivers, restart. Later, do not install the version you keep installing and either try a beta version or the version until you have the problem before the update.

Kind regards

Patrick

Satellite A660-1CJ - 8.1 Windows crashes - BSOD bridge.sys

Hello

I have a Satelite A660-1CJ, running Windows 8.1 and he already broke 5 times with a BSOD:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (bridge.sys)

What can I do?

Hello

It seems that the bridge.sys is causing the BSOD.
Bridge.sys is a Windows system component.

Toshiba says that the Windows 8.1 is not supported on Satellite A660 series.
What does that mean?
This means that Windows 8.1 drivers are not released by Toshiba.

I assume that you have installed drivers in your own hand and probably one of the drivers causing the BSOD.

Windows 8, BSOD bugcheck 3B, ATI

Similar Questions

Maybe you are looking for