BSOD with Microsoft wireless keyboard 6000 v3.0 and mou

hyperdisease · Jan 25, 2010

Microsoft Wireless keyboard 6000 v 3.0/mouse 6000 v2.0

I have been having problems with my wireless keyboard and mouse on my new Windows 7 64 bit pc. Frequently, the transceiver goes in and out. Therefore I have to move the transceiver to another usb port. The products start working fine then I get the BSOD and have to restart my computer. When I restart, there are no more problems for that session.

However, when I shut my pc down for a period of time and start up again later in the day, I get the BSOD after like 10 minutes in. At that time, I have to start up my pc again. Which again, I have no further issues for that session. The mouse cursor stops moving right before the BSOD.

The drivers on the mouse, keyboard and transceiver are up to date. I have replaced the batteries. I dont know what else to do.
Could someone please help me?

I cringe every time I see the BSOD and have to start after improper shutdown. It is getting frustrating. I had no prior problems with my wireless keyboard and mouse on my old pc (vista).

I have an ASUS CG5290 desktop and it came preinstalled with Windows 7. I've managed to take a picture of the BSOD. Could someone please help?!?!?

Any suggestions or comments would be greatly appreciated!

zigzag3143 · Jan 25, 2010

hyperdisease said:
Microsoft Wireless keyboard 6000 v 3.0/mouse 6000 v2.0

I have been having problems with my wireless keyboard and mouse on my new Windows 7 64 bit pc. Frequently, the transceiver goes in and out. Therefore I have to move the transceiver to another usb port. The products start working fine then I get the BSOD and have to restart my computer. When I restart, there are no more problems for that session.

However, when I shut my pc down for a period of time and start up again later in the day, I get the BSOD after like 10 minutes in. At that time, I have to start up my pc again. Which again, I have no further issues for that session. The mouse cursor stops moving right before the BSOD.

The drivers on the mouse, keyboard and transceiver are up to date. I have replaced the batteries. I dont know what else to do.
Could someone please help me?

I cringe every time I see the BSOD and have to start after improper shutdown. It is getting frustrating. I had no prior problems with my wireless keyboard and mouse on my old pc (vista).

I have an ASUS CG5290 desktop and it came preinstalled with Windows 7. I've managed to take a picture of the BSOD. Could someone please help?!?!?

Any suggestions or comments would be greatly appreciated!

We really need the actual dmp files use these to find and upload it http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

thanks

Ken

hyperdisease · Jan 25, 2010

Ken,
Sorry didnt know. Thank you for the reply. I have attached the minidump files to this post. Could you or anyone please help.

Thanks!

Capt.Jack Sparrow · Jan 25, 2010

hyperdisease said:
Ken,
Sorry didnt know. Thank you for the reply. I have attached the minidump files to this post. Could you or anyone please help.

Thanks!

Hyperdisease,

It's just the shortcut not the actual dump file. Copy and paste it to your Desktop then Zip it from here

Hope this helps,
Captain

hyperdisease · Jan 25, 2010

Capt,

Thanks for help. I attached the files individually. There were several and I didnt know which one to attach. Therefore, I attached all of them from top to bottom...

Thank you again.

Capt.Jack Sparrow · Jan 25, 2010

hyperdisease said:
Capt,

Thanks for help. I attached the files individually. There were several and I didnt know which one to attach. Therefore, I attached all of them from top to bottom...

Thank you again.

Ok i'm running the analysis meanwhile you could look this is related to your issue http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Edit:

Most of the Dump file are referring to the Bug Check 0x124 please follow that link to fix your porblem

Bugcheck Analysis

Code:

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

