next »

[Please Support Us!]

Please Support Us!

Please help keep (=WDG=) alive

• Server rules
• Forum rules
• Join us
  
• Clan members
• About the clan
• Server stats
• WDG YouTube Channel
• WDG Downloads
• IRC Webchat

Steam groups:

• WDG community
• WDG clan group
• WDG Battlelog Platoon

Our allies:

• [NuB] TF2 clan
• Velocity Gamers Hub
• Destination Gamer

GoG Links:

• Wix Discord
• Wix IRC channel

TF2 Links:

• Official TF2 Blog
• TF2 Steam Forum
• The Fort 2

October 2025

Mo	Tu	We	Th	Fr	Sa	Su
		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31
	Birthdays
Chaos (40)
	Upcoming Events
Upcoming Birthdays: Chaos (40)

[Ringelbeatz]

Hello

The last few days I had always bluescreens on startup
but now I can't even start windows normally anymore.

I can run it on safe mode, but when I try to run it normally. BAM bluescreen after the win7 welcome screen is loading.

Any Ideas what to do?

[Millicent Bystander]

Stop hitting it with your spade?  Edit: Try hitting it with your spade?

Seriously though
Type in MSCONFIG in seach to bring up all the programs loaded on startup.  Disable all the startup programs except for your antivirus.  In Services tick "hide all Microsoft services" and disable ones you don't need/recognise
 
Try running your antivirus and Malwarebytes.

Delete graphics drivers and reinstall

Try running a program called CCleaner, it cleans up the registry and the bits the standard windows clean up stuff won't reach without needing much technical expertise.

Run Windows install over your existing install (ie don't delete anything)

Oh don't forget to backup

[Ringelbeatz]

so you think its more a software issue?
That would be nice, because I can't afford to buy new stuff atm.
I tried to run the windows dvd but the blue screen appears before i can get into the install/repair section...

[Millicent Bystander]

I would of thought it's a software problem as the PC is still working in safe mode.  If not it sounds like it may be a PSU or graphics problem.

Edit: try disconnecting you DVD drive.  That has worked for me before.

[Ringelbeatz]

thanks milli, will work with your suggestions now.

[Sonic4Ever]

Sometimes there's an error code on the bluescreen and/or a filename displayed (driver often) to give a clue

[Ringelbeatz]

yeah the code is something like 000000x00000050
but i desided to just reinstall windows.

I hope that will shut that stupid pc up otherwise I will post a video where i spade it to pieces

[Hzza]

I hope that will shut that stupid pc up otherwise I will post a video where i spade it to pieces

Fuck the Windows reinstall, I think this is the way to go. I read on a forum somewhere that it fixed some guys computer after he got a BSOD...

[egg]

working in safe mode and bsod in normal mode = driver issue (more than likely)

in safe mode go to c:\windows\minidump, and attach the latest file to this thread, and I'll debug it for you

[DeadlyAvenger]

working in safe mode and bsod in normal mode = driver issue (more than likely)

in safe mode go to c:\windows\minidump, and attach the latest file to this thread, and I'll debug it for you

You can do that? How?

[egg]

working in safe mode and bsod in normal mode = driver issue (more than likely)

in safe mode go to c:\windows\minidump, and attach the latest file to this thread, and I'll debug it for you

You can do that? How?

Using Windbg

edit - Its a microsoft tool, simply install it (install symbol packs for other os's if needs be i.e server 2003 symbol pack if debugging a 2003 server on an XP machine ), then go to file 'open crash dump, and point it at your dump file.  Click the link in the window to analyze, and it will tell you all the info you need... just a quick look will show you exactly what file caused the issue, and being a driver issue a quick google will tell you exactly what hardware driver set the file is for

[DeadlyAvenger]

What kind of information does it tell you?

[Ringelbeatz]

installation complete. looks solid now

next time I will try your suggestion egg

[egg]

What kind of information does it tell you?

Hold on I'll get an example from one I've done previously

[egg]

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


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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: symbols timestamp is wrong 0x4b7aa3ac 0x427b58bb for ntoskrnl.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8
Debug session time: Sun Sep  5 18:44:18.786 2010 (GMT+1)
System Uptime: 6 days 23:52:01.270
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: symbols timestamp is wrong 0x4b7aa3ac 0x427b58bb for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 0, baedd858, baedd554}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** WARNING: Unable to verify timestamp for baspxp32.sys
*** ERROR: Module load completed but symbols could not be loaded for baspxp32.sys
Probably caused by : baspxp32.sys ( baspxp32+bcaf )

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

2: 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: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: baedd858, Exception Record Address
Arg4: baedd554, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
+65e
00000000 ??             

EXCEPTION_RECORD:  baedd858 -- (.exr 0xffffffffbaedd858)
ExceptionAddress: 00000000
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000000
Attempt to read from address 00000000

CONTEXT:  baedd554 -- (.cxr 0xffffffffbaedd554)
eax=01312d00 ebx=00000004 ecx=00000003 edx=89f5c500 esi=89f2e000 edi=00000006
eip=00000000 esp=baedd920 ebp=baedd960 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
00000000 ??             
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

PROCESS_NAME:  è

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000000

READ_ADDRESS:  00000000

FOLLOWUP_IP:
baspxp32+bcaf
bac38caf ??             

FAILED_INSTRUCTION_ADDRESS:
+1e7952f011ddfdc
00000000 ??             

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 89f5e954 to 00000000

STACK_TEXT: 
WARNING: Frame IP not in any known module. Following frames may be wrong.
baedd91c 89f5e954 89f2e000 89f2e058 808398e8 0x0
baedd960 bac38caf 00000000 00010107 baedd9a8 0x89f5e954
baedddac 809208bb 89f2e000 00000000 00000000 baspxp32+0xbcaf
baedddc0 baedddb8 baedd3a8 ffffffff 8083a8fc nt!HvpDiscardBins+0x2d
baedddc8 ffffffff 8083a8fc 8082df18 00000000 0xbaedddb8
baedddcc 8083a8fc 8082df18 00000000 00000000 0xffffffff
baedde08 00000000 00000000 00000000 00000000 nt!MiRemoveUnusedSegments+0x65e


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  baspxp32+bcaf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: baspxp32

IMAGE_NAME:  baspxp32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bed8c5e

STACK_COMMAND:  .cxr 0xffffffffbaedd554 ; kb

FAILURE_BUCKET_ID:  0x7E_NULL_IP_baspxp32+bcaf

BUCKET_ID:  0x7E_NULL_IP_baspxp32+bcaf

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