Windows 10: BSOD on windows 10 and 7 but not on XP

Hello, so some time ago I got windows 7 64 bit, but it BSODed all the time. So I upgraded to win10 as I thought it may fix it. I can switch between XP and 10 freely on my PC and win10 is BSODing every 5 minutes or so and XP is totally fine. I tried everything on 7 and 10 and I still have no clue what the cause for the BSODs is and if it is even the same for both OSs.
Thanks for reading.

Edit: XP is 32 bit, 7 and 10 is 64 bit

:)

 

How do I replace the modern-type BSoD with a Windows 7-type BSoD in Windows 10?

Okay, so, the BSoD in Windows 10 is more modern than previous versions of Windows; however when I get a 640x480 BSoD the text is so poor that it can be harder to read.

So, I'm asking this: How can I replace the Windows 10 BSoD with a Windows 7-type BSoD?

The Windows 7-type BSoD has all the details and instructions that can be used to troubleshoot the error. The later Stop codes can also be used in the BSoD.

I searched for many tutorials on how to display additional BSoD details in Windows 10. However, adding DisplayParameters to the CrashControl hive has no effect on it; that will just keep the original Windows 10 BSoD and display the four parameters on the
top-left corner of the screen.

I've been looking everywhere for a tutorial on how to replace the Windows 10 BSoD with the Windows 7-type BSoD, but it returned no results. I really like the fact that I learned about how the original XP BSoD looked like, I wanted to restore it in Windows
10.

If anyone has any ideas, let me know so we can talk about it. Oh, and don't forget to share your thoughts! Thanks, everyone!

 

Win 7 Key works on Win 10 but not on Win 7.

I dont have a Windows 7 backup as I have factory reset my pc and dont think I ever did a backup. Also I cant download the Win 7 ISO file so I cannot do a clean install it.

 

Try updating or removing firefox.

 