Loading Dump File [C:\Documents and Settings\Owner\Desktop\010810-20514-01.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: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a13000 PsLoadedModuleList = 0xfffff800`02c50e50
Debug session time: Sat Jan  9 10:42:12.878 2010 (GMT+5)
System Uptime: 0 days 0:00:08.798
Loading Kernel Symbols
.............................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80092e9688, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
5: kd> !thread;!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;
GetPointerFromAddress: unable to read from fffff80002cbb000
THREAD fffffa8007942040  Cid 0004.0030  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 5
Not impersonating
GetUlongFromAddress: unable to read from fffff80002bf9b74
Owning Process            fffffa8007926040       Image:         System
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      563          
Context Switch Count      118             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address nt!ExpWorkerThread (0xfffff80002a92050)
Stack Init fffff88003362db0 Current fffff88003362370
Base fffff88003363000 Limit fffff8800335d000 Call 0
Priority 12 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`033626f0 fffff800`02ccda89 : fffffa80`092e9660 fffffa80`07942040 00000000`0000000e 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03362c10 fffff800`02baf547 : fffffa80`092e9660 fffff800`02c285f8 fffffa80`07942040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03362c40 fffff800`02b17b95 : fffff800`02c8a360 fffffa80`08929828 fffffa80`08929820 fffffa80`07942040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03362c80 fffff800`02a92161 : fffff880`01114e00 fffff800`02b17b70 fffffa80`07942040 4dcd4dcd`a335a335 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03362cb0 fffff800`02d28166 : a3e6a3e6`56f956f9 fffffa80`07942040 00000000`00000080 fffffa80`07926040 : nt!ExpWorkerThread+0x111
fffff880`03362d40 fffff800`02a63486 : fffff880`0316a180 fffffa80`07942040 fffff880`031750c0 ad2ead2e`20972097 : nt!PspSystemThreadStartup+0x5a
fffff880`03362d80 00000000`00000000 : fffff880`03363000 fffff880`0335d000 fffff880`02ee4540 00000000`00000000 : nt!KxStartSystemThread+0x16
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80092e9688, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------

BUGCHECK_STR:  0x124_GenuineIntel
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`033626f0 fffff800`02ccda89 : fffffa80`092e9660 fffffa80`07942040 00000000`0000000e 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03362c10 fffff800`02baf547 : fffffa80`092e9660 fffff800`02c285f8 fffffa80`07942040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03362c40 fffff800`02b17b95 : fffff800`02c8a360 fffffa80`08929828 fffffa80`08929820 fffffa80`07942040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03362c80 fffff800`02a92161 : fffff880`01114e00 fffff800`02b17b70 fffffa80`07942040 4dcd4dcd`a335a335 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03362cb0 fffff800`02d28166 : a3e6a3e6`56f956f9 fffffa80`07942040 00000000`00000080 fffffa80`07926040 : nt!ExpWorkerThread+0x111
fffff880`03362d40 fffff800`02a63486 : fffff880`0316a180 fffffa80`07942040 fffff880`031750c0 ad2ead2e`20972097 : nt!PspSystemThreadStartup+0x5a
fffff880`03362d80 00000000`00000000 : fffff880`03363000 fffff880`0335d000 fffff880`02ee4540 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
Followup: MachineOwner
---------
rax=fffffa800932e000 rbx=fffffa80092e9688 rcx=fffff88003362730
rdx=fffff88003095000 rsi=0000000000000000 rdi=fffffa800932e000
rip=fffff80002eb93cc rsp=fffff880033626f0 rbp=0000000000000001
 r8=000000000000f1e0  r9=000000000000060c r10=00000000000007ff
r11=000000000000060c r12=fffff80002c8a3c0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
nt!WheapCreateLiveTriageDump+0x6c:
fffff800`02eb93cc 48897c2438      mov     qword ptr [rsp+38h],rdi ss:0018:fffff880`03362728=fffffa8000000910
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`033626f0 fffff800`02ccda89 : fffffa80`092e9660 fffffa80`07942040 00000000`0000000e 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03362c10 fffff800`02baf547 : fffffa80`092e9660 fffff800`02c285f8 fffffa80`07942040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03362c40 fffff800`02b17b95 : fffff800`02c8a360 fffffa80`08929828 fffffa80`08929820 fffffa80`07942040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03362c80 fffff800`02a92161 : fffff880`01114e00 fffff800`02b17b70 fffffa80`07942040 4dcd4dcd`a335a335 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03362cb0 fffff800`02d28166 : a3e6a3e6`56f956f9 fffffa80`07942040 00000000`00000080 fffffa80`07926040 : nt!ExpWorkerThread+0x111
fffff880`03362d40 fffff800`02a63486 : fffff880`0316a180 fffffa80`07942040 fffff880`031750c0 ad2ead2e`20972097 : nt!PspSystemThreadStartup+0x5a
fffff880`03362d80 00000000`00000000 : fffff880`03363000 fffff880`0335d000 fffff880`02ee4540 00000000`00000000 : nt!KxStartSystemThread+0x16
start             end                 module name
fffff800`00b9d000 fffff800`00ba7000   kdcom    kdcom.dll    Tue Jul 14 07:01:07 2009 (4A5BDFDB)
fffff800`02a13000 fffff800`02ff0000   nt       ntkrnlmp.exe Tue Jul 14 05:10:48 2009 (4A5BC600)
fffff800`02ff0000 fffff800`03039000   hal      hal.dll      Tue Jul 14 06:57:36 2009 (4A5BDF08)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Tue Jul 14 07:02:13 2009 (4A5BE01D)
fffff880`00cc0000 fffff880`00cda000   mountmgr mountmgr.sys Tue Jul 14 04:49:54 2009 (4A5BC11A)
fffff880`00cda000 fffff880`00ce3000   atapi    atapi.sys    Tue Jul 14 04:49:47 2009 (4A5BC113)
fffff880`00cf2000 fffff880`00d36000   mcupdate mcupdate.dll Tue Jul 14 06:59:10 2009 (4A5BDF66)
fffff880`00d36000 fffff880`00d4a000   PSHED    PSHED.dll    Tue Jul 14 07:02:23 2009 (4A5BE027)
fffff880`00d4a000 fffff880`00da8000   CLFS     CLFS.SYS     Tue Jul 14 04:49:57 2009 (4A5BC11D)
fffff880`00da8000 fffff880`00dd2000   ataport  ataport.SYS  Tue Jul 14 04:49:52 2009 (4A5BC118)
fffff880`00dd2000 fffff880`00df0000   jraid    jraid.sys    Thu Aug 13 13:40:27 2009 (4A83CA73)
fffff880`00e00000 fffff880`00e10000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 04:49:48 2009 (4A5BC114)
fffff880`00e10000 fffff880`00eb4000   Wdf01000 Wdf01000.sys Tue Jul 14 04:52:07 2009 (4A5BC19F)
fffff880`00eb4000 fffff880`00ec3000   WDFLDR   WDFLDR.SYS   Tue Jul 14 04:49:54 2009 (4A5BC11A)
fffff880`00ec3000 fffff880`00f1a000   ACPI     ACPI.sys     Tue Jul 14 04:49:34 2009 (4A5BC106)
fffff880`00f1a000 fffff880`00f23000   WMILIB   WMILIB.SYS   Tue Jul 14 04:49:51 2009 (4A5BC117)
fffff880`00f23000 fffff880`00f2d000   msisadrv msisadrv.sys Tue Jul 14 04:49:26 2009 (4A5BC0FE)
fffff880`00f2d000 fffff880`00f60000   pci      pci.sys      Tue Jul 14 04:49:51 2009 (4A5BC117)
fffff880`00f60000 fffff880`00f6d000   vdrvroot vdrvroot.sys Tue Jul 14 05:31:31 2009 (4A5BCADB)
fffff880`00f6d000 fffff880`00f82000   partmgr  partmgr.sys  Tue Jul 14 04:49:58 2009 (4A5BC11E)
fffff880`00f82000 fffff880`00f97000   volmgr   volmgr.sys   Tue Jul 14 04:49:57 2009 (4A5BC11D)
fffff880`00f97000 fffff880`00ff3000   volmgrx  volmgrx.sys  Tue Jul 14 04:50:33 2009 (4A5BC141)
fffff880`00ff3000 fffff880`00ffa000   pciide   pciide.sys   Tue Jul 14 04:49:49 2009 (4A5BC115)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Tue Jul 14 05:19:40 2009 (4A5BC814)
fffff880`010aa000 fffff880`010d9000   SCSIPORT SCSIPORT.SYS Tue Jul 14 05:31:04 2009 (4A5BCAC0)
fffff880`010d9000 fffff880`010e4000   amdxata  amdxata.sys  Tue May 19 23:26:59 2009 (4A12F2EB)
fffff880`010e4000 fffff880`01130000   fltmgr   fltmgr.sys   Tue Jul 14 04:49:59 2009 (4A5BC11F)
fffff880`01130000 fffff880`01144000   fileinfo fileinfo.sys Tue Jul 14 05:04:25 2009 (4A5BC481)
fffff880`01144000 fffff880`011a2000   msrpc    msrpc.sys    Tue Jul 14 04:51:32 2009 (4A5BC17C)
fffff880`011a2000 fffff880`011ee000   volsnap  volsnap.sys  Tue Jul 14 04:50:08 2009 (4A5BC128)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Tue Jul 14 04:50:54 2009 (4A5BC156)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Tue Jul 14 04:49:27 2009 (4A5BC0FF)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 04:49:45 2009 (4A5BC111)
fffff880`0125b000 fffff880`013fe000   Ntfs     Ntfs.sys     Tue Jul 14 04:50:47 2009 (4A5BC14F)
fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  Tue Jul 14 05:20:34 2009 (4A5BC84A)
fffff880`0142b000 fffff880`01475000   fwpkclnt fwpkclnt.sys Tue Jul 14 04:51:08 2009 (4A5BC164)
fffff880`01475000 fffff880`0147d000   spldr    spldr.sys    Mon May 11 22:26:27 2009 (4A0858BB)
fffff880`01499000 fffff880`0158b000   ndis     ndis.sys     Tue Jul 14 04:51:40 2009 (4A5BC184)
fffff880`0158b000 fffff880`015eb000   NETIO    NETIO.SYS    Tue Jul 14 04:51:46 2009 (4A5BC18A)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Tue Jul 14 04:55:34 2009 (4A5BC26E)
fffff880`018e0000 fffff880`0191a000   rdyboost rdyboost.sys Tue Jul 14 05:04:34 2009 (4A5BC48A)
fffff880`0191a000 fffff880`0192c000   mup      mup.sys      Tue Jul 14 04:53:45 2009 (4A5BC201)
fffff880`0192c000 fffff880`01935000   hwpolicy hwpolicy.sys Tue Jul 14 04:49:22 2009 (4A5BC0FA)
fffff880`01935000 fffff880`0196f000   fvevol   fvevol.sys   Tue Jul 14 04:52:15 2009 (4A5BC1A7)
fffff880`0196f000 fffff880`01985000   disk     disk.sys     Tue Jul 14 04:49:57 2009 (4A5BC11D)
fffff880`01985000 fffff880`019b5000   CLASSPNP CLASSPNP.SYS Tue Jul 14 04:49:58 2009 (4A5BC11E)
Mini Kernel Dump does not contain unloaded driver list
start             end                 module name
fffff880`00ec3000 fffff880`00f1a000   ACPI     ACPI.sys     Tue Jul 14 04:49:34 2009 (4A5BC106)
fffff880`010d9000 fffff880`010e4000   amdxata  amdxata.sys  Tue May 19 23:26:59 2009 (4A12F2EB)
fffff880`00cda000 fffff880`00ce3000   atapi    atapi.sys    Tue Jul 14 04:49:47 2009 (4A5BC113)
fffff880`00da8000 fffff880`00dd2000   ataport  ataport.SYS  Tue Jul 14 04:49:52 2009 (4A5BC118)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Tue Jul 14 07:02:13 2009 (4A5BE01D)
fffff880`01985000 fffff880`019b5000   CLASSPNP CLASSPNP.SYS Tue Jul 14 04:49:58 2009 (4A5BC11E)
fffff880`00d4a000 fffff880`00da8000   CLFS     CLFS.SYS     Tue Jul 14 04:49:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Tue Jul 14 05:19:40 2009 (4A5BC814)
fffff880`0196f000 fffff880`01985000   disk     disk.sys     Tue Jul 14 04:49:57 2009 (4A5BC11D)
fffff880`01130000 fffff880`01144000   fileinfo fileinfo.sys Tue Jul 14 05:04:25 2009 (4A5BC481)
fffff880`010e4000 fffff880`01130000   fltmgr   fltmgr.sys   Tue Jul 14 04:49:59 2009 (4A5BC11F)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 04:49:45 2009 (4A5BC111)
fffff880`01935000 fffff880`0196f000   fvevol   fvevol.sys   Tue Jul 14 04:52:15 2009 (4A5BC1A7)
fffff880`0142b000 fffff880`01475000   fwpkclnt fwpkclnt.sys Tue Jul 14 04:51:08 2009 (4A5BC164)
fffff800`02ff0000 fffff800`03039000   hal      hal.dll      Tue Jul 14 06:57:36 2009 (4A5BDF08)
fffff880`0192c000 fffff880`01935000   hwpolicy hwpolicy.sys Tue Jul 14 04:49:22 2009 (4A5BC0FA)
fffff880`00dd2000 fffff880`00df0000   jraid    jraid.sys    Thu Aug 13 13:40:27 2009 (4A83CA73)
fffff800`00b9d000 fffff800`00ba7000   kdcom    kdcom.dll    Tue Jul 14 07:01:07 2009 (4A5BDFDB)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Tue Jul 14 04:50:54 2009 (4A5BC156)
fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  Tue Jul 14 05:20:34 2009 (4A5BC84A)
fffff880`00cf2000 fffff880`00d36000   mcupdate mcupdate.dll Tue Jul 14 06:59:10 2009 (4A5BDF66)
fffff880`00cc0000 fffff880`00cda000   mountmgr mountmgr.sys Tue Jul 14 04:49:54 2009 (4A5BC11A)
fffff880`00f23000 fffff880`00f2d000   msisadrv msisadrv.sys Tue Jul 14 04:49:26 2009 (4A5BC0FE)
fffff880`01144000 fffff880`011a2000   msrpc    msrpc.sys    Tue Jul 14 04:51:32 2009 (4A5BC17C)
fffff880`0191a000 fffff880`0192c000   mup      mup.sys      Tue Jul 14 04:53:45 2009 (4A5BC201)
fffff880`01499000 fffff880`0158b000   ndis     ndis.sys     Tue Jul 14 04:51:40 2009 (4A5BC184)
fffff880`0158b000 fffff880`015eb000   NETIO    NETIO.SYS    Tue Jul 14 04:51:46 2009 (4A5BC18A)
fffff800`02a13000 fffff800`02ff0000   nt       ntkrnlmp.exe Tue Jul 14 05:10:48 2009 (4A5BC600)
fffff880`0125b000 fffff880`013fe000   Ntfs     Ntfs.sys     Tue Jul 14 04:50:47 2009 (4A5BC14F)
fffff880`00f6d000 fffff880`00f82000   partmgr  partmgr.sys  Tue Jul 14 04:49:58 2009 (4A5BC11E)
fffff880`00f2d000 fffff880`00f60000   pci      pci.sys      Tue Jul 14 04:49:51 2009 (4A5BC117)
fffff880`00ff3000 fffff880`00ffa000   pciide   pciide.sys   Tue Jul 14 04:49:49 2009 (4A5BC115)
fffff880`00e00000 fffff880`00e10000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 04:49:48 2009 (4A5BC114)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Tue Jul 14 04:49:27 2009 (4A5BC0FF)
fffff880`00d36000 fffff880`00d4a000   PSHED    PSHED.dll    Tue Jul 14 07:02:23 2009 (4A5BE027)
fffff880`018e0000 fffff880`0191a000   rdyboost rdyboost.sys Tue Jul 14 05:04:34 2009 (4A5BC48A)
fffff880`010aa000 fffff880`010d9000   SCSIPORT SCSIPORT.SYS Tue Jul 14 05:31:04 2009 (4A5BCAC0)
fffff880`01475000 fffff880`0147d000   spldr    spldr.sys    Mon May 11 22:26:27 2009 (4A0858BB)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Tue Jul 14 04:55:34 2009 (4A5BC26E)
fffff880`00f60000 fffff880`00f6d000   vdrvroot vdrvroot.sys Tue Jul 14 05:31:31 2009 (4A5BCADB)
fffff880`00f82000 fffff880`00f97000   volmgr   volmgr.sys   Tue Jul 14 04:49:57 2009 (4A5BC11D)
fffff880`00f97000 fffff880`00ff3000   volmgrx  volmgrx.sys  Tue Jul 14 04:50:33 2009 (4A5BC141)
fffff880`011a2000 fffff880`011ee000   volsnap  volsnap.sys  Tue Jul 14 04:50:08 2009 (4A5BC128)
fffff880`00e10000 fffff880`00eb4000   Wdf01000 Wdf01000.sys Tue Jul 14 04:52:07 2009 (4A5BC19F)
fffff880`00eb4000 fffff880`00ec3000   WDFLDR   WDFLDR.SYS   Tue Jul 14 04:49:54 2009 (4A5BC11A)
fffff880`00f1a000 fffff880`00f23000   WMILIB   WMILIB.SYS   Tue Jul 14 04:49:51 2009 (4A5BC117)
Mini Kernel Dump does not contain unloaded driver list
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`092e9688 00000000`00000000 00000000`00000000

Hope this helps,
captain

hyperdisease · Jan 26, 2010

Capt,
Thank you very much for the suggestion. I took the advice to not overclock. Quite frankly, I didn't even know it was happening. I noticed a pre-installed software called
EPU-6 which gives me the freedom to set my performance settings. It was set on high and I lowered it to medium. Since then, I havent had the BSOD problem. (knock on wood)
Hopefully, this is the solution.

Thanks again!!

Capt.Jack Sparrow · Jan 26, 2010

hyperdisease said:
Capt,
Thank you very much for the suggestion. I took the advice to not overclock. Quite frankly, I didn't even know it was happening. I noticed a pre-installed software called
EPU-6 which gives me the freedom to set my performance settings. It was set on high and I lowered it to medium. Since then, I havent had the BSOD problem. (knock on wood)
Hopefully, this is the solution.

Thanks again!!

Your Most Welcome Mate .. Let us know if you have any problems we will be here

hyperdisease · Jan 26, 2010

WOW, just my luck!!!!

Right after I posted the comment, BSOD.....ergh!

Help again????

Capt.Jack Sparrow · Jan 26, 2010

hyperdisease said:
WOW, just my luck!!!!

Right after I posted the comment, BSOD.....ergh!

Help again????

Just checked the Dump it has the same Stop Error "BUGCHECK_STR: 0x124_GenuineIntel" did you follow H2SO4's full documentation ??

hyperdisease · Jan 26, 2010

Capt,
If it is in regards with the link you posted, below is what I have tried.

1. components no longer overclocked (reduced high to medium performance)
2. The machine is cool...Currently CPU is 36 C....Motherboard 52 C.....Processors averaging 51 C
3. Updated all drivers
4. updated BIOS
5. Windows is updated
6. Ran MDSCHED with no errors
7. did CHKDSK but didnt really understand it. (window popped up and ran through 3 stages and disappeared...

As far as a vanilla reinstallation, I did not try because I have no clue how to proceed. So, a bit reluctant in this dept.

Regarding dust, it is a new computer and I have this product call Shopshield....which is a filter that covers the desktop. So, I think dust should'nt be an issue.

Anything I'm doing wrong or should try?

usasma · Jan 27, 2010

Motherboard 52 C - that's awfully high. IME the mobo is usually 10 to 20 degrees cooler than the CPU

CHKDSK Report:

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

Vanilla reinstallation is only installing Windows - no extra programs. Check Device Manager to ensure all drivers are installed - only install any missing drivers from the manufacturer's website. Install Windows Updates, and maybe an antivirus (NOT an Internet Security application)

hyperdisease · Jan 27, 2010

usasma,

Thanks for the reply.
What are the best ways to lower my MB heat? It is consistently at 51-52 C....

I hope I followed your directions correctly. Below is what I copy and pasted for CHKDSK

Checking file system on C: The type of the file system is NTFS. Volume label is WIN7. WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... 143360 file records processed. File verification completed. 56 large file records processed. 0 bad file records processed. 0 EA records processed. 42 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 178388 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)... 143360 file SDs/SIDs processed. Cleaning up 646 unused index entries from index $SII of file 0x9. Cleaning up 646 unused index entries from index $SDH of file 0x9. Cleaning up 646 unused security descriptors. Security descriptor verification completed. 17515 data files processed. CHKDSK is verifying Usn Journal... 37127240 USN bytes processed. Usn Journal verification completed. Windows has checked the file system and found no problems. 390708832 KB total disk space. 43726664 KB in 63261 files. 78000 KB in 17516 indexes. 0 KB in bad sectors. 258388 KB in use by the system. 65536 KB occupied by the log file. 346645780 KB available on disk. 4096 bytes in each allocation unit. 97677208 total allocation units on disk. 86661445 allocation units available on disk.
00300200953B0100725B020000000000E84600002A0000000000000000000000

--------------------------------------------------------------------------------

Binary data:

In Words

0000: 00023000 00013B95 00025B72 00000000
0008: 000046E8 0000002A 00000000 00000000

In Bytes

0000: 00 30 02 00 95 3B 01 00 .0..;..
0008: 72 5B 02 00 00 00 00 00 r[......
0010: E8 46 00 00 2A 00 00 00 èF..*...
0018: 00 00 00 00 00 00 00 00 ........

usasma · Jan 30, 2010

Windows has checked the file system and found no problems.

That's good!

To lower the heat you've gotta figure out what's overheating (and why).
First, are you BIOS settings set at default/fail safe/optimized?

Then, run the computer until the mobo gets that hot. Then shutdown, unplug from the wall, and open the case.
CAREFULLY feel around the motherboard (while holding on to the metal of the case) to see what feels excessively hot (you can burn yourself this way!).

While you're in there, check to see if the air vents are clear and that the airflow isn't obstructed.
Once you're done checking everything, plug the case in and boot it up just long enough to check and see if the fans are working (DON'T stick your fingers in the case!).

Then, to help lower the temp's, point a house fan into the case and see if that helps - both in lowering the temps and to see if it decreases the frequency of the BSOD's.

BSOD with Microsoft wireless keyboard 6000 v3.0 and mou

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Crash Dump Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Crash Dump Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Crash Dump Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Crash Dump Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer