BSOD after starting up computer, first time experiencing

EDIT: Solved for now

Hey all,

Just booted up, and about 20 seconds after getting into Windows, I got a BSOD. I wasn't looking at the screen when it happened but I briefly saw some type of counter, increasing in number, up to 100, at which point the computer restarted. Any clues? Thanks for your help!

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 4a
BCP1: 0000000076FB132A
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8800AB9DB60
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\021116-7768-01.dmp
C:\Users\JP\AppData\Local\Temp\WER-17097-0.sysdata.xml

Hello AshiiT.

You will need to upload the dmp file in a zip file for us to help you.

When you respond/write a reply, there is a paperclip icon, click it and from there you can add files as attachments.

Cheers, Boris :)

Please post the report of Windows Genuine and Activation Issue Posting Instruction

Code:

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\martijn\AppData\Local\Temp\Temp1_AshiiT Minidump.zip\021116-7768-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\xNtKrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for xNtKrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for xNtKrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`0361c000 PsLoadedModuleList = 0xfffff800`03860890
Debug session time: Thu Feb 11 20:29:23.133 2016 (UTC + 1:00)
System Uptime: 0 days 0:01:28.961
Unable to load image \SystemRoot\system32\xNtKrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for xNtKrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for xNtKrnl.exe
Loading Kernel Symbols

I think it is quite clear that this isn't genuine Windows 7 version :/

Pc shops usually install counterfeit systems because that saves money.

If you didn't pay for a Windows OEM license at least, then I suppose it's not surprising that one was not placed on the system. However, they should definitely not be installing license hacks (illegal), and technically sales of Windows 7 by OEMs was stopped last year, so they shouldn't be installing Windows 7 on a machine without selling a Windows 10 Pro license (and using downgrade rights), which wouldn't have required a hacked install either.

This place you found is shady, and probably worth reporting anonymously to Microsoft.

cluberti said:

If you didn't pay for a Windows OEM license at least, then I suppose it's not surprising that one was not placed on the system. However, they should definitely not be installing license hacks (illegal), and technically sales of Windows 7 by OEMs was stopped last year, so they shouldn't be installing Windows 7 on a machine without selling a Windows 10 Pro license (and using downgrade rights), which wouldn't have required a hacked install either.

This place you found is shady, and probably worth reporting anonymously to Microsoft.

I wonder if it would be that easy.

And honestly I've never heard that M$ makes house calls.

There's a site to report stuff like this. Not sure if it'd happen or not, but the site exists...

https://www.microsoft.com/en-us/howt...fr/Report.aspx