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 when booting

23 Jul 2010   #1

win xp
BSOD when booting

I run Win 7 and I recently updated my bios from 1.3 to 1.8 on my Toshiba Satellite A305, there was a screen issue where it just turns off or freezes.. fixed that but now I get BSOD when i boot normally.

Compressed 6 of the minidump files and attached the folder.

My System SpecsSystem Spec
23 Jul 2010   #2

Win 8 Release candidate 8400

Quote   Quote: Originally Posted by NauzD View Post
I run Win 7 and I recently updated my bios from 1.3 to 1.8 on my Toshiba Satellite A305, there was a screen issue where it just turns off or freezes.. fixed that but now I get BSOD when i boot normally.

Compressed 6 of the minidump files and attached the folder.
These all seem to be caused by your HD. Disk hardware failure. I would run a checkdisk to start.

Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\K\Desktop\072310-19141-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*;srv*e:\symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e1d000 PsLoadedModuleList = 0xfffff800`0305ae50
Debug session time: Fri Jul 23 21:58:26.481 2010 (GMT-4)
System Uptime: 0 days 0:02:00.494
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000006, fffff80002f16823, fffff880047d5698, fffff880047d4f00}

Probably caused by : hardware_disk

Followup: MachineOwner

0: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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
Arg1: ffffffffc0000006, The exception code that was not handled
Arg2: fffff80002f16823, The address that the exception occurred at
Arg3: fffff880047d5698, Exception Record Address
Arg4: fffff880047d4f00, Context Record Address

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

fffff800`02f16823 0fb702          movzx   eax,word ptr [rdx]

EXCEPTION_RECORD:  fffff880047d5698 -- (.exr 0xfffff880047d5698)
ExceptionAddress: fffff80002f16823 (nt!XpressDecodeCreate+0x0000000000000073)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000468000
   Parameter[2]: 00000000c0000185
Inpage operation failed at 0000000000468000, due to I/O error 00000000c0000185

CONTEXT:  fffff880047d4f00 -- (.cxr 0xfffff880047d4f00)
rax=0000000000000004 rbx=0000000000467ff3 rcx=0000000000000004
rdx=0000000000468000 rsi=fffff8a0036136d0 rdi=0000000000000001
rip=fffff80002f16823 rsp=fffff880047d58d8 rbp=0000000000010000
 r8=0000000000220c50  r9=fffff8a0036136d0 r10=00000000db000000
r11=000000000021f34e r12=00000000001e9e81 r13=fffff8a0035290cc
r14=000000000000001c r15=0000000000464676
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
fffff800`02f16823 0fb702          movzx   eax,word ptr [rdx] ds:002b:00000000`00468000=????
Resetting default scope





ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000468000

EXCEPTION_PARAMETER3:  00000000c0000185

IO_ERROR: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.


EXCEPTION_STR:  0xc0000006_c0000185

00000000`00468000 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

IMAGE_NAME:  hardware_disk



FAILURE_BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

Followup: MachineOwner

Old drivers needing update
RimSerial_AMD64.sys        fffff880`04e1a000    fffff880`04e21680    0x00007680    0x45a3c7c3    1/9/2007 12:50:11                        
PxHlpa64.sys        fffff880`0114e000    fffff880`01159380    0x0000b380    0x45c3ac06    2/2/2007 17:24:22                        
rimspx64.sys        fffff880`04dce000    fffff880`04de5000    0x00017000    0x45e3d96d    2/27/2007 03:10:37                        
rimmpx64.sys        fffff880`04dba000    fffff880`04dce000    0x00014000    0x45fdfeee    3/18/2007 23:09:34                        
rixdpx64.sys        fffff880`04e84000    fffff880`04edb000    0x00057000    0x4607a4f7    3/26/2007 06:48:23                        
agrsm64.sys        fffff880`084cc000    fffff880`085ee000    0x00122000    0x49184ccf    11/10/2008 11:01:35                        
Rt64win7.sys        fffff880`03a49000    fffff880`03a7b000    0x00032000    0x49a65b0d    2/26/2009 05:04:13                        
netw5v64.sys        fffff880`04821000    fffff880`04d5c000    0x0053b000    0x49cbab84    3/26/2009 12:21:24                        
spldr.sys        fffff880`015ef000    fffff880`015f7000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`04f17000    fffff880`04f24000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`00e85000    fffff880`00e90000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59
My System SpecsSystem Spec
23 Jul 2010   #3

Windows 10 Pro x64

Looks like you double-posted:

Might want to combine these.
My System SpecsSystem Spec


 BSOD when booting

Thread Tools

Similar help and support threads
Thread Forum
BSOD when booting up
Hi, a friend of mine recently lend another friend's laptop. When the unit came back, my friend said it won't boot normally. The laptop flashes BSOD for a split second (or a quarter of second. The thing is it doesn't let me see the error code) then restarts. I tried booting into safe mode. It loads...
BSOD Help and Support
BSOD soon after booting.
General Discussion
BSOD after booting into 7
Working on a Dell Inspiron N7110 running Windows 7 Home Premium SP1. The computer will boot into Windows fine, but after about 30 seconds to a minute it will blue screen and reboot. I have re-seated the memory and run memtest, as well as Dell's built in diagnostics and everything passed. Safe mode...
BSOD Help and Support
Issue booting Win 7, booting directly into XP & no boot manager
Hi, I just got a ASUS G75V series and updated it to windows 7 professional with Intel core i7. I was able to work with it and everything was fine until I had to install XP because some softwares are not compatible with Win 7 x64. I have Win 7 on drive C: and windows xp on drive E: which in...
Installation & Setup
BSOD when booting from USB HD
Unfortunately my computer's hard disk has failed on me. Fortunately I did create an image (using Acronis TrueImage Home) shortly before disk failure. The OS is Windows 7 (32-bit), and the image includes the system partition, Windows 7's system reserved partition and the master boot record. Since...
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 17:15.
Twitter Facebook Google+