Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD while at windows startup


01 Feb 2012   #1

Windows 7 64bit Ultimate
 
 
BSOD while at windows startup

had strange BSOD at windows start-up. doesn't seem to happen every time. I'm very curious about the reason to this, as this is my only computer and I use it all day long for school and work.

minidump file attached.

Any help will be very much appreciated!

here's some system spec's:

OS Name Microsoft Windows 7 Ultimate
Version 6.1.7600 Build 7600
System Manufacturer Gateway
System Model T-6836
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz, 2201 Mhz, 2
Core(s), 2 Logical Processor(s)
BIOS Version/Date Gateway 89.24, 22/05/2008
SMBIOS Version 2.4
Hardware Abstraction Layer Version = "6.1.7600.16385"
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.99 GB
Available Physical Memory 2.13 GB
Total Virtual Memory 7.98 GB
Available Virtual Memory 6.15 GB


My System SpecsSystem Spec
.

01 Feb 2012   #2

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Please post the entire set of files requested below, these are necessary for us to help you.
Blue Screen of Death (BSOD) Posting Instructions

Can you post your specs.
Enter them in the 'My System Specs' dropbox at the lower left corner of any of your posts.
Use these links to find your system specs.
System Info - See Your System Specs
Or
Speccy Free System information Utility

Enter this information in the 'My System Specs' dropbox in the lower left corner of any of you posts.
Be sure to add details on your RAM.


