• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 556
  • Last Modified:

Vista x64 BSOD 0x7E with no driver mentioned

I have a Acer Aspirce 6930 running Vista 64 bit that will load all the way to the blue background and vista logo, but then makes the "dung" error noise, BSODs, and reboots. After setting the "don't restart on crash" option, I can see that it's a 0x7E (paramater1, paramater2, paramater3, paramater4) but it doesn't list a driver that failed. Anyone have any ideas on what might be the cause?

Alternatively, is there a way to reinstall Vista but preserve all of the programs, user files? I used to do that a lot with XP, but haven't yet with this. Thanks in advance!
0
biofishfreak
Asked:
biofishfreak
  • 18
  • 10
  • 5
  • +1
2 Solutions
 
nobusCommented:
some info here :  http://www.techsupportforum.com/forums/f299/vista-0x7e-stop-error-315577.html
attach the minidump here  for more info
you can also try a repair : http://www.bleepingcomputer.com/tutorials/tutorial148.html
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Does it create a dump file?
0
 
biofishfreakAuthor Commented:
It does create a dump file, though I couldn't get it to open. I can boot into safe mode (with networking), if that helps at all.

nobus, using that first link I'll check if SP1 is installed or not (I think it is.) As for a repair, I tried that early on and it couldn't find any start up issues. Running a system restore fails (I've tried several different restores) and when I run sfc /scannow it fixes some issues but others "can't be repaired."

Sadly I left the laptop at home today, so I'll try digging up the dump file when I get home. hanccocka, is there a specific dump file you want or are curious about? (Windows is full of 'em.)
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
biofishfreakAuthor Commented:
I just remembered Vista is on SP2, so I'll try to install that (like I said, I think it's running SP1 currently.)
0
 
nobusCommented:
get the latest minidump if possible
0
 
biofishfreakAuthor Commented:
So I couldn't install the SDK tools onto the Vista machine in safemode (gave an error), so I copied the file to my Win7 x64 laptop and I'm not sure if it's the actual dump saying the code below or just the analyzer having a fit with the file. Please let me know if this helps at all, and if you have any thoughts. I will try to have the laptop on me tomorrow so I can respond more timely.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\Mini030711-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`02065000 PsLoadedModuleList = 0xfffff800`0222adb0
Debug session time: Mon Mar  7 14:19:55.234 2011 (UTC - 7:00)
System Uptime: 0 days 0:01:23.952
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {2e7a6a5e2, c, 0, fffff800020c693b}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+6193b )

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

Open in new window

0
 
nobusCommented:
just post the dmp plse
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
upload your dump to this site

http://www.osronline.com/page.cfm?name=analyze
0
 
biofishfreakAuthor Commented:
hmmm... looking at the dump again, it looks like the file date is from a few months ago, not the BSOD I just had occur 10 minutes ago. Any thoughts of where I should look to make sure I'm checking the right file. If I look at either c:\windows\minidump or the memory dump in the \windows\ folder, they aren't recent.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
is it set to create a crash dump?

is it creating a dump on bsod?

if the storage driver had been compromised, maybe due to storage fault, you may not get a dump.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
so theres a clue, run chkdsk, surface scan
0
 
biofishfreakAuthor Commented:
wouldn't a storage fault cause it to not boot into safe mode? the bsod says its creating a dump.
Thanks for your continued support!
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Safe Mode, doesn't load all the drivers, dlls etc could be a sector on the disk which is bad, which has an important driver or dll that's not used in safe mode.

Check hard disk and memory. (memtest86.org)
0
 
biofishfreakAuthor Commented:
True. i did run grc and it came up clean. ill try running chkdsk too.
0
 
biofishfreakAuthor Commented:
Sorry for the last post being so low quality. Yes, I did check and the system is set to create a dump upon failure. I tried changing from mem dump to mini dump and it still doesn't create a dump upon BSOD.
As for "grc" I mentioned, I meant I ran Spin Rite. I've tried running chkdsk a few times but it has to reboot to run it, and apparently it won't run if rebooting into safe mode, and when normal booting it BSODs before chkdsk runs. Running it from within the Recovery Menu doesn't work either.
0
 
nobusCommented:
your  OS can be corrupted - try sfc or a repair :
      http://vistasupport.mvps.org/system_file_checker.htm            SFC in Vista
      http://www.bleepingcomputer.com/tutorials/tutorial148.html      repair Vista
0
 
biofishfreakAuthor Commented:
Ive already run those both. The repair said nothing is wrong, and sfc throws errors. I will rerun it overnight and post the errors tomorrow morning.
0
 
nobusCommented:
looks like disk problems to me -  run a diag to be sure : http://www.ultimatebootcd.com/      
0
 
biofishfreakAuthor Commented:
I feel so smart... I was running a chkdsk /b from a Vista Repair Disc I made and getting an error about the disk being write protected, then realized I was trying to chkdsk the CD.
chkdsk c: /B

Open in new window

I'll update this when that finishes.
0
 
nobusCommented:
chkdsk is NOT a disk diag -it checks the file sysetem
plse run the diag as suggested !
0
 
biofishfreakAuthor Commented:
Which tool should I run in UBCD? Like I said before, I've run Spin Rite (and disk utility, not file system) and it came up with no errors.
0
 
nobusCommented:
the diag for the disk brand of course
0
 
biofishfreakAuthor Commented:
:-P *grabs screw driver*
0
 
biofishfreakAuthor Commented:
Just ran the Seagate tools, the drive came up clean. I think I'm just going to nuke the laptop if I can't get things working soon. One thing I will mention is that every time I disable a driver or service in safe mode, upon rebooting it still shows as active (rebooting both straight into safe mode but also doing a regular boot > BSOD > safe mode.)
0
 
joinaunionCommented:
Did you add new memory?
0
 
biofishfreakAuthor Commented:
Nope. I did try swapping the ram out though- same issue.
0
 
joinaunionCommented:
Can you enter bios then load defaults then reboot and post back?
0
 
biofishfreakAuthor Commented:
Same issue. im running a memtest now.
0
 
biofishfreakAuthor Commented:
Ran memtest (from MS) and everythingcame up good.
0
 
joinaunionCommented:
Follow this tutorial http://www.bleepingcomputer.com/tutorials/tutorial148.html
If you need to choose command prompt then type fixmbr and also try fixboot
http://www.michaelstevenstech.com/r_c_cmds.htm
0
 
nobusCommented:
ok  - since ram and disk look OK, it is probably the OS
run the repair as suggested by joinaunion
if that does not work - backup your files -  (you should have done that by now) and do a fresh install
0
 
biofishfreakAuthor Commented:
Ill try the Repair one more time , but nuking it is what i think ill have to do. As for a backup, I made one before doing anything, of course. ;) Ill post back later today on everything.
0
 
biofishfreakAuthor Commented:
So nuking the system of course resolved the issue. I appreciate the two of you helping me on this case for so long, and split the points down the middle since you both gave lots of suggestions. I did learn something new though with that online dump analyzer.
0
 
nobusCommented:
i still wonder why you did not post it here..
0
 
biofishfreakAuthor Commented:
I mentioned the dump analyzer because I hadn't seen that before for a future reference. As far as the weird things going on, the only dump and mini dump on the system were from four months ago. I tried moving them to see if it was somehow blocking a new dump from happening, but still no dump. I made sure everything was turned on too, just nothing would write.

Believe you me, I would have liked to have uploaded a dump, but I had nothing to offer. :(
0
 
nobusCommented:
ah - i see; tx for feedback
0

Featured Post

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

  • 18
  • 10
  • 5
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now