CanSpoilU
Got a damm blue screen on Sat night right in the middle of my gig. Grrrrrrrr.
I still haven't figured out why this happens. It happens maybe once every 1-2 months. My laptop will be playing great... then all of a sudden BAMM the screen goes out music goes off... blue screen and reboot.
I wasn't even doing anything special. The song was playing and I was standing there watching the crowd (and working the mic).
The only saving grace about this particular blue screen was it happened right in the middle of the chorus of "I will Survive". All joking aside with the song... the music cut out and all the girls kept singing the verse. LOL I almost made it looked "planned". Thank god I had a DVD lined up in my backup player I threw right on.
Any ideas what I should look for in a blue screen? Laptop wasn't hot or overheating. I run videos and MK2 controller. XP install was fresh (in fact I just formatted the week before).
I still haven't figured out why this happens. It happens maybe once every 1-2 months. My laptop will be playing great... then all of a sudden BAMM the screen goes out music goes off... blue screen and reboot.
I wasn't even doing anything special. The song was playing and I was standing there watching the crowd (and working the mic).
The only saving grace about this particular blue screen was it happened right in the middle of the chorus of "I will Survive". All joking aside with the song... the music cut out and all the girls kept singing the verse. LOL I almost made it looked "planned". Thank god I had a DVD lined up in my backup player I threw right on.
Any ideas what I should look for in a blue screen? Laptop wasn't hot or overheating. I run videos and MK2 controller. XP install was fresh (in fact I just formatted the week before).
Posted Mon 06 Aug 07 @ 5:02 pm
CanSpoilU
Let me also add that I am a senior computer network engineer... which is what I do fulltime. So I am highly computer proficient so I am willing to try just about anything. ;)
Not sure if I mentioned this before.
Not sure if I mentioned this before.
Posted Mon 06 Aug 07 @ 5:03 pm
Andrew87
Start > Run > eventvwr.msc
Check out the Applications and System tabs. You can look through by date and time so shouldn't have too much problem finding the error. When you find the error, rightclick and goto Properties. Post back the details here.
Check out the Applications and System tabs. You can look through by date and time so shouldn't have too much problem finding the error. When you find the error, rightclick and goto Properties. Post back the details here.
Posted Mon 06 Aug 07 @ 5:08 pm
sbangs
just a thought how do you cool your machine , it might be geting toasty
Posted Mon 06 Aug 07 @ 5:09 pm
cstoll
What is the message on the BlueScreen? You should know you can query the MS Knowledge Base on that error - - it is worth a stab at a good starting point.
Posted Mon 06 Aug 07 @ 5:12 pm
Andrew87
This site may come in handy alongside the MS one
http://www.eventid.net/display.asp
http://www.eventid.net/display.asp
Posted Mon 06 Aug 07 @ 5:15 pm
CanSpoilU
The bluescreen flashes too quickly for me to get the error message. Ill check out the event viewer and let you know.
I think the last time this happened there was no event ID generated. It just gave a "the previous system shutdown was unexpected" error.
I think the last time this happened there was no event ID generated. It just gave a "the previous system shutdown was unexpected" error.
Posted Mon 06 Aug 07 @ 5:34 pm
CanSpoilU
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 8/5/2007
Time: 12:41:00 AM
User: N/A
Computer: DJPILL-VDJ
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e (0xc0000005, 0xb213dbb1, 0xbad07a98, 0xbad07794). A dump was saved in: D:\WINDOWS\Minidump\Mini080507-01.dmp.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 8/5/2007
Time: 12:41:00 AM
User: N/A
Computer: DJPILL-VDJ
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e (0xc0000005, 0xb213dbb1, 0xbad07a98, 0xbad07794). A dump was saved in: D:\WINDOWS\Minidump\Mini080507-01.dmp.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Posted Mon 06 Aug 07 @ 5:42 pm
Andrew87
Any of this relevent to your system?
http://support.microsoft.com/?kbid=925528
Ideally, you should upload your minidump somewhere.
http://support.microsoft.com/?kbid=925528
Ideally, you should upload your minidump somewhere.
Posted Mon 06 Aug 07 @ 5:50 pm
cstoll
It was generated by a driver issue - read here - http://msdn2.microsoft.com/en-us/library/ms795746.aspx
Searched - Bugcheck 0x1000007e
The follow on hex codes point to
# 0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred.
Searched - Bugcheck 0x1000007e
The follow on hex codes point to
# 0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred.
Posted Mon 06 Aug 07 @ 5:52 pm
CanSpoilU
I ran the windows debugger and got these results. What is swmx00.sys used for? Anyone know?
--------------------------------------------------
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [d:\windows\minidump\minidump.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: F:\windows\i386
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Aug 5 00:40:08.250 2007 (GMT-4)
System Uptime: 0 days 1:34:24.029
Loading Kernel Symbols
.........................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image swmx00.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for swmx00.sys
*** ERROR: Module load completed but symbols could not be loaded for swmx00.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, b213dbb1, bad07a98, bad07794}
Probably caused by : swmx00.sys ( swmx00+8bb1 )
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: c0000005, The exception code that was not handled
Arg2: b213dbb1, The address that the exception occurred at
Arg3: bad07a98, Exception Record Address
Arg4: bad07794, 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:
swmx00+8bb1
b213dbb1 80480301 or byte ptr [eax+3],1
EXCEPTION_RECORD: bad07a98 -- (.exr 0xffffffffbad07a98)
ExceptionAddress: b213dbb1 (swmx00+0x00008bb1)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000003
Attempt to write to address 00000003
CONTEXT: bad07794 -- (.cxr 0xffffffffbad07794)
eax=00000000 ebx=00000000 ecx=88611104 edx=000000e1 esi=886111f8 edi=886112b3
eip=b213dbb1 esp=bad07b60 ebp=bad07b68 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
swmx00+0x8bb1:
b213dbb1 80480301 or byte ptr [eax+3],1 ds:0023:00000003=??
Resetting default scope
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
WRITE_ADDRESS: 00000003
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 804f15b6 to b213dbb1
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bad07b68 804f15b6 88744028 886111f8 887440e0 swmx00+0x8bb1
bad07b98 b8a98859 00000000 bad07bd8 bad07bc0 nt!IopfCompleteRequest+0xa2
bad07ba8 b8a98d23 892d20e8 886111f8 00000000 usbhub!USBH_CompletePowerIrp+0x41
bad07bc0 b8a98d5a 892d20e8 bad07bd8 00000000 usbhub!USBH_HubCompleteQueuedPortWakeIrps+0x23
bad07be0 b8a98e2d 892d20e8 00000000 8918e6e7 usbhub!USBH_HubCompletePortWakeIrps+0x28
bad07bf8 80525cdf 8883b030 00000002 00000001 usbhub!USBH_FdoPoRequestD0Completion+0x17
bad07c28 804f15b6 892d2030 8918e608 b8a98e16 nt!PopCompleteRequestIrp+0x55
bad07c58 b4669090 00000001 bad07ca0 b4677ad6 nt!IopfCompleteRequest+0xa2
bad07c64 b4677ad6 8883b030 8918e608 00000000 USBPORT!USBPORT_CompleteIrp+0x2a
bad07ca0 b46691cc 8883b030 8918e608 80562248 USBPORT!USBPORT_PdoPowerIrp+0x600
bad07cc4 804ef095 8918e6c0 8883b188 8918e6c0 USBPORT!USBPORT_Dispatch+0x132
bad07cd4 80525d89 8918e6c0 8918e608 00000000 nt!IopfCallDriver+0x31
bad07ce8 805262a3 8918e6c0 8918e608 8918e6dc nt!PopPresentIrp+0x57
bad07d08 b8a99f93 8883b030 8883b9e8 8918e608 nt!PoCallDriver+0x195
bad07d2c b8a95055 892d20e8 8918e608 00000002 usbhub!USBH_FdoPower+0x3fd
bad07d54 b8a951ee 892d20e8 8918e608 bad07d7c usbhub!USBH_FdoDispatch+0x7f
bad07d64 804ef095 892d2030 8918e608 8056375c usbhub!USBH_HubDispatch+0x5e
bad07d74 80525c13 bad07dac 805379bd 8918e608 nt!IopfCallDriver+0x31
bad07d7c 805379bd 8918e608 00000000 89e3f640 nt!PopPassivePowerCall+0x13
bad07dac 805ce84c 8918e608 00000000 00000000 nt!ExpWorkerThread+0xef
bad07ddc 8054532e 805378ce 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
swmx00+8bb1
b213dbb1 80480301 or byte ptr [eax+3],1
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: swmx00
IMAGE_NAME: swmx00.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45de34c6
SYMBOL_NAME: swmx00+8bb1
STACK_COMMAND: .cxr 0xffffffffbad07794 ; kb
FAILURE_BUCKET_ID: 0x7E_BADMEMREF_swmx00+8bb1
BUCKET_ID: 0x7E_BADMEMREF_swmx00+8bb1
Followup: MachineOwner
---------
--------------------------------------------------
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [d:\windows\minidump\minidump.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: F:\windows\i386
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Aug 5 00:40:08.250 2007 (GMT-4)
System Uptime: 0 days 1:34:24.029
Loading Kernel Symbols
.........................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image swmx00.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for swmx00.sys
*** ERROR: Module load completed but symbols could not be loaded for swmx00.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, b213dbb1, bad07a98, bad07794}
Probably caused by : swmx00.sys ( swmx00+8bb1 )
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: c0000005, The exception code that was not handled
Arg2: b213dbb1, The address that the exception occurred at
Arg3: bad07a98, Exception Record Address
Arg4: bad07794, 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:
swmx00+8bb1
b213dbb1 80480301 or byte ptr [eax+3],1
EXCEPTION_RECORD: bad07a98 -- (.exr 0xffffffffbad07a98)
ExceptionAddress: b213dbb1 (swmx00+0x00008bb1)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000003
Attempt to write to address 00000003
CONTEXT: bad07794 -- (.cxr 0xffffffffbad07794)
eax=00000000 ebx=00000000 ecx=88611104 edx=000000e1 esi=886111f8 edi=886112b3
eip=b213dbb1 esp=bad07b60 ebp=bad07b68 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
swmx00+0x8bb1:
b213dbb1 80480301 or byte ptr [eax+3],1 ds:0023:00000003=??
Resetting default scope
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
WRITE_ADDRESS: 00000003
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 804f15b6 to b213dbb1
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bad07b68 804f15b6 88744028 886111f8 887440e0 swmx00+0x8bb1
bad07b98 b8a98859 00000000 bad07bd8 bad07bc0 nt!IopfCompleteRequest+0xa2
bad07ba8 b8a98d23 892d20e8 886111f8 00000000 usbhub!USBH_CompletePowerIrp+0x41
bad07bc0 b8a98d5a 892d20e8 bad07bd8 00000000 usbhub!USBH_HubCompleteQueuedPortWakeIrps+0x23
bad07be0 b8a98e2d 892d20e8 00000000 8918e6e7 usbhub!USBH_HubCompletePortWakeIrps+0x28
bad07bf8 80525cdf 8883b030 00000002 00000001 usbhub!USBH_FdoPoRequestD0Completion+0x17
bad07c28 804f15b6 892d2030 8918e608 b8a98e16 nt!PopCompleteRequestIrp+0x55
bad07c58 b4669090 00000001 bad07ca0 b4677ad6 nt!IopfCompleteRequest+0xa2
bad07c64 b4677ad6 8883b030 8918e608 00000000 USBPORT!USBPORT_CompleteIrp+0x2a
bad07ca0 b46691cc 8883b030 8918e608 80562248 USBPORT!USBPORT_PdoPowerIrp+0x600
bad07cc4 804ef095 8918e6c0 8883b188 8918e6c0 USBPORT!USBPORT_Dispatch+0x132
bad07cd4 80525d89 8918e6c0 8918e608 00000000 nt!IopfCallDriver+0x31
bad07ce8 805262a3 8918e6c0 8918e608 8918e6dc nt!PopPresentIrp+0x57
bad07d08 b8a99f93 8883b030 8883b9e8 8918e608 nt!PoCallDriver+0x195
bad07d2c b8a95055 892d20e8 8918e608 00000002 usbhub!USBH_FdoPower+0x3fd
bad07d54 b8a951ee 892d20e8 8918e608 bad07d7c usbhub!USBH_FdoDispatch+0x7f
bad07d64 804ef095 892d2030 8918e608 8056375c usbhub!USBH_HubDispatch+0x5e
bad07d74 80525c13 bad07dac 805379bd 8918e608 nt!IopfCallDriver+0x31
bad07d7c 805379bd 8918e608 00000000 89e3f640 nt!PopPassivePowerCall+0x13
bad07dac 805ce84c 8918e608 00000000 00000000 nt!ExpWorkerThread+0xef
bad07ddc 8054532e 805378ce 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
swmx00+8bb1
b213dbb1 80480301 or byte ptr [eax+3],1
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: swmx00
IMAGE_NAME: swmx00.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45de34c6
SYMBOL_NAME: swmx00+8bb1
STACK_COMMAND: .cxr 0xffffffffbad07794 ; kb
FAILURE_BUCKET_ID: 0x7E_BADMEMREF_swmx00+8bb1
BUCKET_ID: 0x7E_BADMEMREF_swmx00+8bb1
Followup: MachineOwner
---------
Posted Mon 06 Aug 07 @ 6:01 pm
Andrew87
Possibly C:/Program Files/Sierra Wireless/USBMUX Drivers/
http://www.runscanner.net/getmd5.aspx?MD5=5753F4DEF80535E8D8BA753A18CB6A20&process=swmx00.sys
http://www.runscanner.net/getmd5.aspx?MD5=5753F4DEF80535E8D8BA753A18CB6A20&process=swmx00.sys
Posted Mon 06 Aug 07 @ 6:03 pm
cstoll
Don't tell me you leave your wireless ON while using this machine and DJing?
Posted Mon 06 Aug 07 @ 6:04 pm
CanSpoilU
Andrew87 wrote :
Any of this relevent to your system?
http://support.microsoft.com/?kbid=925528
Ideally, you should upload your minidump somewhere.
http://support.microsoft.com/?kbid=925528
Ideally, you should upload your minidump somewhere.
I have 2 GB of memory and I have an NVIDIA video card... but I do not think I have an NFORCE USB controller on this laptop's motherboard.
Posted Mon 06 Aug 07 @ 6:06 pm
Andrew87
That won't be the problem, it's the Sierra driver. The debug information cleared that bit up :)
Posted Mon 06 Aug 07 @ 6:07 pm
CanSpoilU
The Sierra Wireless is my aircard that I use on my laptop (not the built in wireless G). I use this every night. But the bluescreen only happens once every two months.
Posted Mon 06 Aug 07 @ 6:08 pm
Andrew87
The cards drivers are what's causing the crash. You can try searching for an updated driver, but you are still taking the risk having it enabled when using VirtualDJ. You could try sending the crash information to Sierra, whether that would do any good or not I can't say.
Posted Mon 06 Aug 07 @ 6:12 pm
CanSpoilU
I just looked and the driver I am using for my Sierra Wireless is called SWNC5E00.SYS.
Where can I look to see if this SWMX00.SYS driver is loaded on my system and is active?
Where can I look to see if this SWMX00.SYS driver is loaded on my system and is active?
Posted Mon 06 Aug 07 @ 6:14 pm
Andrew87
Check Device Manager and expand the properties for your Sierra Wireless card. Under the Driver tab check out Driver Details, you should find it listed there. There will probably be a few files listed including the sys file you mentioned.
Posted Mon 06 Aug 07 @ 6:17 pm
CanSpoilU
Andrew87 wrote :
Check Device Manager and expand the properties for your Sierra Wireless card. Under the Driver tab check out Driver Details, you should find it listed there. There will probably be a few files listed including the sys file you mentioned.
I already checked that... that was the only driver (the one I just posted above).
Posted Mon 06 Aug 07 @ 6:23 pm