I just did a fresh windows 10 reinstall and it still BSODs (I don't have firefox installed yet)

Edit: 16 hours memtest 86+, 8 passes, 0 errors

 

Looking at your dumps (0x1A, 0x1E and 0x139) it's pretty open as to what the problem could be, I'm not ruling out hardware yet but let's rule out some other things first. It's possible that a driver is causing the issue so we'll see if we can make any poke their head out.






Diagnostic Test

DRIVER VERIFIER
Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Forums



Warning Make a System Restore point before enabling Driver Verifier.


Note Your system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
Post any resulting dump files.

 

Here are 4 minidumps that happened after enabling driver verifier.

 

Finally we have a culprit, Avast. Please uninstall Avast and use native Defender coupled with MalwareBytes.



Note Make sure you uncheck the 'Enable Free Trial' box when installing.





Code: ffffd000`22619e88 fffff800`c5600d77Unable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswSnx.sys *** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys aswSnx+0x50d77[/quote]

 

Already tried that, but I guess I'll remove it again.
Btw: Thanks for the help.

Edit: ok, maybe the trojans were the problem... *Eek

 

Trojans? What picked those up?

 

I installed MalwareBytes and ran it and it found some trojans *Shock

 

Run a round of SuperAntiSpyware as linked in my signature, full scans of both would be best.

 

I did the second scan,
still BSODing (as expected)

 

It's another 0x133, this is a difficult one to determine because the problem stems from DPCs running from multiple drivers so the stack is insufficient to pinpoint the culprit.
Code: DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Arguments: Arg1: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. The offending component can usually be identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: 0000000000000000 Arg4: 0000000000000000[/quote]
The only suggestion I can make at the moment is to enable DV again and see if it can weed out any more problematic drivers.

 

Another crash, this time it's flagging "mmcss.sys"
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc000001d, fffff801a8e416be, ffffd001c89f78c8, ffffd001c89f70e0} Probably caused by : mmcss.sys ( mmcss!CiSchedulerWait+8e ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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 happening. Arguments: Arg1: ffffffffc000001d, The exception code that was not handled Arg2: fffff801a8e416be, The address that the exception occurred at Arg3: ffffd001c89f78c8, Exception Record Address Arg4: ffffd001c89f70e0, Context Record Address Debugging Details: ------------------ SYSTEM_SKU: SKU SYSTEM_VERSION: System Version BIOS_DATE: 04/28/2015 BASEBOARD_PRODUCT: A88X-PLUS BASEBOARD_VERSION: Rev X.0x BUGCHECK_P1: ffffffffc000001d BUGCHECK_P2: fffff801a8e416be BUGCHECK_P3: ffffd001c89f78c8 BUGCHECK_P4: ffffd001c89f70e0 EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {AUSNAHME} Ung ltige Anweisung Es wurde versucht, eine ung ltige Anweisung auszuf hren. FAULTING_IP: mmcss!CiSchedulerWait+8e fffff801`a8e416be 44382d6c5b0000 cmp byte ptr [mmcss!CiSchedulerDisallowLazyMode (fffff801`a8e47231)],r13b EXCEPTION_RECORD: ffffd001c89f78c8 -- (.exr 0xffffd001c89f78c8) ExceptionAddress: fffff801a8e416be (mmcss!CiSchedulerWait+0x000000000000008e) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000 NumberParameters: 0 CONTEXT: ffffd001c89f70e0 -- (.cxr 0xffffd001c89f70e0) rax=0000000000000000 rbx=0000000000000000 rcx=fffff801a8e470c0 rdx=0000000000000000 rsi=0000000000000010 rdi=fffff801a8e47180 rip=fffff801a8e416be rsp=ffffd001c89f7b00 rbp=00000040c38cd264 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=fffff801a8e47170 r12=ffffd001c89f7c00 r13=0000000000000000 r14=0000000000000010 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 mmcss!CiSchedulerWait+0x8e: fffff801`a8e416be 44382d6c5b0000 cmp byte ptr [mmcss!CiSchedulerDisallowLazyMode (fffff801`a8e47231)],r13b ds:002b:fffff801`a8e47231=00 Resetting default scope CPU_COUNT: 4 CPU_MHZ: c78 CPU_VENDOR: AuthenticAMD CPU_FAMILY: 15 CPU_MODEL: 10 CPU_STEPPING: 1 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: AV PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc000001d - {AUSNAHME} Ung ltige Anweisung Es wurde versucht, eine ung ltige Anweisung auszuf hren. ANALYSIS_VERSION: 10.0.10240.9 amd64fre LAST_CONTROL_TRANSFER: from fffff801a8e429c8 to fffff801a8e416be FAILED_INSTRUCTION_ADDRESS: mmcss!CiSchedulerWait+8e fffff801`a8e416be 44382d6c5b0000 cmp byte ptr [mmcss!CiSchedulerDisallowLazyMode (fffff801`a8e47231)],r13b STACK_TEXT: ffffd001`c89f7b00 fffff801`a8e429c8 : 00000000`00000010 00000000`00000016 00000000`00000001 ffffe001`fc83a230 : mmcss!CiSchedulerWait+0x8e ffffd001`c89f7ba0 fffff801`34369698 : 00000000`00000010 ffffe001`fc83a230 ffffe001`fdae5040 00000000`00000000 : mmcss!CiSchedulerThreadFunction+0x1b8 ffffd001`c89f7c00 fffff801`343d6306 : fffff801`345e7180 ffffe001`fdae5040 ffffe001`fdae8080 00000000`00000000 : nt!PspSystemThreadStartup+0x58 ffffd001`c89f7c60 00000000`00000000 : ffffd001`c89f8000 ffffd001`c89f2000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 FOLLOWUP_IP: mmcss!CiSchedulerWait+8e fffff801`a8e416be 44382d6c5b0000 cmp byte ptr [mmcss!CiSchedulerDisallowLazyMode (fffff801`a8e47231)],r13b SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: mmcss!CiSchedulerWait+8e FOLLOWUP_NAME: MachineOwner MODULE_NAME: mmcss IMAGE_NAME: mmcss.sys DEBUG_FLR_IMAGE_TIMESTAMP: 559f383c IMAGE_VERSION: 10.0.10240.16384 STACK_COMMAND: .cxr 0xffffd001c89f70e0 ; kb BUCKET_ID_FUNC_OFFSET: 8e FAILURE_BUCKET_ID: AV_BAD_IP_mmcss!CiSchedulerWait BUCKET_ID: AV_BAD_IP_mmcss!CiSchedulerWait PRIMARY_PROBLEM_CLASS: AV_BAD_IP_mmcss!CiSchedulerWait ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:av_bad_ip_mmcss!cischedulerwait FAILURE_ID_HASH: {0751b085-dc92-d0ca-8974-d74e14e97034} Followup: MachineOwner ---------[/quote]