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 0x7E

18 May 2011   #1
misterxsai

windows 7 ultimate x64
 
 
BSOD 0x7E

need some help regarding my system. running on windows 7. it has been working fine for a few months then I started getting BSOD 0X0A and now the last BSOD that I got was 0x7E. It's pretty much random since there can be a time that I can use my PC for a really long time and not get BSOD and sometimes get it in just as little as 10 minute use.

I just got this BSOD a few minutes ago and then when the system restarted there was no display. So I restarted the computer and NO POST, no beeps as well. keyboard light does not light up, no display either.

I am now just using my laptop.

Appreciate the help!


My System SpecsSystem Spec
.
18 May 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by misterxsai View Post
need some help regarding my system. running on windows 7. it has been working fine for a few months then I started getting BSOD 0X0A and now the last BSOD that I got was 0x7E. It's pretty much random since there can be a time that I can use my PC for a really long time and not get BSOD and sometimes get it in just as little as 10 minute use.

I just got this BSOD a few minutes ago and then when the system restarted there was no display. So I restarted the computer and NO POST, no beeps as well. keyboard light does not light up, no display either.

I am now just using my laptop.

Appreciate the help!
0A
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

7E
If you do not know the specific cause of the exception, consider the following issues:
  • Hardware incompatibility. Make sure that any new hardware that is installed is listed in the Microsoft Windows Marketplace Tested Products List.
  • Faulty device driver or system service. A faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.


Other than that we need the DMP files to analyze.

I would suggest trying to boot into safe mode, from the dvd.

If that doesnt work you might want to reset the CMOS battery by unplugging and holding the power button in for a minute.
My System SpecsSystem Spec
18 May 2011   #3
misterxsai

windows 7 ultimate x64
 
 

i tried to reset CMOS but system freezes on windows log on. i am able to go to sage mode with net. can you help me to locate dump. thanks!!!
My System SpecsSystem Spec
.

18 May 2011   #4
misterxsai

windows 7 ultimate x64
 
 

i tried to reset CMOS but system freezes on windows log on. i am able to go to safe mode with net. can you help me to locate dump. thanks!!!
My System SpecsSystem Spec
18 May 2011   #5
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by misterxsai View Post
i tried to reset CMOS but system freezes on windows log on. i am able to go to safe mode with net. can you help me to locate dump. thanks!!!
sure


To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



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.
My System SpecsSystem Spec
19 May 2011   #6
misterxsai

windows 7 ultimate x64
 
 

here's the dump file. hope this helps. thanks!!!
My System SpecsSystem Spec
19 May 2011   #7
misterxsai

windows 7 ultimate x64
 
 

just got another BSOD 0X1E; 0X3E; 0X3B

here's another dump file... thanks
My System SpecsSystem Spec
26 May 2011   #8
misterxsai

windows 7 ultimate x64
 
 

Hi Sir,

any news on what might be the cause of the multiple BSOD?

Thanks!!!
My System SpecsSystem Spec
26 May 2011   #9
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by misterxsai View Post
just got another BSOD 0X1E; 0X3E; 0X3B

here's another dump file... thanks
Sorry about the delay.

You crashes are related to two things. Readybooest and your nvstor64.sys storage driver.

I would stop using ready boost and update the driver as yours is from 2008.

Other drivers needing updating
Code:
nvstor64.sys    8/18/2008 9:53:39 PM        fffff880`010e0000    fffff880`0110c000    0x0002c000    0x48aa27a3                        
dump_nvstor64.sys    8/18/2008 9:53:39 PM        fffff880`05cf1000    fffff880`05d1d000    0x0002c000    0x48aa27a3                        
nvsmu.sys    8/25/2008 6:22:45 AM        fffff880`03fe3000    fffff880`03fee000    0x0000b000    0x48b287f5                        
spldr.sys    5/11/2009 12:56:27 PM        fffff880`01928000    fffff880`01930000    0x00008000    0x4a0858bb                        
amdxata.sys    5/19/2009 1:56:59 PM        fffff880`0110c000    fffff880`01117000    0x0000b000    0x4a12f2eb                        
nvstor.sys    5/20/2009 2:45:37 AM        fffff880`00c5c000    fffff880`00c87000    0x0002b000    0x4a13a711                        
Rt64win7.sys    5/22/2009 10:52:30 AM        fffff880`042b1000    fffff880`042ea000    0x00039000    0x4a16bc2e
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads




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


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

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`03219000 PsLoadedModuleList = 0xfffff800`03456e50
Debug session time: Mon May 16 22:15:09.240 2011 (GMT-4)
System Uptime: 0 days 0:00:55.832
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa801536788b, 2, 1, fffff88001950192}

