Windows 8 EventID 1001 BugCheck 0xa1 BSOD

As mentioned I am having a fairly common BSOD problem. I really hope its not a hardware issue as this is a new desktop.
The computer has rebooted from a bugcheck. The bugcheck was: 0xa0000001 (0x0000000000000005, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 031714-23968-01.
Anyway, here is the MEMORY.DMP file:
Please let me know what the problem is asap. This has been happening over the last couple of months, and its completely random and doesn't happen very often which makes me think it is a driver issue of some kind? At least I REALLY hope so...
Ill edit with link to skydrive when upload is complete it is a large file...any thoughts on the bugcheck though?

Irsterrific
For future reference please change your system control panel settings to "small" DMP as it wil make uploading it (and downloading) much faster.
This one crash points to DirectX (dxkrnl.sys) /atikmpag.sys making an incorrect power request to ACPI. I would start by installing the newest driver available.
To ensure minidumps are enabled:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
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 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff803`a7881000 PsLoadedModuleList = 0xfffff803`a7b45990
Debug session time: Sun Mar 16 14:53:56.919 2014 (UTC - 4:00)
System Uptime: 0 days 2:36:01.579
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 44, {ffffe00006ff1a10, f8a, 0, 0}
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiFdoHandleSystemPower+173 )
Followup: MachineOwner
2: kd> !analyze -v
* Bugcheck Analysis *
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: ffffe00006ff1a10, Address of the IRP
Arg2: 0000000000000f8a
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
IRP_ADDRESS: ffffe00006ff1a10
FOLLOWUP_IP:
dxgkrnl!DpiFdoHandleSystemPower+173
fffff800`0233016b e9d8020000 jmp dxgkrnl!DpiFdoHandleSystemPower+0x450 (fffff800`02330448)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff803a7a09b4b to fffff803a79ceca0
STACK_TEXT:
ffffd000`205c6778 fffff803`a7a09b4b : 00000000`00000044 ffffe000`06ff1a10 00000000`00000f8a 00000000`00000000 : nt!KeBugCheckEx
ffffd000`205c6780 fffff803`a797a91a : ffffe000`06ff1a10 fffff803`a7997000 ffffe000`00fe3c28 ffffe000`06ff1a10 : nt! ?? ::FNODOBFM::`string'+0x2a9ab
ffffd000`205c6890 fffff800`00401470 : 00000000`00000000 ffffe000`06ff1a10 ffffe000`00fe3bd0 ffffe000`053fcd40 : nt!IopInvalidDeviceRequest+0x16
ffffd000`205c68c0 fffff800`00401157 : ffffe000`00fb9870 ffffe000`06ff1a10 ffffe000`00fe3bb0 fffff803`a7be525e : ACPI!ACPIDispatchForwardIrp+0x70
ffffd000`205c68f0 fffff800`0233016b : 00000000`00000007 ffffe000`06ff1a10 00000000`00000001 ffffe000`047e5190 : ACPI!ACPIDispatchIrp+0x137
ffffd000`205c6960 fffff800`0232ca32 : ffffe000`06ff1a10 ffffd000`205c6ab9 ffffe000`047e5040 ffffe000`00295810 : dxgkrnl!DpiFdoHandleSystemPower+0x173
ffffd000`205c6a00 fffff800`0270990b : 00000000`c0000001 ffffd000`205c6bd0 00000000`c0000010 ffffe000`06ff1a10 : dxgkrnl!DpiDispatchPower+0x8e
ffffd000`205c6b20 fffff803`a7997927 : 00000000`00000001 ffffe000`06ff1a10 ffffe000`06ff1ab8 00000000`00000001 : atikmpag+0x5b90b
ffffd000`205c6b50 fffff803`a790e2e4 : 80000000`00a80121 ffffe000`00376040 ffffe000`00376040 ffffe000`0026f900 : nt!PopIrpWorker+0x2df
ffffd000`205c6c00 fffff803`a79d52c6 : ffffd000`2088e180 ffffe000`00376040 ffffd000`2089a240 80000000`00a80121 : nt!PspSystemThreadStartup+0x58
ffffd000`205c6c60 00000000`00000000 : ffffd000`205c7000 ffffd000`205c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: dxgkrnl!DpiFdoHandleSystemPower+173
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52cbac50
BUCKET_ID_FUNC_OFFSET: 173
FAILURE_BUCKET_ID: 0x44_dxgkrnl!DpiFdoHandleSystemPower
BUCKET_ID: 0x44_dxgkrnl!DpiFdoHandleSystemPower
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x44_dxgkrnl!dpifdohandlesystempower
FAILURE_ID_HASH: {a6b9f88d-89b9-7f00-8ca8-f2d35dc482e0}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

Similar Messages

Event 1001, BugCheck + Event 41, Kernel-Power

hello,
I'm getting these random restarts on my laptop i baught just few months ago.
In the event viewer i found Event 41, Kernel-Power
followed by an Event 1001, BugCheck.
Please help.
System
Provider
[ Name]
Microsoft-Windows-Kernel-Power
[ Guid]
{331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID
41
Version
3
Level
1
Task
63
Opcode
0
Keywords
0x8000000000000002
TimeCreated
[ SystemTime]
2014-03-25T23:24:31.654884500Z
EventRecordID
21937
Correlation
Execution
[ ProcessID]
4
[ ThreadID]
8
Channel
System
Computer
Arseni_Graifer
Security
[ UserID]
S-1-5-18
EventData
BugcheckCode
159
BugcheckParameter1
0x3
BugcheckParameter2
0xffffe000059b3620
BugcheckParameter3
0xffffd00020c6b840
BugcheckParameter4
0xffffe00000c83010
SleepInProgress
0
PowerButtonTimestamp
0
BootAppStatus
0
System
Provider
[ Name]
Microsoft-Windows-WER-SystemErrorReporting
[ Guid]
{ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName]
BugCheck
EventID
1001
[ Qualifiers]
16384
Version
0
Level
2
Task
0
Opcode
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2014-03-25T23:24:56.000000000Z
EventRecordID
21926
Correlation
Execution
[ ProcessID]
0
[ ThreadID]
0
Channel
System
Computer
ARSENI_GRAIFER
Security
EventData
param1
0x0000009f (0x0000000000000003, 0xffffe000059b3620, 0xffffd00020c6b840, 0xffffe00000c83010)
param2
C:\WINDOWS\MEMORY.DMP
param3
032614-25828-01
My tech specs:
proccessor: Intel Core i7-3632QM CPU @ 2.20GHz 2.20GHz
NVIDIA Geforce GT 635M
LENOVO IDEAPAD Z500

Hi,
First, for this issue, please open device manager and check updates for power driver first.
Then, we consider that this issue is related to BSOD, please help to upload the minidump file here for our research:
Please upload them to a file sharing service like Onedrive or "Rapidshare" and put a link to them in your reply.
Link for how to upload below.
http://www.wikihow.com/Use-SkyDrive
To ensure minidumps are enabled, refer to the step “Configure the dump type” in following article:
How to read the small memory dump file that is created by Windows if a crash occurs
http://support.microsoft.com/kb/315263#method2
Kate Li
TechNet Community Support

Windows 8 Blue Screen Of Death (BSOD) BAD_POOL_CALLER

Hi,
I have been using windows 8 for the past week and have issues with BSOD appearing at random intervals and over the lat few days more frequently. After performing several rebuilds of the OS and carefully selecting Windows 8 supported applications i still
continue to receive this error.
I have reviewed the minidump files and the cause of the issues seems to be with ntoskrnl.exe
I have contacted microsoft support and sony vaio support and they advise e to rebuild every time or restore the system to a previous working version. Unfortunately this does not resolve the issue and i find myself back at the beginning again.
Could anyone advise on this issue and how to resolve?
Thanks
Matt

hi, i am using windows 8 on sony waio and i am getting this error. I guess i am getting this error when i am using dongle of idea net setter(huwaie) but as you suugested i have the link to my newest dmp file. please go through it and suggest what can be
done.
update the huawei driver:
* Bugcheck Analysis *
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880068210aa, The address that the exception occurred at
Arg3: fffff88005be5568, Exception Record Address
Arg4: fffff88005be4da0, Context Record Address
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
ewusbwwan+210aa
fffff880`068210aa 440fb608 movzx r9d,byte ptr [rax]
EXCEPTION_RECORD: fffff88005be5568 -- (.exr 0xfffff88005be5568)
ExceptionAddress: fffff880068210aa (ewusbwwan+0x00000000000210aa)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88005be4da0 -- (.cxr 0xfffff88005be4da0)
rax=5757575757575757 rbx=0000000000000500 rcx=26b791d663d80000
rdx=0000000000000000 rsi=0000000000000001 rdi=fffff980133c6bb5
rip=fffff880068210aa rsp=fffff88005be57a0 rbp=fffff980133c6bbd
r8=0000000000000000 r9=fffff88005be5400 r10=00000000ffffffff
r11=0000000000000000 r12=0000000000000480 r13=0000000000000001
r14=fffffa800858c000 r15=fffff980133c6b00
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
ewusbwwan+0x210aa:
fffff880`068210aa 440fb608 movzx r9d,byte ptr [rax] ds:002b:57575757`57575757=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80012d5a168
GetUlongFromAddress: unable to read from fffff80012d5a1f8
ffffffffffffffff
FOLLOWUP_IP:
ewusbwwan+210aa
fffff880`068210aa 440fb608 movzx r9d,byte ptr [rax]
BUGCHECK_STR: AV
LAST_CONTROL_TRANSFER: from fffff88005be0000 to fffff880068210aa
STACK_TEXT:
ewusbwwan
0x0
0x0
ewusbwwan
IMAGE_NAME: ewusbwwan.sys
Loaded symbol image file: ewusbwwan.sys
Image path: ewusbwwan.sys
Image name: ewusbwwan.sys
Timestamp: Thu Dec 23 05:18:25 2010
"A programmer is just a tool which converts caffeine into code"

Server reboot after Event 1001, BugCheck on virtual machine

Hi,
We have a virtual machine server 2008 R2 hoe does reboots after a bugcheck.
The notification is :
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000030, 0x0000000000000000, 0xfffff880009b8180, 0x0000000000000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061214-139312-01.
If i look at the console, then i see a BSOD screen
Can you help determine the cause of this failure ?
Best regards
Paul

Hi Paul,
It is recommended to run hardware diagnostics on the server to check if it is a hardware issue. The Windows built-in hardware diagnostic tools include CHKDSK and Windows Memory Diagnostic tool.
Chkdsk
http://technet.microsoft.com/en-us/library/bb491051.aspx
Windows Memory Diagnostics Tool in Windows Server 2008
http://www.itechtalk.com/thread2230.html
In additional, please refer to the article below to troubleshoot the issue:
Stop error message on a Windows Server 2008 R2-based computer that has the Hyper-V role installed and that uses one or more Intel CPUs that are code-named Nehalem: "0x00000101 - CLOCK_WATCHDOG_TIMEOUT"
http://support.microsoft.com/kb/975530
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows 8 Encore CS4 Blu-ray BSOD

I'm getting a BSOD in Encore CS4 when I try to build a blu-ray project. I have an HP laptop with an LG USB blu-ray burner. When I click build, even to build just an image, and then change from "DVD" to "Blu-Ray", there is a hang then a BSOD. My crashdump indicates that pxhlpa64.sys is the culprit.
This seems to be relevant, BUT the solution is to upgrade CS6 to new patch:
http://forums.adobe.com/message/4672190
I'm up-to-date in CS4, so that doesn't help. However, it sounds related and I'm hoping that my copy of CS4 Production Premium is still supported.
My version of pxhlpa64.sys is 3.0.78.0. WU can't find any updates as far as I can tell. I have not installed any drivers for my LG BE12LU38 Super Multi Blue, but it seems to be recognized and there are no updates via WU.
Here is my crashdump analysis:
0: kd> !analyze -v
* Bugcheck Analysis *
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000281, The DPC time count (in ticks).
Arg3: 0000000000000280, The DPC time allotment (in ticks).
Arg4: 0000000000000000
Debugging Details:
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
TAG_NOT_DEFINED_c000000f: FFFFF80393BA8FB0
LAST_CONTROL_TRANSFER: from fffff80393e48853 to fffff80393cee740
STACK_TEXT:
fffff803`93ba2128 fffff803`93e48853 : 00000000`00000133 00000000`00000000 00000000`00000281 00000000`00000280 : nt!KeBugCheckEx
fffff803`93ba2130 fffff803`93d19e51 : 0000034b`321b0754 fffff803`93f6a180 fffff803`93ba2290 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13c4c
fffff803`93ba21b0 fffff803`93c2ae94 : ffffffff`ffd1dc08 fffff803`93c54502 fffff880`012a0740 fffff880`0318e9c0 : nt!KeUpdateRunTime+0x51
fffff803`93ba21e0 fffff803`93ce7b2e : fffff803`93ba2290 00000000`279cdae1 fffff803`93c54580 fffff880`012a0740 : hal!HalpTimerClockInterrupt+0x50
fffff803`93ba2210 fffff803`93cde643 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x1ce
fffff803`93ba23a0 fffff803`93d1b025 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x23
fffff803`93ba23d0 fffff880`01298644 : 00000000`00000000 00000000`00000000 fffff6fd`4008aa48 fffff6fb`7ea00450 : nt!KeAcquireSpinLockRaiseToDpc+0x35
fffff803`93ba2400 fffff880`01298c1d : fffffa80`0d3855c0 fffff803`93ba2559 00000000`00000006 00000000`00000005 : PxHlpa64+0x2644
fffff803`93ba2470 fffff803`93d26406 : 00000000`00000001 fffff880`06da1c00 fffffa80`10ca75b0 ffff0083`95c9c410 : PxHlpa64+0x2c1d
fffff803`93ba24f0 fffff880`00a76c92 : fffffa80`11549b18 fffffa80`0e1f9e00 fffffa80`0d4bfbf0 00000000`00000000 : nt!IopfCompleteRequest+0x446
fffff803`93ba25d0 fffff880`00a29f30 : 00000000`00000000 fffffa80`0d494400 00000000`00000000 fffffa80`0d494400 : iaStorV!ScsiPortCompleteSrb+0x31a
fffff803`93ba2690 fffff880`00a29762 : fffff803`93ba2870 00000000`00000000 00000000`00000000 fffff880`0476de14 : iaStorV!DeviceToHostCompleteRequest+0x530
fffff803`93ba27b0 fffff880`00a76959 : fffff803`93f6cf00 fffff803`93ba2ab0 fffffa80`0d488630 00000000`00019ba2 : iaStorV!AHCIFinishIntProcessing+0xea
fffff803`93ba2980 fffff803`93d15fd8 : 00000028`00000002 00000345`2a93dd9e fffffa80`0d66e010 fffff803`93ba2a00 : iaStorV!SpRequestCompleteDpc+0x45
fffff803`93ba29b0 fffff803`93d155d0 : fffff880`00a7685c 00001f80`00ff00ff 00000000`00000000 00000000`00000002 : nt!KiExecuteAllDpcs+0x198
fffff803`93ba2af0 fffff803`93d1a4ba : fffff803`93f6a180 fffff803`93f6a180 00000000`00183de0 fffff803`93fc4880 : nt!KiRetireDpcList+0xd0
fffff803`93ba2c60 00000000`00000000 : fffff803`93ba3000 fffff803`93b9d000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
PxHlpa64+2644
fffff880`01298644 48b90800000080f7ffff mov rcx,0FFFFF78000000008h
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: PxHlpa64+2644
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: PxHlpa64
IMAGE_NAME: PxHlpa64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 475dd06d
FAILURE_BUCKET_ID: 0x133_DPC_PxHlpa64+2644
BUCKET_ID: 0x133_DPC_PxHlpa64+2644
Followup: MachineOwner

For CS4 you must update the Roxio component http://forums.adobe.com/thread/400484
More on Encore and Roxio http://forums.adobe.com/thread/528582 or direct to
http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/000070GN&PARAMS
Right click the program icon and select Run as Administrator, which is NOT the same thing as running the computer with the Administrator account, and which fixes several "odd" problems... To create a two layer DVD (or a BluRay?), you MUST have Encore set to use the Run as Administrator option
Run as Administrator http://forums.adobe.com/thread/969395
Also, for CS4, right click the program icon and see if Win8 has the same WinXP compatibility mode that is available in Win7
As far as support outside of this user to user group... I seriously doubt that Adobe will provide any help for a program that is 3 versions old, and which was written before Win8 was more than a Microsoft dream

NEED HELP w/ P35 Neo Combo and Windows XP Install Stop 0x24 error BSOD

First a little background, in case it's relevant:
I was running a 865PE Neo2 with 4 x 1gig Corsair DDR2 6400. Otherwise, same specs as below. Ran it for 2 years without a hitch, then got a virus that corrupted my profile and had trouble booting, logging on, and persistent virus messages. Long story short, I fried the BIOS and decided to replace the mobo and upgrade the memory, keeping the rest of the system intact. I previously had windows installed on both partitions of the HDD but changed the name of the directory for Windows on the C: drive so it would boot from the D: drive.
I have replaced 865PE with the P35 and changed the boot sequence to boot from CD. The BIOS loads fine, and I get to the windows setup screen ok. Whether I opt for Recovery Console, or a new install of Windows, I get a BSOD error message below.
STOP: 0x00000024 (0x001902FA, 0xf7906700, 0xf7906400, 0xf7103bef)
ntfs.sys Address F7103BEF base at F709f00, Datestamp 3d6de5c1
I tried with both new and old memory (in the right slots) and get the same message. I booting with no memory because I read in another post that the system should beep to indicate no memory and there was no beep.
BIOS recognizes the HDD, CPU and Memory so not sure what the problem is. Should I try taking the HDD out and reformatting it on another PC? (not easy since I don't have another desktop pc) Please help with some suggestions. Thank you.
System Specs
P35 Neo Combo Mobo
BIOS ver 1.3
E6400 Intel Dual Core
1 x 2 gig Crucial PC3 8500 DDR3 1066 mhz
nVidia 8800 GTS graphics
WD 250 gig Sata HD w/ 2 partitions of 125 ea.
Antec 500W SmartPower PSU
Installation disk is Windows XP Pro sp1

STOP: 0x00000024 indicates corrupt NTFS file system on the hard drive
Reformat would be the best thing to do. Download WD Data Lifeguard for your HDD, make the disk and run it.
http://support.wdc.com/product/download.asp?level1=6&lang=en
Quote from: FlyingSteve on 18-August-09, 10:29:00
I didn't know that the P35 Neo board ran ddr3...
That's where the 'Combo' part in the name comes into play, 2 DDR2 or 2 DDR3.
From MSI description of MB:
Main Memory
• Supports two unbuffered DIMM of 1.8 Volt DDR2 667/800 SDRAM. (Max: 4GB)
• Supports two unbuffered DIMM of 1.5 Volt DDR3 800/1066 SDRAM. (Max: 4GB)

T410 Windows 7 Professional 64-Bit Install BSOD

Hi, I am hoping someone can help me with resolving the issues I'm having trying to install Win7Pro 64-Bit
I recently upgraded the memory on my Lenovo T410 Thinkpad from 4GB to 8GB under Windows 7 32-Bit but as I later found out that there wasn't a reliable hack to allow me to use the extra RAM so I decided to move all my files off the machine and then do a clean install of Windows 7 32-Bit.
Unfortunately, I have had nothing but problems with the install, resulting in a BSOD every time. To give full details of what I have tried, see the list below:
Downloaded a version of Win7Pro 64-Bit and created a bootable USB using Microsoft's bootable USB creation software
Tried to boot and install the software
Downloaded another 2 different versions of Win7Pro 64-Bit for COA installs from the Microsoft website and created the bootable USB again with each of these and tried the installation again.
Used the Rufus software to create the bootabe USB drive (version rufus-1.4.9) and this gave the same results.
I also used the Novicorp WinToFlash 0.8.0009 software to create the bootable USB but this made no difference.
I have tried deleting the other partitions on the hard drive when given the option in the initial stages of the Win7 64-Bit setup but this made no difference.
I then created a UEFI bootable USB drive and tried this and this had the same issues
All in, I think I have tried the install about 10 times and have never managed to get anywhere with it.
Results
The furthest I have got with this is that the laptop boots from the USB and begins the install. It copies the Windows installation files over and then begins to expand the files. After successfully expending the files, it crashes with the BSOD with no real information on what can be causing the issue.
On the penultimate installation attempt, the message that came up was a BSOD message saying "Ntfs.sys - Address FFFFF88001C....... etc"
On the last attempt, I got the message "Windows installation encountered an unexpected error. Very that the installation sources are accessible, and restart the installation. Error code: 0x0000005"
What I have ruled out
The memory being an issue - this is because the machine seemed to work perfectly with the new memory modules in Win7 32-Bit and the issue only came up when running the 64-Bit versions
Win7 64-Bit ISOs being corrupt - because this would not occur on all ISO files but may occur on one... I have done a check on the MD5 of the downloaded files and they are all as they should be. An example of one is ed15956fe33c13642a6d2cb2c7aa9749 X17-59186.iso.
Research I have done
I have looked in this forum and other sites and just cannot find a definitive answer on why I'm having the issue. I had seen something pointing to it possbly being due to me not using the UEFI boot option but trying this did not help.
I researched what the "Error code: 0x0000005" meant and found a page on microsoft support asking me to check hardware as the issue could be related to a hard drive problem. I am currently running the hard drive diagnostic program and it's a slow process.
Can anyone help me with this? I'm really stuck!
Solved!
Go to Solution.

delprimero wrote:
What I have ruled out
The memory being an issue - this is because the machine seemed to work perfectly with the new memory modules in Win7 32-Bit and the issue only came up when running the 64-Bit versions
If I were you I would still run Memtest+ on that RAM, run it overnight and allow several passes.
Just to be 100% sure that the RAM isn't the culprit, (unless you already did that in which case my point would be moot)
My 2 cents only...
/L40SX/240/240X/2*340CSE/360PE/365XD/380D/380E/380XD/380Z/390/560E/560X/2*570/2*600/600E/750Cs/755C/760CD/760EL/760XD/770E/A20p/A22p
A31/i1600/G40/R50p/R61i/S30/SL510/2*T22/4*T4x/11*T6x/6*T4x0x/6*T5x0/3*W5x0/W700/3*X2x/4*X3x/3*X4x/5*X6x/3*X6xT/10*X2xx/2*X200T/4*X30x/Z60m/3*Z61x
Comunidad en Español English Community Deutsche Community Русскоязычное Сообщество

Windows Overlay Filter (wof.sys), file in Windows 8.1, is associated with BSOD in Windows 10 bld 9879

BSOD in Win 10 build 9879 is with bug check 0x1e. Wof.sys is a file that is in Win 8.1. HP g7-1310us (refurbished) laptop has been having BSOD's even when it had Win 7 installed. Checked RAM, hardware, and SATA disk but there is no specific lead to why BSOD's
happen routinely. Interestingly, there were no problems while this laptop was running Ubuntu 14. Any details on what Windows Overlay Filter driver named wof.sys does? Also, could this error be caused by faulty CPU? It has an Intel i3-2350M CPU @2.3Ghz, x64
based processor.
==================================================
Dump File         : 121114-22984-01.dmp
Crash Time        : 12/11/2014 5:23:05 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000008
Parameter 4       : 00000000`00000000
Caused By Driver : Wof.sys
Caused By Address : Wof.sys+1e40
File Description : Windows Overlay Filter
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.4.9879.0 (fbl_release.141103-1722)
Processor         : x64
Crash Address     : ntoskrnl.exe+161109
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\121114-22984-01.dmp
Processors Count : 4
Major Version     : 15
Minor Version     : 9879
Dump File Size    : 282,776
Dump File Time    : 12/11/2014 5:26:16 PM
==================================================
Gilda Sanchez

