Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random BSOD on new Windows 7 installation?


  • Please log in to reply
8 replies to this topic

#1 Iden

Iden

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:01:30 PM

Posted 30 December 2017 - 08:08 PM

Following the Posting Instructions for the forum:

 

Attached File  SysnativeFileCollectionApp.zip   411.35KB   6 downloads

 

And here is the Speccy system snapshot

 

 

I'm mostly worried that whatever has caused 2 crashes so far with a fresh installation will turn into a constant issue if I don't figure out why it happened!  :unsure:

 

What happened:

I recently installed Windows 7 Home Premium 64-bit, and everything was going well, but then there was a random BSOD.

 

After that I ran Windows Update to install fixes and security things, hoping that might fix it. After it restarted to finish installing updates, it said it had recovered from another crash. I hadn't seen a crash while it restarted though!

 

 

I'll start doing the "memory and hard drive diagnostics" requested in the Post Instruction guide now.

 

Thanks for any help!

 



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:02:30 PM

Posted 30 December 2017 - 09:37 PM

I'll start doing the "memory and hard drive diagnostics" requested in the Post Instruction guide now.

Yes, please do so. If they pass please run Driver Verifier according to these instructions - https://www.bleepingcomputer.com/forums/t/576333/driver-verifier-bsod-related-windows-10-81-8-7-vista/
 
Please also run MGADiag when you're free...
  • Download and save MGADiag from here.
  • Navigate to the directory where you saved the file.
  • Right-click on MGADiag.exe, select Run as administrator, and accept any User Account Control prompts.
  • Click Continue.
  • Click Copy.
  • Paste the copied information in your next reply.
Thank you.

Edited by bwv848, 30 December 2017 - 09:37 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 Iden

Iden
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:01:30 PM

Posted 31 December 2017 - 01:39 PM

I still have to do the two new tests you've suggested, which I'll do right after reporting on the things I've done so far!

 

 

So far: 

 

Seagate tools drive test thing: Long Generic - Pass for both drives

 

Memtest86, the site suggested at least 3 passes so I let it do 4 and a half, which took 6 hours and had 0 errors

 

 