Unable to load image \SystemRoot\system32\DRIVERS\nvstor64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvstor64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor64.sys
Probably caused by : hardware ( rdyboost!SmdIoTreeIoComplete+6a )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa801536788b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001950192, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c10e0
 fffffa801536788b 

CURRENT_IRQL:  2

FAULTING_IP: 
rdyboost!SmdIoTreeIoComplete+6a
fffff880`01950192 3083f8ff7410    xor     byte ptr [rbx+1074FFF8h],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f1b7d0 -- (.trap 0xfffff88002f1b7d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004c17818 rbx=0000000000000000 rcx=fffffa8004c1bc3f
rdx=fffffa8004c17610 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001950192 rsp=fffff88002f1b968 rbp=0000000000000000
 r8=fffffa8005e093a0  r9=fffffa8004c1b438 r10=0000000000401902
r11=fffffa800468d348 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
rdyboost!SmdIoTreeIoComplete+0x6a:
fffff880`01950192 3083f8ff7410    xor     byte ptr [rbx+1074FFF8h],al ds:8000:00000000`1074fff8=??
Resetting default scope

MISALIGNED_IP: 
rdyboost!SmdIoTreeIoComplete+6a
fffff880`01950192 3083f8ff7410    xor     byte ptr [rbx+1074FFF8h],al

LAST_CONTROL_TRANSFER:  from fffff80003288c69 to fffff80003289700