Here is the CPU data:
Intel(R) Processor Identification Utility
Version: 5.01.20140910
Time Stamp: 2014/12/11 19:28:20
Operating System: 6.2-9200-
Number of processors in system: 1
Current processor: #1
Active cores per processor: 2
Disabled cores per processor: 0
Processor Name: Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz
Type: 0
Family: 6
Model: 2A
Stepping: 7
Revision: 29
Maximum CPUID Level: D
L1 Instruction Cache: 2 x 32 KB
L1 Data Cache: 2 x 32 KB
L2 Cache: 2 x 256 KB
L3 Cache: 3 MB
Packaging: µPGA/BGA
Enhanced Intel SpeedStep(R) Technology: Yes
MMX(TM): Yes
Intel(R) SSE: Yes
Intel(R) SSE2: Yes
Intel(R) SSE3: Yes
Intel(R) SSE4: Yes
Intel(R) AES-NI: No
Intel(R) AVX: Yes
Enhanced Halt State: Yes
Execute Disable Bit: Yes
Gilda Sanchez

Windows 2008 R2 DC Recovery Test BSOD on boot

Hello everyone.
first off i have a perfectly healthy production domain with 2 domain controllers and replication occurring between them, the only issue is there on the same site.
i am in a test environment testing a scenario where both DC's are broken and i need to build a new one on new hardware, and all i have is a system state backup.
following the instructions,
Build a new machine closely matching the original machine hardware, (RAM and HDD size)
install 2008r2. allocate static IP address and reboot in DRM
add windows feature, windows server backup
select restore in WSB and select the system state.
DC then restores the data and askes to be rebooted.
after the reboot i get a BSOD on boot and its seems to occur when to loading CLASSPNP.SYS file any suggestions on how to resolve this?
also is there a way of building a DC, using DCPRMO then restoring the data to another location and then importing it into active directory.
basically i need a plan that can be used in a total disaster scenario with a off site backup of the system state / backup as my only options.
cheers
Gordon