This crash is STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Usual causes: Device driver, Memory
The driver blamed is WUDFRd - Windows Driver Foundation - User-mode Driver Framework Reflector. This is a Windows driver and likely the result of the crash and not the cause.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff88008a87e10, Virtual address for the attempted write.
Arg2: 8000000136a2c121, PTE contents.
Arg3: fffff88002fd1cc0, (reserved)
Arg4: 000000000000000b, (reserved)

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'secdrv' and 'atksgt.sys' overlap

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002fd1cc0 -- (.trap 0xfffff88002fd1cc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88008a87e10 rbx=0000000000000000 rcx=fffffa8005fb4170
rdx=fffffa8006cbc150 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008a7953e rsp=fffff88002fd1e50 rbp=fffff88008a8f110
 r8=fffff88008a87e10  r9=0000000000000001 r10=fffff80002e4c888
r11=fffff88002fd1e68 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         ov up ei ng nz na po nc
WudfPf!LpcControlDevice::DeviceIoControlInternal+0x1a:
fffff880`08a7953e 82              ???
Resetting default scope

LOCK_ADDRESS:  fffff80002ec1420 -- (!locks fffff80002ec1420)

Resource @ nt!PiEngineLock (0xfffff80002ec1420)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff80002ec1420
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

MISALIGNED_IP: 
WudfPf!LpcControlDevice::DeviceIoControlInternal+1a
fffff880`08a7953e 82              ???

LAST_CONTROL_TRANSFER:  from fffff80002d3d9c2 to fffff80002cbd5c0

STACK_TEXT:  
fffff880`02fd1b58 fffff800`02d3d9c2 : 00000000`000000be fffff880`08a87e10 80000001`36a2c121 fffff880`02fd1cc0 : nt!KeBugCheckEx
fffff880`02fd1b60 fffff800`02cbb6ae : 00000000`00000001 00000000`0000000f fffff880`02fd1f00 fffff800`02cf5dc2 : nt! ?? ::FNODOBFM::`string'+0x4223e
fffff880`02fd1cc0 fffff880`08a7953e : 00000000`65444d55 fffffa80`06ff63e0 fffffa80`05fb4170 fffff880`08a77e99 : nt!KiPageFault+0x16e
fffff880`02fd1e50 fffffa80`06ff63e0 : fffffa80`06cbc150 fffff880`08a76cc4 00000000`00000000 fffff880`08a8f110 : WudfPf!LpcControlDevice::DeviceIoControlInternal+0x1a
fffff880`02fd1ea0 fffffa80`06cbc150 : fffff880`08a76cc4 00000000`00000000 fffff880`08a8f110 fffffa80`0651d360 : 0xfffffa80`06ff63e0
fffff880`02fd1ea8 fffff880`08a76cc4 : 00000000`00000000 fffff880`08a8f110 fffffa80`0651d360 fffffa80`0651d360 : 0xfffffa80`06cbc150
fffff880`02fd1eb0 fffff880`05498c4a : 00000000`00000000 00000000`c000009a 00000000`00000001 fffff880`054961a7 : WudfPf!LpcDriver::s_Dispatch+0xc0
fffff880`02fd1ef0 fffff880`0549728f : fffffa80`0651d360 fffffa80`06ff6270 00000000`00000000 fffffa80`06ff6930 : WUDFRd!RdDriver::InitializeLpcAndConnect+0xf2
fffff880`02fd1fc0 fffff880`054c24c1 : 00000000`00000244 00000000`00000000 fffffa80`00000006 00000000`00000000 : WUDFRd!RdDriver::RdDriver+0x3fb
fffff880`02fd21d0 fffff800`030a5eb7 : fffffa80`00000006 fffffa80`06ff6930 fffffa80`05fa4500 00000000`000007ff : WUDFRd!DriverEntry+0x4b9
fffff880`02fd2240 fffff800`03139200 : 00000000`00000001 00000000`00000000 fffff880`02fd2828 ffffffff`800010e8 : nt!IopLoadDriver+0xa07
fffff880`02fd2510 fffff800`02f73f7c : fffff8a0`0384be30 00000000`00000000 fffff8a0`0384be78 fffff8a0`0384be30 : nt!PipCallDriverAddDeviceQueryRoutine+0x390
fffff880`02fd2610 fffff800`02f74617 : 00000000`00000000 fffff880`02fd2860 00000000`00000001 00000000`000007ff : nt!RtlpCallQueryRegistryRoutine+0x31c
fffff880`02fd2680 fffff800`030a916c : 00000000`00000000 fffffa80`06ff5ac0 00000000`20206f49 fffff880`02fd2828 : nt!RtlQueryRegistryValues+0x417
fffff880`02fd27a0 fffff800`030aa902 : fffffa80`06ff5ac0 fffffa80`06ff5ac0 00000000`00000000 fffff8a0`0000004c : nt!PipCallDriverAddDevice+0x45c
fffff880`02fd2950 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x2b2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WudfPf!LpcControlDevice::DeviceIoControlInternal+1a
fffff880`08a7953e 82              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  WudfPf!LpcControlDevice::DeviceIoControlInternal+1a

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_WudfPf.sys

BUCKET_ID:  X64_IP_MISALIGNED_WudfPf.sys

Followup: MachineOwner
---------
This is indicating a hardware issue.
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
My System SpecsSystem Spec
01 Feb 2012   #3

Windows 7 64bit Ultimate
 
 

sorry, I guess I'm kinda new at this... temps are checked. they go between 54C to 75C.

I added the files in the zip and here are some snips from cpu-z:

Attachment 196193

Attachment 196194

Attachment 196195

Attachment 196196
My System SpecsSystem Spec
.


02 Feb 2012   #4

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Good information.

First, your CPU temps are too high.
Have you cleaned out your laptop?
You need to open the back cover and blow the dust out. Get a can of dry compressed air from a computer shop.

The crash you had can be caused by your system/CPU overheating.

Let us know if you have any questions.
My System SpecsSystem Spec
02 Feb 2012   #5

Windows 7 64bit Ultimate
 
 
Will do

thank you guys (or girls) so much. you are great!
My System SpecsSystem Spec
02 Feb 2012   #6

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

You have crash dumps from Aug 2010, total of 32.

The crashes from most recent going back.

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver

STOP 0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED
This bug check appears very infrequently.

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bug check.

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bug check.

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000890, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001401435, address which referenced memory

Debugging Details:
------------------
MODULE_NAME: NETIO
IMAGE_NAME:  NETIO.SYS

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff88002f1b1b0
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff880014c0b21

Debugging Details:
------------------
MODULE_NAME: ndis
IMAGE_NAME:  ndis.sys

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002db9de1, Address of the instruction which caused the bugcheck
Arg3: fffff88002bbfac0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  audiodg.exe
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------
MODULE_NAME: NETwLv64
IMAGE_NAME:  NETwLv64.sys

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ff7477, address which referenced memory

Debugging Details:
------------------
MODULE_NAME: netw5v64

IMAGE_NAME:  netw5v64.sys
Run memtest86+ for a minimum on 7 full passes with both RAM cards installed, best to run overnight.
Stop the test if you get any errors.
RAM - Test with Memtest86+

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

Go to the Gateway support site and update all your drivers.

Old or problem drivers.
Code:
GEARAspiWDM.sys Mon May 18 20:17:04 2009 - CD-ROM Class Filter Driver by Gear Software Also comes with iTunes
Uninstall iTunes.
iTunes is known to cause crashes with some Windows 7 systems.

Code:
avgmfx64.sys Thu Jul 02 04:38:25 2009 - AVG Mini-Filter Resident Anti-Virus Shield
AVG is known to cause crashes on Windows 7 systems.
Uninstall AVG for testing purposes.
Install MSE for now: Microsoft Security Essentials*- Free Antivirus for Windows

Code:
VSTAZL6  VSTAZL6.SYS  Thu Oct 16 08:53:42 2008 - Conexant SoftK56 Modem Driver
Update this driver at your Gateway support site.
My System SpecsSystem Spec
03 Feb 2012   #7

Windows 7 64bit Ultimate
 
 

thanks Dave. I just had another BSOD. This time error message was about some drive trying to corrupt the system, so I guess it's pretty bad... Would you think it is a good solution to format the drive and make a fresh OS install?

I attached the BSOD's minidump..
My System SpecsSystem Spec
04 Feb 2012   #8

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Run and attach the full files at this link.
Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.

Have you cleaned out your laptop case?

Did you run memtest86+?

Did you update your drivers from the Gateway website?

Did you uninstall iTunes and AVG?
Install MSE: Microsoft Security Essentials*- Free Antivirus for Windows ?

Please confirm what steps you have taken and the steps you have not done yet.


The latest crash is STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Usual causes: Device driver, Memory
This minidump is blaming WUDFRd.sys - Windows Driver Foundation - User-mode Driver Framework Reflector, a Windows driver and probably the result of the crash and not the cause.
Hardware is named as the cause.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff88008a87e10, Virtual address for the attempted write.
Arg2: 8000000136a2c121, PTE contents.
Arg3: fffff88002fd1cc0, (reserved)
Arg4: 000000000000000b, (reserved)

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'secdrv' and 'atksgt.sys' overlap

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002fd1cc0 -- (.trap 0xfffff88002fd1cc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88008a87e10 rbx=0000000000000000 rcx=fffffa8005fb4170
rdx=fffffa8006cbc150 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008a7953e rsp=fffff88002fd1e50 rbp=fffff88008a8f110
 r8=fffff88008a87e10  r9=0000000000000001 r10=fffff80002e4c888
r11=fffff88002fd1e68 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         ov up ei ng nz na po nc
WudfPf!LpcControlDevice::DeviceIoControlInternal+0x1a:
fffff880`08a7953e 82              ???
Resetting default scope

LOCK_ADDRESS:  fffff80002ec1420 -- (!locks fffff80002ec1420)

Resource @ nt!PiEngineLock (0xfffff80002ec1420)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff80002ec1420
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

MISALIGNED_IP: 
WudfPf!LpcControlDevice::DeviceIoControlInternal+1a
fffff880`08a7953e 82              ???

LAST_CONTROL_TRANSFER:  from fffff80002d3d9c2 to fffff80002cbd5c0

STACK_TEXT:  
fffff880`02fd1b58 fffff800`02d3d9c2 : 00000000`000000be fffff880`08a87e10 80000001`36a2c121 fffff880`02fd1cc0 : nt!KeBugCheckEx
fffff880`02fd1b60 fffff800`02cbb6ae : 00000000`00000001 00000000`0000000f fffff880`02fd1f00 fffff800`02cf5dc2 : nt! ?? ::FNODOBFM::`string'+0x4223e
fffff880`02fd1cc0 fffff880`08a7953e : 00000000`65444d55 fffffa80`06ff63e0 fffffa80`05fb4170 fffff880`08a77e99 : nt!KiPageFault+0x16e
fffff880`02fd1e50 fffffa80`06ff63e0 : fffffa80`06cbc150 fffff880`08a76cc4 00000000`00000000 fffff880`08a8f110 : WudfPf!LpcControlDevice::DeviceIoControlInternal+0x1a
fffff880`02fd1ea0 fffffa80`06cbc150 : fffff880`08a76cc4 00000000`00000000 fffff880`08a8f110 fffffa80`0651d360 : 0xfffffa80`06ff63e0
fffff880`02fd1ea8 fffff880`08a76cc4 : 00000000`00000000 fffff880`08a8f110 fffffa80`0651d360 fffffa80`0651d360 : 0xfffffa80`06cbc150
fffff880`02fd1eb0 fffff880`05498c4a : 00000000`00000000 00000000`c000009a 00000000`00000001 fffff880`054961a7 : WudfPf!LpcDriver::s_Dispatch+0xc0
fffff880`02fd1ef0 fffff880`0549728f : fffffa80`0651d360 fffffa80`06ff6270 00000000`00000000 fffffa80`06ff6930 : WUDFRd!RdDriver::InitializeLpcAndConnect+0xf2
fffff880`02fd1fc0 fffff880`054c24c1 : 00000000`00000244 00000000`00000000 fffffa80`00000006 00000000`00000000 : WUDFRd!RdDriver::RdDriver+0x3fb
fffff880`02fd21d0 fffff800`030a5eb7 : fffffa80`00000006 fffffa80`06ff6930 fffffa80`05fa4500 00000000`000007ff : WUDFRd!DriverEntry+0x4b9
fffff880`02fd2240 fffff800`03139200 : 00000000`00000001 00000000`00000000 fffff880`02fd2828 ffffffff`800010e8 : nt!IopLoadDriver+0xa07
fffff880`02fd2510 fffff800`02f73f7c : fffff8a0`0384be30 00000000`00000000 fffff8a0`0384be78 fffff8a0`0384be30 : nt!PipCallDriverAddDeviceQueryRoutine+0x390
fffff880`02fd2610 fffff800`02f74617 : 00000000`00000000 fffff880`02fd2860 00000000`00000001 00000000`000007ff : nt!RtlpCallQueryRegistryRoutine+0x31c
fffff880`02fd2680 fffff800`030a916c : 00000000`00000000 fffffa80`06ff5ac0 00000000`20206f49 fffff880`02fd2828 : nt!RtlQueryRegistryValues+0x417
fffff880`02fd27a0 fffff800`030aa902 : fffffa80`06ff5ac0 fffffa80`06ff5ac0 00000000`00000000 fffff8a0`0000004c : nt!PipCallDriverAddDevice+0x45c
fffff880`02fd2950 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x2b2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WudfPf!LpcControlDevice::DeviceIoControlInternal+1a
fffff880`08a7953e 82              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  WudfPf!LpcControlDevice::DeviceIoControlInternal+1a

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_WudfPf.sys

BUCKET_ID:  X64_IP_MISALIGNED_WudfPf.sys

Followup: MachineOwner
---------
First run this diagnostic program on your HDD.
D/L and run Western Digital Lifeguard – Quick Test and Extended Test.

Let us know the results and status of previous suggestions, we'll go from there.
My System SpecsSystem Spec
Reply

 BSOD while at windows startup




Thread Tools



Similar help and support threads for2: BSOD while at windows startup
Thread Forum
Solved BSOD on windows startup BSOD Help and Support
BSOD on Windows 7 startup - not HDD? BSOD Help and Support
BSOD on startup , error 0x000000f4 . startup takes half an hour BSOD Help and Support
BSOD at windows startup BSOD Help and Support
BSOD Windows 7 on Startup. BSOD Help and Support
BSOD on Windows Startup BSOD Help and Support
BSOD with windows startup BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 10:02 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33