STACK_TEXT:  
fffff880`02f1b688 fffff800`03288c69 : 00000000`0000000a fffffa80`1536788b 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f1b690 fffff800`032878e0 : 00000000`00401902 fffffa80`04c17893 01535242`00000050 00000000`09daa4a7 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b7d0 fffff880`01950192 : fffff800`0328bd26 fffffa80`04c177bb fffffa80`04c15650 fffffa80`04c17610 : nt!KiPageFault+0x260
fffff880`02f1b968 fffffa80`04ab9928 : fffffa80`04ab7008 fffff880`0114b0cc fffff880`02f1b9d0 fffff880`02f1b9f9 : rdyboost!SmdIoTreeIoComplete+0x6a
fffff880`02f1b9a8 fffffa80`04ab7008 : fffff880`0114b0cc fffff880`02f1b9d0 fffff880`02f1b9f9 fffff880`0114af1d : 0xfffffa80`04ab9928
fffff880`02f1b9b0 fffff880`0114b0cc : fffff880`02f1b9d0 fffff880`02f1b9f9 fffff880`0114af1d fffffa80`00000001 : 0xfffffa80`04ab7008
fffff880`02f1b9b8 fffff880`02f1b9d0 : fffff880`02f1b9f9 fffff880`0114af1d fffffa80`00000001 00000000`00000001 : nvstor64+0x1d0cc
fffff880`02f1b9c0 fffff880`02f1b9f9 : fffff880`0114af1d fffffa80`00000001 00000000`00000001 fffffa80`04ab7008 : 0xfffff880`02f1b9d0
fffff880`02f1b9c8 fffff880`0114af1d : fffffa80`00000001 00000000`00000001 fffffa80`04ab7008 fffffa80`04ab7008 : 0xfffff880`02f1b9f9
fffff880`02f1b9d0 fffffa80`00000001 : 00000000`00000001 fffffa80`04ab7008 fffffa80`04ab7008 fffffa80`06b40000 : nvstor64+0x1cf1d
fffff880`02f1b9d8 00000000`00000001 : fffffa80`04ab7008 fffffa80`04ab7008 fffffa80`06b40000 00000000`00000001 : 0xfffffa80`00000001
fffff880`02f1b9e0 fffffa80`04ab7008 : fffffa80`04ab7008 fffffa80`06b40000 00000000`00000001 00000000`00000002 : 0x1
fffff880`02f1b9e8 fffffa80`04ab7008 : fffffa80`06b40000 00000000`00000001 00000000`00000002 fffffa80`04c128e0 : 0xfffffa80`04ab7008
fffff880`02f1b9f0 fffffa80`06b40000 : 00000000`00000001 00000000`00000002 fffffa80`04c128e0 fffffa80`04c128e0 : 0xfffffa80`04ab7008
fffff880`02f1b9f8 00000000`00000001 : 00000000`00000002 fffffa80`04c128e0 fffffa80`04c128e0 00000000`00000000 : 0xfffffa80`06b40000
fffff880`02f1ba00 00000000`00000002 : fffffa80`04c128e0 fffffa80`04c128e0 00000000`00000000 fffffa80`04c12790 : 0x1
fffff880`02f1ba08 fffffa80`04c128e0 : fffffa80`04c128e0 00000000`00000000 fffffa80`04c12790 00000000`ffffffff : 0x2
fffff880`02f1ba10 fffffa80`04c128e0 : 00000000`00000000 fffffa80`04c12790 00000000`ffffffff 00000000`00000004 : 0xfffffa80`04c128e0
fffff880`02f1ba18 00000000`00000000 : fffffa80`04c12790 00000000`ffffffff 00000000`00000004 fffffa80`05331970 : 0xfffffa80`04c128e0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!SmdIoTreeIoComplete+6a
fffff880`01950192 3083f8ff7410    xor     byte ptr [rbx+1074FFF8h],al

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  rdyboost!SmdIoTreeIoComplete+6a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_rdyboost.sys

BUCKET_ID:  X64_IP_MISALIGNED_rdyboost.sys

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa801536788b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001950192, address which referenced memory

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


WRITE_ADDRESS:  fffffa801536788b 

CURRENT_IRQL:  2

FAULTING_IP: 
rdyboost!SmdIoTreeIoComplete+6a
fffff880`01950192 3083f8ff7410    xor     byte ptr [rbx+1074FFF8h],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f1b7d0 -- (.trap 0xfffff88002f1b7d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004c17818 rbx=0000000000000000 rcx=fffffa8004c1bc3f
rdx=fffffa8004c17610 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001950192 rsp=fffff88002f1b968 rbp=0000000000000000
 r8=fffffa8005e093a0  r9=fffffa8004c1b438 r10=0000000000401902
r11=fffffa800468d348 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
rdyboost!SmdIoTreeIoComplete+0x6a:
fffff880`01950192 3083f8ff7410    xor     byte ptr [rbx+1074FFF8h],al ds:8000:00000000`1074fff8=??
Resetting default scope

MISALIGNED_IP: 
rdyboost!SmdIoTreeIoComplete+6a
fffff880`01950192 3083f8ff7410    xor     byte ptr [rbx+1074FFF8h],al

LAST_CONTROL_TRANSFER:  from fffff80003288c69 to fffff80003289700

STACK_TEXT:  
fffff880`02f1b688 fffff800`03288c69 : 00000000`0000000a fffffa80`1536788b 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f1b690 fffff800`032878e0 : 00000000`00401902 fffffa80`04c17893 01535242`00000050 00000000`09daa4a7 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b7d0 fffff880`01950192 : fffff800`0328bd26 fffffa80`04c177bb fffffa80`04c15650 fffffa80`04c17610 : nt!KiPageFault+0x260
fffff880`02f1b968 fffffa80`04ab9928 : fffffa80`04ab7008 fffff880`0114b0cc fffff880`02f1b9d0 fffff880`02f1b9f9 : rdyboost!SmdIoTreeIoComplete+0x6a
fffff880`02f1b9a8 fffffa80`04ab7008 : fffff880`0114b0cc fffff880`02f1b9d0 fffff880`02f1b9f9 fffff880`0114af1d : 0xfffffa80`04ab9928
fffff880`02f1b9b0 fffff880`0114b0cc : fffff880`02f1b9d0 fffff880`02f1b9f9 fffff880`0114af1d fffffa80`00000001 : 0xfffffa80`04ab7008
fffff880`02f1b9b8 fffff880`02f1b9d0 : fffff880`02f1b9f9 fffff880`0114af1d fffffa80`00000001 00000000`00000001 : nvstor64+0x1d0cc
fffff880`02f1b9c0 fffff880`02f1b9f9 : fffff880`0114af1d fffffa80`00000001 00000000`00000001 fffffa80`04ab7008 : 0xfffff880`02f1b9d0
fffff880`02f1b9c8 fffff880`0114af1d : fffffa80`00000001 00000000`00000001 fffffa80`04ab7008 fffffa80`04ab7008 : 0xfffff880`02f1b9f9
fffff880`02f1b9d0 fffffa80`00000001 : 00000000`00000001 fffffa80`04ab7008 fffffa80`04ab7008 fffffa80`06b40000 : nvstor64+0x1cf1d
fffff880`02f1b9d8 00000000`00000001 : fffffa80`04ab7008 fffffa80`04ab7008 fffffa80`06b40000 00000000`00000001 : 0xfffffa80`00000001
fffff880`02f1b9e0 fffffa80`04ab7008 : fffffa80`04ab7008 fffffa80`06b40000 00000000`00000001 00000000`00000002 : 0x1
fffff880`02f1b9e8 fffffa80`04ab7008 : fffffa80`06b40000 00000000`00000001 00000000`00000002 fffffa80`04c128e0 : 0xfffffa80`04ab7008
fffff880`02f1b9f0 fffffa80`06b40000 : 00000000`00000001 00000000`00000002 fffffa80`04c128e0 fffffa80`04c128e0 : 0xfffffa80`04ab7008
fffff880`02f1b9f8 00000000`00000001 : 00000000`00000002 fffffa80`04c128e0 fffffa80`04c128e0 00000000`00000000 : 0xfffffa80`06b40000
fffff880`02f1ba00 00000000`00000002 : fffffa80`04c128e0 fffffa80`04c128e0 00000000`00000000 fffffa80`04c12790 : 0x1
fffff880`02f1ba08 fffffa80`04c128e0 : fffffa80`04c128e0 00000000`00000000 fffffa80`04c12790 00000000`ffffffff : 0x2
fffff880`02f1ba10 fffffa80`04c128e0 : 00000000`00000000 fffffa80`04c12790 00000000`ffffffff 00000000`00000004 : 0xfffffa80`04c128e0
fffff880`02f1ba18 00000000`00000000 : fffffa80`04c12790 00000000`ffffffff 00000000`00000004 fffffa80`05331970 : 0xfffffa80`04c128e0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!SmdIoTreeIoComplete+6a
fffff880`01950192 3083f8ff7410    xor     byte ptr [rbx+1074FFF8h],al

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  rdyboost!SmdIoTreeIoComplete+6a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_rdyboost.sys

BUCKET_ID:  X64_IP_MISALIGNED_rdyboost.sys

Followup: MachineOwner
---------
My System SpecsSystem Spec
26 May 2011   #10
misterxsai

windows 7 ultimate x64
 
 

how do I stop using readyboost?
My System SpecsSystem Spec
Reply

 BSOD 0x7E




Thread Tools




Similar help and support threads
Thread Forum
BSOD 0x7E iastor.sys consistently
Hi, I have started getting BSOD STOP 0x0000007E error and iastor.sys driver was listed on the blue screen. I get the BSOD every 20-30 mins. Have already tried the following: 1. Updated iastor.sys driver to the latest one 2. Uninstalled most recent windows updates. I started getting the BSODs...
BSOD Help and Support
Reoccurring BSOD's (0xD1 & 0x7E)
Hey guys, So I have been having these reoccurring stop errors. It first started with the 0x7E error. I restored my system to an earlier time, the re installed a new driver. The message then changed to 0xD1. This one displayed the messaged DRIVER_IRQL_NOT_LESS_OR_EQUAL. I took my computer into...
BSOD Help and Support
BSOD doing anything heavy, error 0x7e
Hello, since recently my computer started giving me BSODs, it usually occurs when im doing anything cpu heavy things (games, repairing rar files ect.) i really hope any of the experts here can fix it. 64 bits clean harddrive, w7 first os that's o nthere retail hardware is about 1 year 6...
BSOD Help and Support
bsod 0X7e when i wake up display...
hello, since i update my nvidia graphic card driver to the last ver 296.10 i got a BSOD 0X0000007e, every time i turn my screen on(i dont have sleep mode or hibernate mode or screensaver active) as long as i using the computer everything fine, but if i dont using the computer for several hours...
BSOD Help and Support
Windows 7 will not start: BSOD 0x7e
Hi. I'm trying to fix a Toshiba laptop running Windows 7 Home Premium 32bit. Windows begins to load with the animated logo on the screen, then it blue screens with an 0x7e error. The info does not list a file, just these parameters: (0xC0000006, 0x878ED630, 0X8DD1F770, 0x8DD1F350)
BSOD Help and Support
BSoD 0x7e x64 Pro
Hi guys, Last week I've updated my motherboard, cpu and memory. Since then, I am getting BSoD's. Almost every time I boot the desktop computer, it shows me the screen of death... I tried to read the minidumps myself but I just don't get it, so I figured I'd upload it on this forum. I'm...
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 13:14.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App