Have you seen? Also make sure to install the exactly same operating system and service pack level
http://support.microsoft.com/kb/249694/
Enfo Zipper
Christoffer Andersson – Principal Advisor
http://blogs.chrisse.se - Directory Services Blog

Windows 7 and BootCamp 3.0: BSOD every startup

Ok, I have a Mac Pro early 2008, I have Windows 7 RTM (from MSDNAA) and after I install BootCamp 3.0, every time I boot into Windows it gives me a BSOD, a few seconds after it reaches the desktop (reproducible) . Anyone have this experience? I know this is very early in the stage.
BootCamp 2.1 seems to do just fine.

Actually. At first, I installed Windows 7 with BootCamp 2.1, everything worked out well.
Then I got the Snow Leopard disc, it apparently had BootCamp 3.0, I installed it (I didn't uninstall BootCamp 2.1), restarted, it gave me the BSOD, I rebooted into Windows 7 a few more times, same thing.
I formatted Windows 7 drive and reinstalled it from scratch, this time, on first boot, I install BootCamp 3.0 (and only that), restarted into Windows 7 again, and it gave me the BSOD. I rebooted several more times, and it was reproducible.
Now I'm reinstalling Windows 7 again, but this time keeping BootCamp 2.1.
All the drivers worked, even the WiFi, BlueTooth, Sound, etc. The only thing that did not work was the video card, but I found the drivers directly from Nvidia's website instead.

T400 Windows XP Random Freezes / Lockups (no BSOD) - Intel Wireless issue?

Hi,
I installed Windows XP Pro SP3 on my new Thinkpad T400 purchased a few days ago. I installed all the latest drivers and thinkvantage software from the drivers matrix.
For two days now the system randomly freezes. The screen freezes, i cannot move the mouse or keyboard. Some FN buttons like the Thinklight still work, the rest does not and it ultimately requires a force power off by holding the power button pressed.
Interestingly enough the Wireless symbol still blinks even when the laptop is frozen. When i turn off the wireless switch, the bluetooth icon will turn off, yet the wireless KEEPS blinking (normally both turn off when the wireless switch is turned off).
I originally had the lenovo intel wireless 5100 drivers, now tried the intel.com drivers, no avail, same issue. The system also freezes when just sitting idle. I have not yet tried if the freezes occur with wireless turned off, will try later...
Kind of annoying as i had various BSODs due to the lenovo intel Matrix Storage driver (the original intel one made it go away), now this problem...is XP just not really supported by this machine?
Thinkpad T400 (Windows 7 Ultimate x64)

Hi,
I installed Windows XP Pro SP3 on my new Thinkpad T400 purchased a few days ago. I installed all the latest drivers and thinkvantage software from the drivers matrix.
For two days now the system randomly freezes. The screen freezes, i cannot move the mouse or keyboard. Some FN buttons like the Thinklight still work, the rest does not and it ultimately requires a force power off by holding the power button pressed.
Interestingly enough the Wireless symbol still blinks even when the laptop is frozen. When i turn off the wireless switch, the bluetooth icon will turn off, yet the wireless KEEPS blinking (normally both turn off when the wireless switch is turned off).
I originally had the lenovo intel wireless 5100 drivers, now tried the intel.com drivers, no avail, same issue. The system also freezes when just sitting idle. I have not yet tried if the freezes occur with wireless turned off, will try later...
Kind of annoying as i had various BSODs due to the lenovo intel Matrix Storage driver (the original intel one made it go away), now this problem...is XP just not really supported by this machine?
Thinkpad T400 (Windows 7 Ultimate x64)

Windows 7 Blue Screen Of Death (BSOD)

Hi everybody,
a week ago my laptop showed for the first time a BSOD. I'm 90% sure that it is a hardware issue. Sometimes when i lift/move it or even press with my hands in certain areas it appears the following symptoms:
the screen will immediately freeze or
it will reboot or
a BSOD will appear
I have checked other topics and i found that these files can be useful:
https://www.dropbox.com/s/dnh40wkdvhv2efm/Minidump.rar
Additionally, I have noticed that the BSOD error code is not the same everytime. The last time was this one i think:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1032
Additional information about the problem:
BCCode: 50
BCP1: FFFFD46000105629
BCP2: 0000000000000008
BCP3: FFFFD46000105629
BCP4: 0000000000000007
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
I would really appreciate any help. Thank you

These crashes were related to memory corruption (probably caused by a driver).
Please run this test to find which driver is causing the problem.
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
know what it is you probably are not overclocking.
Driver verifier (for complete directions see our wiki here)
Co-Authored by JMH3143
Wanikiya and Dyami--Team Zigzag

DHCP client fails to get an valid IP address from DHCP server. windows 8.1

I have a win 8.1 Pro 64 bit pc in my office .I'm trying to connect it to my wireless cisco router with either wireless or hardwired connection but I get an error in the event viewer with discription DHCP error 1007. and Ip address showing
169.254.93.17 but our dhcp range is 192.168.1.x
Log Name: Microsoft-Windows-Dhcp-
Source: Microsoft-Windows-Dhcp-Client
Date: 23/Jun/2014 12:03:21 PM
Event ID: 1001
Task Category: Address Configuration State Event
Level: Error
Keywords: (1)
User: LOCAL SERVICE
Computer: sanddeplap.vts.com
Description:
Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0xF4B7E22D8721. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its
own from the network address (DHCP) server.
Event Xml:
<Event xmlns="http://schemas.">
<System>
<Provider Name="Microsoft-Windows-Dhcp-
<EventID>1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>75</Opcode>
<Keywords>0x4000000000000001</
<TimeCreated SystemTime="2014-06-23T08:03:
<EventRecordID>363</
<Correlation />
<Execution ProcessID="988" ThreadID="7932" />
<Channel>Microsoft-Windows-
<Computer>sanddeplap.vts.com</
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="HWLength">6</Data>
<Data Name="HWAddress">F4B7E22D8721<
<Data Name="StatusCode">121</Data>
</EventData>
</Event>
I tried to track issue with microsoft network monitor I'm attaching the capture file also please help me to sort out this issue
capture report https://onedrive.live.com/redir?resid=AFE3D0245A92F6F8%21183

The issue is that your machine is not being assigned an IP address / was unable to reach the DHCP server to receive one. The 169.254.x.x IP your machine is showing isn't assigned from DHCP, it's assigned by the local machine and is referred to as an APIPA
address.
So something is preventing your machine from reaching your DHCP server, which could one of a number of things. In the first instance I'd suggest having a look at
http://epan36.blogspot.co.uk/2012/09/eventid-1001-dhcp-your-computer-was-not.html which lists several of things that could cause this error and things you can try in order to resolve it.
If none of those work, can you confirm whether you have any other machines connecting via the same method on the network, which might indicate whether this is an issue at the machine end or somewhere between the machine and DHCP server?

BSOD event 1001, bug check

<can someone help me what is the cause of it? it just happened a while ago and i got feared it will damage my pc..
n
System
Provider
[ Name]
Microsoft-Windows-WER-SystemErrorReporting
[ Guid]
{ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName]
BugCheck
EventID
1001
[ Qualifiers]
16384
Version
0
Level
2
Task
0
Opcode
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2014-04-20T23:40:42.000000000Z
EventRecordID
10197
Correlation
Execution
[ ProcessID]
0
[ ThreadID]
0
Channel
System
Computer
rustyevangelista
Security
EventData
param1
0x0000007e (0xffffffffc0000005, 0x0000000000000000, 0xfffff880031fbb08, 0xfffff880031fb370)
param2
C:\Windows\MEMORY.DMP
param3
042114-53539-01

Hi,
In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
If you don't know where .DMP files are located, here's how to get to them:
1. Navigate to the %systemroot%\Minidump folder.
2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Prefered sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers.
4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
If you are going to use Onedrive but don't know how to upload to it, please visit the following:
Upload photos and files to Onedrive.
Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete .DMP files upon use.
If your computer is not generating .DMP files, please do the following:
1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all
drives'.
3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system
log'.
Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
4. Double check that the WERS is ENABLED:
Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
If you cannot get into normal mode to do any of this, please do this via Safe Mode.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama

Windows 8.1 BSOD please help Minidump file attached

Windows 8.1 BSOD please help Minidump file and dxdiag info file link is below,
This BSOD frequency is about once every 1 hour to 4 hours,
Memtest passed with one pass on the one chip of 4GB
Brand new 8.1 install
https://drive.google.com/file/d/0B39S6eNyRvOHRnZHRG1Jd1lwT2M/view?usp=sharing
https://docs.google.com/document/d/1XueM-ov7wjfePJh45Pp3fg1QSSzFBqMuO1tfr9GZm8k/edit?usp=sharing

This is a crash related to some type of hardware failure. Please refer to the Wiki link below, for some troubleshooting tips.
BugCheck Code 124 Co-Authored by ZigZag3143& JMH3143
http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/bugcheck-code-124/98c998d2-447a-40ce-ae1f-8211e355f14d
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
Machine Name:
Kernel base = 0xfffff800`c0e7b000 PsLoadedModuleList = 0xfffff800`c113f990
Debug session time: Tue Mar 3 23:19:34.178 2015 (UTC - 5:00)
System Uptime: 0 days 0:00:04.947
Loading Kernel Symbols
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, ffffe000016f88f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
1: kd> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe000016f88f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
ffffd000`2087f6c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x81
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
1: kd> !errrec ffffe000016f88f8
===============================================================================
Common Platform Error Record @ ffffe000016f88f8
Record Id : 01d0563268a81312
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 3/4/2015 4:19:34
Flags : 0x00000002 PreviousError
===============================================================================
Section 0 : Processor Generic
Descriptor @ ffffe000016f8978
Section @ ffffe000016f8a50
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : BUS error
Operation : Generic
Flags : 0x00
Level : 3
CPU Version : 0x0000000000100f42
Processor ID : 0x0000000000000000
===============================================================================
Section 1 : x86/x64 Processor Specific
Descriptor @ ffffe000016f89c0
Section @ ffffe000016f8b10
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000000
CPU Id : 42 0f 10 00 00 08 02 00 - 09 20 80 00 ff fb 8b 17
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0 @ ffffe000016f8b10
===============================================================================
Section 2 : x86/x64 MCA
Descriptor @ ffffe000016f8a08
Section @ ffffe000016f8b90
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
Status : 0xba00001000020c0f

Windows 8 EventID 1001 BugCheck 0xa1 BSOD

Similar Messages

Maybe you are looking for