But then when trying to restart to come back here to post this I had a blue screen  :(

 

"STOP unknown hard error"

 

which automatically restarted to another blue screen:

 

STOP: 0x0000001E (0XFFFFFFFF0000005, 0XFFFF8000C095565, 0X0000000000000000, 0XFFFFFFFFFFFFFFF)

 

and then kept asking me if I wanted to run startup repair, which didn't work, but then it restarted normally and I'm back!

 

 

I'll go figure out Driver Verifier and then MGADiag and will be back, maybe on my phone if this gets worse!



#4 Iden

Iden
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:01:30 PM

Posted 31 December 2017 - 01:52 PM

 Please also run MGADiag when you're free...

 

I have Driver Verifier running now and the instructions said it has to run for at least 24 hours?

 

Do any of the results I've posted so far change anything?

 

Here are the results of the MGADiag thing:

 

 

 

Diagnostic Report (1.9.0019.0):
-----------------------------------------
WGA Data-->
Validation Status: Genuine
Validation Code: 0
 
Cached Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-9PMPY-F9XG3-XYC44
Windows Product Key Hash: grWNK4ZwuuFHssjIzCPh5IrcKS8=
Windows Product ID: 00359-OEM-9811907-11604
Windows Product ID Type: 8
Windows License Type: COA SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {BD39847A-5642-4324-B2E6-B971136C9257}(1)
Is Admin: Yes
TestCab: 0x0
WGA Version: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_ldr.170913-0600
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A
 
WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
 
WGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002
 
OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002
 
OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
 
Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Opera\launcher.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed
 
File Scan Data-->
 
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{BD39847A-5642-4324-B2E6-B971136C9257}</UGUID><Version>1.9.0019.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-XYC44</PKey><PID>00359-OEM-9811907-11604</PID><PIDType>8</PIDType><SID>S-1-5-21-1726791961-2266604940-3971151324</SID><SYSTEM><Manufacturer>ASUS</Manufacturer><Model>All Series</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1204</Version><SMBIOSVersion major="2" minor="8"/><Date>20140620000000.000000+000</Date></BIOS><HWID>830B0500018400F4</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  
 
Spsys.log Content: 0x80070002
 
Licensing Data-->
Software licensing service version: 6.1.7601.17514
 
Name: Windows® 7, HomePremium edition
Description: Windows Operating System - Windows® 7, OEM_COA_SLP channel
Activation ID: 5e017a8a-f3f9-4167-b1bd-ba3e236a4d8f
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00196-119-011604-02-1033-7601.0000-3632017
Installation ID: 013192121386234224427071235893395881018795468736459932
Partial Product Key: XYC44
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 12/31/2017 2:20:57 PM
 
Windows Activation Technologies-->
HrOffline: N/A
HrOnline: N/A
HealthStatus: N/A
Event Time Stamp: N/A
WAT Activex: Registered
WAT Admin Service: Registered
 
HWID Data-->
HWID Hash Current: KgAAAAAAAQABAAEAAAACAAAAAQABAAEAln1kd6wOqH1GcKgcnCooP8j2
 
OEM Activation 1.0 Data-->
N/A
 
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name OEMID Value OEMTableID Value
  APIC ALASKA A M I
  FACP ALASKA A M I
  HPET ALASKA A M I
  MCFG ALASKA A M I
  FPDT ALASKA A M I
  SSDT Ther_R Ther_Rvp
  SSDT Ther_R Ther_Rvp
  SSDT Ther_R Ther_Rvp
  SSDT Ther_R Ther_Rvp
  SSDT Ther_R Ther_Rvp

Edited by Iden, 31 December 2017 - 02:25 PM.


#5 Iden

Iden
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:01:30 PM

Posted 01 January 2018 - 02:06 PM

If they pass please run Driver Verifier according to these instructions - https://www.bleepingcomputer.com/forums/t/576333/driver-verifier-bsod-related-windows-10-81-8-7-vista/

 

I'm still running Driver Verifier and am not sure when to stop it or post anything about it, but I shut my computer down this morning and when I tried to start it recently it had two STOP hard error blue screens before it would finally go to Windows. I think I had some yesterday as well.

 

Should I be posting those somehow, or just continue waiting for Driver Verifier to do something else?



#6 Iden

Iden
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:01:30 PM

Posted 01 January 2018 - 10:31 PM

OK I ran Driver Verifier for over 24 hours and had multiple blue screens and Stop Hard Error crashes at startup, it kept saying Windows didn't start right then would do it again. :(

 

I turned it off just now because the post said 24 hours was OK, and I'm attaching the Minidump files in a zip file as instructed by the Driver Verifier post!

 

Here they are:

Attached File  123117-25272-01.zip   28.95KB   2 downloads

 

Thanks for any help, and for the help so far!

 

 



#7 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:02:30 PM

Posted 01 January 2018 - 11:24 PM

Thank you!

You may turn off Driver Verifier for now. At first I had thought that your issues were actually software-related, but that doesn't seem to be the case now. For the record, the dumps in post #1 weren't particularly useful at all anyway — very little info!

I just loaded up the Driver Verifier dumps. They were STOP c0000221s, the c0000221 error code indicating:

0: kd> !error c0000221
Error code: (NTSTATUS) 0xc0000221 (3221226017) - {Bad Image Checksum}  The image %hs is possibly corrupt. The header checksum does not match the computed checksum.

It does appear that the BSODs occurred at startup, am I right? Regardless, they revealed nothing at all.

Given that Driver Verifier didn't find any obvious issues (though we could leave Verifier running for longer) and this is a clean install, I do suspect that we may be dealing with unknown hardware failure here. Did you just build this PC (I don't think so honestly)? If not, what was the reason for the reinstall, and were you experiencing any BSODs before the reinstall?

I would like you to run MemTest86 again — I honestly suspect a RAM issue, but I don't have anything to justify my claims (apart from the rather useless, strange dumps!). This time test one stick of RAM for eight passes, preferably alternating the slots.

We may consider a BIOS update in the future, but I wouldn't do one quite yet if I were you (with potentially faulty hardware things could get ugly).

Please also run the hardware diagnostics on this page - www.carrona.org/hwdiag.html Run all the tests, especially Prime95's blend test (which will stress the CPU and RAM).


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#8 Iden

Iden
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:01:30 PM

Posted 13 January 2018 - 08:16 PM

I would like you to run MemTest86 again — I honestly suspect a RAM issue, but I don't have anything to justify my claims (apart from the rather useless, strange dumps!).

 

I'm sorry for the reply delay! Thank you for being so helpful!

 

It was a RAM issue! :( You were right. I'm sad that I have less RAM now, but glad I can reliably use my PC!

 

Thank you so much for the help!!



#9 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:02:30 PM

Posted 13 January 2018 - 09:00 PM

No problem! Glad I could help, thanks for the update.


Edited by bwv848, 13 January 2018 - 09:01 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users